The Linux Thread - The Autist's OS of Choice

[Slav Power]

I suspect that what actually happened was someone corrupted a flash drive because they suddenly removed a device with a funny filesystem.

Yeah, a funny filesystem. Was it that? Was it not? Who knows, most probably I was wrong, all I know is that this shitstorm started because of this quote:

I understand that Stockholm syndrome comes with being a Linux user, yes? If Windows did this, I wouldn't go "oh well, can't be mad at it, I'll just avoid doing that", I would go "why the fuck do you do this you piece of shit you're supposed to work".

If Linux users stopped being this forgiving about their OS doing asinine shit for once and actually complained like a functional human being, it would finally be a good contender for a Windows replacement.

Where the topics mentioned beyond that was Debian vs Devuan, file managers, and file storage shit. But all of that perfectly technical and on-topic discussion got overshadowed because I poked fun at the Stockholm syndrome thing.

So I'll keep that in mind that it's the best way to cause a shitstorm in a Linux thread. Make fun of Linux users and mention Windows as the superior OS. Of course it's fine when the roles are reversed, isn't it?

 

[Friendly Primarina]

MAME

Don't tell me this is the entire MAME romset? I mean, it's your life and everything but Jesus Christ.

RAID0 was also intended to increase read/write speed when drives were much slower. So if you had four drives in a RAID0 setup you could write 25% of a file to each drive and quadruple your read/write speed, at the cost of having ALL files in the data pool corrupted if a drive is lost.

I always wondered what the point of that was. Now I know, thanks.

 

[DavidS877]

Windows as the superior OS

We all know which OS is superior.

TOPS-20

 

[Sperg Coalition]

So I'll keep that in mind that it's the best way to cause a shitstorm in a Linux thread.

Ironically you are ending up to be the major autist here. In the linux thread. And you are a Windows user, I even agreed on some of your points but at this point I really don't know what to tell you man.

 

[Susanna]

Feels good to be a Mac user first, Linux user second. My primary OS just works, and it’s the OS of choice for people who actually work with computers and know what they’re doing, such as software developers. My secondary OS is Linux, which has a bunch of extra features but requires me not to be a retard about unplugging thumbdrives.
Unlimited looking down on windows babies from both directions.

 

[DavidS877]

Don't tell me this is the entire MAME romset? I mean, it's your life and everything but Jesus Christ.

MAME is a small part, the CHDs are sort of large though:

399M    ./MAME 0.249 ROMs (bios-devices)
72G    ./MAME 0.249 ROMs (merged)
82G    ./MAME 0.249 Software List ROMs (merged)
924G    ./MAME 0.249 CHDs (merged)
2.6T    ./MAME 0.249 Software List CHDs (merged)
3.7T    .

TOSEC-ISO comes in at 3.3T

 

[demicolon]

I've been called to the blackboard regarding the pendrive issue, so let me quote a person an order of magnitude more intelligent than me about it:

File descriptors and network sockets cannot be forcibly closed - it's indeed unsafe to remove USB sticks without unmounting them first as it leads to stale mount points, and in certain cases to oopses and crashes. For the same reason you cannot modify your partitions table and resize/move the root partition on the fly.

Link to the full article
All I'm saying is that, under Linux, many times whenever I'd just plug out the pendrive without manually ejecting it first on software level, the pendrive would be only good for formatting later. Data was lost, device was reusable.

 

[Sperg Coalition]

I've been called to the blackboard regarding the pendrive issue, so let me quote a person an order of magnitude more intelligent than me about it:

Link to the full article
All I'm saying is that, under Linux, many times whenever I'd just plug out the pendrive without manually ejecting it first on software level, the pendrive would be only good for formatting later.

That answers the question of having corrupted data and/or partitions but it doesn't answer if the device can get bricked (as in, hardware failure).

 

[Betonhaus]

Isn't that just NTFS superiority?

 

[demicolon]

That answers the question of having corrupted data and/or partitions but it doesn't answer if the device can get bricked (as in, hardware failure).

Hardware failure: didn't happen to me.

 

[Friendly Primarina]

MAME is a small part, the CHDs are sort of large though:

399M    ./MAME 0.249 ROMs (bios-devices)
72G    ./MAME 0.249 ROMs (merged)
82G    ./MAME 0.249 Software List ROMs (merged)
924G    ./MAME 0.249 CHDs (merged)
2.6T    ./MAME 0.249 Software List CHDs (merged)
3.7T    .

TOSEC-ISO comes in at 3.3T

Just the thought of it, I guess. That must be tens of thousands of games

 

[DavidS877]

Isn't that just NTFS superiority?

Any Journaling FS should work better(XFS, EXT4, NTFS, etc). But for interoperability most flash sticks are formatted FAT/FAT32/exFAT which does not take kindly to being hot removed as a previous poster mentioned.

 

[Slav Power]

Feels good to be a Mac user first, Linux user second. My primary OS just works, and it’s the OS of choice for people who actually work with computers and know what they’re doing, such as software developers. My secondary OS is Linux, which has a bunch of extra features but requires me not to be a retard about unplugging thumbdrives.
Unlimited looking down on windows babies from both directions.

Make a macOS general so that both Windows and Linux users can circlejerk in it about how much better their OS' are because they don't get locked into a walled garden just to use them.

I've been called to the blackboard regarding the pendrive issue, so let me quote a person an order of magnitude more intelligent than me about it:

Link to the full article
All I'm saying is that, under Linux, many times whenever I'd just plug out the pendrive without manually ejecting it first on software level, the pendrive would be only good for formatting later.

So I was the retard that misunderstood the posts and it's just another issue with file corruption and not device bricking where you should do safe removals both on Windows and Linux anyway, got it.

Isn't that just NTFS superiority?

This seems to be more about how Linux handles drives regardless of the file system. NTFS has that issue where files cannot be modified when they're in use, which is why to this day Windows updates require a system restart to update system files before the system is fully running, and Linux can update while running.

 

[demicolon]

I was the retard calling file corruption "bricking". Many times Windows 10 would fuck up with automatic updates, because I have better things to do than wait half a day, after waiting all night, for Windows to finish so I'd forcibly restart, or Internet would lose connection because Poland, and called it bricking but obviously the hardware was fine.

Feels good to say it. Brick.

 

[Sperg Coalition]

So I was the retard that misunderstood the posts and it's just another issue with file corruption and not device bricking where you should do safe removals both on Windows and Linux anyway, got it.

It was exactly that, a simple misunderstanding about a term that got misused to actually indicate data corruption instead of hardware failure. Just to be safe though, it's better to cleanly remove devices in any operating system to eliminate potential data corruption problems.

 

[Susanna]

Windows updates require a system restart to update system files before the system is fully running, and Linux can update while running.

While it’s true that Linux can update, including loading a new kernel, without a reboot, it’s sure to cause a panic unless you halt the affected daemons beforehand. Changes to libraries can seem fine for days, but then an old but still running browser loads the new java.o or whatever and crashes. Rebooting is a better and faster solution 99% of the time.
What isn’t okay is Windows Professional, ostensibly for powerusers, deciding to reboot at random and without input from the user. If I start a big sim Tuesday afternoon with the expectation that it’ll be done when I return to office Wednesday morning, and I’m instead greeted by the login screen and bejeweled or whatever having been reinstalled, that’s absolutely unacceptable.

I was the retard calling file corruption "bricking". Many times Windows 10 would fuck up with automatic updates, because I have better things to do than wait half a day, after waiting all night, for Windows to finish so I'd forcibly restart, or Internet would lose connection because Poland, and called it bricking but obviously the hardware was fine.

Feels good to say it. Brick.

Blame windows for forcibly autoinstalling updates at inconvenient times, not for the system being unrecoverable if you literally unplugged it out of rage mid-update.

Windows Home should auto update each night, that’s fine and good for everyone. But the professional version must be designed with the expectation that sometimes computers are left running overnight because paying an engineer to sit at an unusable workstation for two hours is not good business sense.

 

[AmpleApricots]

man, and I feel bad for my walls of text sometimes.

Journaling file systems fare better because they have an easier time rolling back to a known good state, which usually can be detected via unclean unmounting. (existance of a flag that wasn't cleared, FAT has this too, that's how the computer can tell) Caching is done here too and data loss is still possible.

I did not interpret bricking literally and interpreted by context, it's a given that you usually cannot brick an usb device by hotplugging it, if you could that would be a fundamental problem in the electric design of the invovled devices, not an OS problem.

 

[DavidS877]

But the professional version must be designed with the expectation that sometimes computers are left running overnight because paying an engineer to sit at an unusable workstation for two hours is not good business sense.

The only reason for Windows Professional is to set all the GPOs to disable automatic Windows Update

 

[Sperg Coalition]

Windows Home should auto update each night, that’s fine and good for everyone. But the professional version must be designed with the expectation that sometimes computers are left running overnight because paying an engineer to sit at an unusable workstation for two hours is not good business sense.

If you want these features you need to use Professional or an Enterprise version of Windows which I don't know if a small business can afford a license for, assuming they don't simply pirate it and then you need to modify the group policy settings irc.

 

[demicolon]

I doubt even Windows Ultra SSJ Professional Fresh Lemon Smell lets you disable updates at this point. With Linux, you get what you pay for but with Windows you pay to tell customers at 8.00 AM to come later after your system finishes updating or risk losing half 'a year worth of data.