Timeline
Post
Remote status
Replies
43
Let us know if you're able to go 2 minutes without finding a bug #ubuntu
I mean I'd like to learn about a linux distro that you can go 2 minutes without finding a bug.
@cjd I'm less than a year into my venture into Linux but I haven't encountered any bugs yet, although it could be I'm too inexperienced to recognize them as such π Also I don't do anything advanced, mostly playing around with various tools in the terminal. Like today I've been using grep to filter some data from one .csv to another and then calculate something in the new file using sc-im, so much more fun than Excel.
My recollection of Ubuntu is having troubles in the first 30 minutes of setting it up, and then realizing that the "troubles" are not really user error, but rather that the default ubuntu apps (gnome stuff) just have bugs, like save button doesn't save, that type of stuff.
@cjd Ubuntu's default partition setup allocates a 512MB /boot. You tell it "do what you want with the disk" and it'll do that. Then by default it turns on unattended-upgrades. Then it trickles new kernels to /boot but does not remove the old ones and updates the bootloader to boot the new kernel by default, which apparently occurs whether or not /boot is full. Then eventually the user reboots the machine. There are two options on the screen: new kernel, or new kernel plus safe mode. But the kernel it is configured to use does not represent a kernel that is actually on the disk, so it refuses to boot. Ubuntu renders itself impossible to boot. Ubuntu commits suicide if you don't intervene.
I do not know for certain whether this problem persists to the present day but it did occur for years. I don't know who is in charge of QA at Canonical but apparently no one is in charge of telling Ubuntu not to commit suicide.
I do not know for certain whether this problem persists to the present day but it did occur for years. I don't know who is in charge of QA at Canonical but apparently no one is in charge of telling Ubuntu not to commit suicide.
I heard that everyone at that company just spends all of their time interviewing people for ghost jobs over and over until the candidate gives up.
@p @cjd about the boot partition, 512MB sounds a waste of space, but I think I must be confusing this with the EFI partition, because I made it of 16MB on /dev/sda2 because /dev/sda1 was suddenly "corrupted", and that amount of space was a lot.
Continuing about the topic, you *should* run sudo apt autoremove (or autoclean - I honestly don't remember the difference right now) - oh wait that doesn't remove old kernels I think...
it doesn't, because MX Linux comes with a tool for exactly that, remove old kernels from the boot partition... but isn't the partition where the BIOS checks first? I'm so confused right now.
Anyway, I will use this post to tell you I applied to a job at Canonical once and they made me have an interview with an AI that would skip questions if you wouldn't begin to reply after 3 seconds (each question) -it was so annoying that I let her keep asking to see what were the questions. Mostly about AppArmor and Snap.
Continuing about the topic, you *should* run sudo apt autoremove (or autoclean - I honestly don't remember the difference right now) - oh wait that doesn't remove old kernels I think...
it doesn't, because MX Linux comes with a tool for exactly that, remove old kernels from the boot partition... but isn't the partition where the BIOS checks first? I'm so confused right now.
Anyway, I will use this post to tell you I applied to a job at Canonical once and they made me have an interview with an AI that would skip questions if you wouldn't begin to reply after 3 seconds (each question) -it was so annoying that I let her keep asking to see what were the questions. Mostly about AppArmor and Snap.
> Anyway, I will use this post to tell you I applied to a job at Canonical once and they made me have an interview
Like I said in the other post, they are kind of known for posting ghost jobs and trolling people who need work.
Like I said in the other post, they are kind of known for posting ghost jobs and trolling people who need work.
@anokasion @cjd Oh, it's not related to EFI. Basically the EFI partition usually just has the bootloader and things like that, the bootloader config, right, and that points at the boot partition, the boot partition will have the kernel and initrd. It doesn't usually need to be a separate partition.
> they made me have an interview with an AI
This is so fucking stupid. Whoever puts shit like that in place should be slapped.
> they made me have an interview with an AI
This is so fucking stupid. Whoever puts shit like that in place should be slapped.
Remember when Canonical hired a monster who was convicted of raping his own sister, admitted they were informed of his sex offender status, and then defended the hiring decision after the public found out because he'd "served his debt to society"? Quite the fascinating ethical framework these "people" have.
Well look at firefox for instance, where do they get all of their money from? Google (Chrome)... It gets a little worse every year and you never hear about Google having any negative opinions about that.
It doesn't take a massive amount of imagination to suppose that perhaps possibly they're doing exactly what they're supposed to do.
It doesn't take a massive amount of imagination to suppose that perhaps possibly they're doing exactly what they're supposed to do.
@p @cjd that makes sense, I must have the kernels in another partition (can you have it on your Linux main one though?) because they began to have an important filesize *I think* (50-150mb?) - basically by what you told, I think I have a 16mb boot partition (the EFI one) with the bootloader, another partition with the kernels and stuff, another with the main system ("/") and another for my $HOME. I should check it on gpart later. Thanks for the explanation.
@anokasion @cjd
> (can you have it on your Linux main one though?)
Yep! I don't do a separate /boot partition.
> another with the main system ("/") and another for my $HOME
Always good to have a separate /home partition. I usually do a root partition and another partition of the same size so I can update the system on one of them and then keep the other as the upgrade target/old root. So I wanna upgrade, I don't have to turn off the box to do the system update: I just rsync the current root and then chroot into it, do the upgrade, pop the chroot, set the other partition as the new root (bootloader, /etc/fstab), then I can either reboot and be in the new system immediately or I can chroot into it and start sshd and everyone that ssh's in gets the new server.
> (can you have it on your Linux main one though?)
Yep! I don't do a separate /boot partition.
> another with the main system ("/") and another for my $HOME
Always good to have a separate /home partition. I usually do a root partition and another partition of the same size so I can update the system on one of them and then keep the other as the upgrade target/old root. So I wanna upgrade, I don't have to turn off the box to do the system update: I just rsync the current root and then chroot into it, do the upgrade, pop the chroot, set the other partition as the new root (bootloader, /etc/fstab), then I can either reboot and be in the new system immediately or I can chroot into it and start sshd and everyone that ssh's in gets the new server.
@Suzu @p @cjd Even there you aren't free from the memery of Debian and Canonical.
Everyone hates me for this, but all I need to do to upgrade between releases on my Loonix servers is install two packages, run 2 commands, one of which checks whether my current system configuration is even valid on the next release, maybe update said configuration and reboot. 5 minutes of my time and I have to do it only once every 10 years.
Everyone hates me for this, but all I need to do to upgrade between releases on my Loonix servers is install two packages, run 2 commands, one of which checks whether my current system configuration is even valid on the next release, maybe update said configuration and reboot. 5 minutes of my time and I have to do it only once every 10 years.
@mint @p @cjd The comments are classic Loonix discourse as well...
image.png
image.png
image.png
gnujak-windows-linux-skill-issue.png
image.png
image.png
image.png
gnujak-windows-linux-skill-issue.png
@hakui @Suzu @p @cjd It is paid-only by default :D Unless you use derivatives like: https://fluffytail.org/objects/40249859-3748-46e7-ba3b-0176b57f1e6b Which kinda exist at RH's mercy.
@mischievoustomato @Suzu @p @cjd @hakui GLM 4.7, Kimi 2.7 and GLM 5.2 are all mediocre at RPM since the documentation does not reflect reality. Every distro has their own set of macros for packaging stuff and they also change by version.
@p @Suzu @cjd @hakui Yeah, not as unusual in an enterprise setting for making sure a company actually pays for what they are using. But it's a really bad joke for personal stuff.
At least the derivatives aren't maintained by RH in the background like with CentOS before its inevitable death, and don't entirely depend on RH either. All three major ones kinda went their own ways: ABI compat only, full source rebuild, and whatever Larry Ellison is doing. Only one of them needs RH to publish full sources.
At least the derivatives aren't maintained by RH in the background like with CentOS before its inevitable death, and don't entirely depend on RH either. All three major ones kinda went their own ways: ABI compat only, full source rebuild, and whatever Larry Ellison is doing. Only one of them needs RH to publish full sources.