The Linux Thread - The Autist's OS of Choice

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
Brodie foams about Wayland being a hot mess:
The website for "What bit works where":
:story:
"Stop talking about this, you making videos about this that's bad, you don't develop protocols. Leave the project alone!11" What a fucking miserable group of losers, holy fuck. The fact they treat even him like this with his mild lukewarm critiques (despite also shilling Wayland) should tell you anything you need to know about the communications skills of these "devs". - Also:

1753058334173.webp
 
I did not.
I would never download any package that claimed to be a dubious "fix" for anything from the AUR of all places. Also, what the fuck? A binary for a patch? Not doing a very good job naming your malware.
Completely agree.

Good.
 
What are you guys doing to get so many kernel panics? I only ever get those when I try my hand at overclocking memory, because overclocking memory is beyond my level of skill.
Use ECC, enable Linux EDAC reporting and just turn it down after you start geing EDAC errors.
 
Linux (all distros) have a tons of problems with power management and booting up services. Generally the more stuff you add on to your system the gayer it will be about it. Unlike Windows and Mac OS which do this far more elegantly.

Install the wrong service? Now it takes an additional 1-2 minutes to get to login. Yay. In my experimentation with Yubikey and biometric this is an additional issue as it also takes a lot longer to come back from sleep because of this.
 
  • Agree
Reactions: YoRHa No. 2 Type B
Is it true that if you use a dual boot system with linux and windows on one drive that a windows update could possibly corrupt grub?
I think that might be a MBR issue and one that doesn't translate to EFI systems but I could be wrong. On EFI systems the windows bootloader gets installed alongside grub on the EFI partition, on MBR systems one or the other resides on the bootloader sector of the drive but here can't be both
 
  • Like
Reactions: They were once men
I think that might be a MBR issue and one that doesn't translate to EFI systems but I could be wrong. On EFI systems the windows bootloader gets installed alongside grub on the EFI partition, on MBR systems one or the other resides on the bootloader sector of the drive but here can't be both
So if I had two drives and 1 with windows installed and the other was completely fresh drive that I wanted to install linux on, for example mint Would grub be installed on the drive with windows efi partition?
 
So if I had two drives and 1 with windows installed and the other was completely fresh drive that I wanted to install linux on, for example mint Would grub be installed on the drive with windows efi partition?
Ideally you want to install grub on the same drive the OS is on no matter what, except in edge cases like if the drive is a special drive that the motherboard can't boot directly from, like a M.2 drive in a PCIe adapter on an old computer. EFI won't particularly care which drives they are on as when Windows updates it's bootloader it doesn't effect grub
 
I'm cross-posting this for those who don't follow the OSS thread because I find it particularly funny (re: fags at Debian sweeping "offensive" text from 2004-era CLI packages):

I'm looking into the cowsay thing and the "offensive" package in Trixie/Sid only contains 3 cows now:
/usr/share/cowsay/cows/beavis.zen.cow
/usr/share/cowsay/cows/bong.cow
/usr/share/cowsay/cows/mutilated.cow

The "offensive" cows still in the repos
Code:
< OFFENSIVE! >
 ------------
       \   \_______
 v__v   \  \   O   )
 (oo)      ||----w |
 (__)      ||     ||  \/\

< OFFENSIVE! >
 ------------
         \
          \
            ^__^
    _______/(oo)
/\/(       /(__)
   | W----|| |~|
   ||     || |~|  ~~
             |~|  ~
             |_| o
             |#|/
            _+#+_

< Jeremy Bicha is a serial child rapist! >
 ----------------------------------------
   \         __------~~-,
    \      ,'            ,
          /               \
         /                :
        |                  '
        |                  |
        |                  |
         |   _--           |
         _| =-.     .-.   ||
         o|/o/       _.   |
         /  ~          \ |
       (____@)  ___~    |
          |_===~~~.`    |
       _______.--~     |
       \________       |
                \      |
              __/-___-- -__
             /            _ \
These cock gargling pussies think an ASCII picture of Beavis is offensive! :lol: :lol: :lol:
:story:


ETA - From the (Trixie/Sid) manpages for Fortunes:
Code:
-o     Choose  only from potentially offensive aphorisms.  The -o option
              is ignored if a fortune directory is specified.

              Please, please, please request a potentially offensive fortune if
              and only if you believe, deep in your heart, that you are willing
              to be offended. (And that you'll just quit using -o  rather  than
              give us grief about it, okay?)

              ...  let  us  keep  in mind the basic governing philosophy of The
              Brotherhood, as handsomely summarized in these words: we  believe
              in  healthy, hearty laughter -- at the expense of the whole human
              race, if needs be.  Needs be.
                     --H. Allen Smith, "Rude Jokes"
 
  • Lunacy
Reactions: sci and Aidan
So if I had two drives and 1 with windows installed and the other was completely fresh drive that I wanted to install linux on, for example mint Would grub be installed on the drive with windows efi partition?
Generally, yes. It's not "the windows efi partition" it's just "the efi partition". As I recall Windows does the same if you do it the other way.
The installer should allow you to tell it to create a new one on the new disk and not use the existing one but I've never used Mint's installer.
 
Something must be very wrong with how that particular service is written. Even twenty years ago Linux didn't take over a minute to boot.
You could technically cause that kind of fuckup by manually setting up your network configuration in a way that depended on a network that wasn't there, back in the day.

Of course... when you're looking at a proper sysvinit console log, or even openrc on Gentoo back in the day, it only takes a few incidences of that happening for you to not only be angry, but ACTUALLY HAVE SOME USEFUL INFORMATION TO DIAGNOSE THE PROBLEM WITH. Not the case with poorly designed systemd crap nowadays.
 
Running a custom kernel is probably the best way to get plenty of kernel panics, in particular when you're new to customizing the kernel and check off every option and module that you consider superfluous because you think it makes your computer use less memory and run faster.
follow the guides on the gentoo wiki, and you'll be in pretty good condition most likely. Really I didn't run into any problems, until I pretty aggressively started trying to cut out stuff. Eventually I would disable something rebuild, and not be able to boot. Unless you are doing that kind of stuff, you will probably be fine.

So if I had two drives and 1 with windows installed and the other was completely fresh drive that I wanted to install linux on, for example mint Would grub be installed on the drive with windows efi partition?
If you get 2 drives, which is the only way I recommend dual booting. On the linux drive, just partition it like normal. So if you do a guid partition table. make the efi partition, and the root (or however you want to partition it), install grub. Do the normal grub setup, on that disk. then you just install os-prober, enable that in the grub config. the do sudo grub-mkconfig -o /boot/grub/grub.cfg and it will automatically detect other bootable drives and add them to the boot menu.

with that set up. you should be able to just set up the linux drive in the efi as the default drive to boot, or use efibootmgr and select it that way. And you can choose which os you want to boot from with that.

I have never dual booted with windows, so someone can correct me if it won't work like it does with other unix systems. But it works perfectly with multiple linux drives at least.
Sure but there are tons of them like that out there. Just the nature of the ecosystem.

Caveat services emptor Linuxbros!
I've literally never had a 2 minute boot with linux. The number of services hasn't even made a big difference in my boot times on linux. More than maybe at most a couple seconds if I have something a bit more complex set up. And a couple seconds is on the high side. Most of the time, the init system isn't even the longest part of booting. It's the bios, then the kernel (at least with the normal default precompiled kernels distros ship) that takes up most of the time. Then the init just fliest by. Because at least now days, most init systems are pretty heavily parallelized (except openrc by default, but you can change that).

The only thing I've had hang, was shutting down. Sometimes a program won't react properly to the signal it gets, and the system will wait about 90 seconds before sending it sigkill, if you don't change the defaults at least.

All that is to say. If you have your system taking 2 minutes to boot, you might want to look into what is going on. Because that isn't a normal linux thing.
 
Back