Systemd 256.1 Fixes "systemd-tmpfiles" Unexpectedly Deleting Your /home Directory

[sophisticles]

World runs on Linux and the code is open out there. You are so obviously stupid to claim something so obviously wrong. Seek help, seriously.

How about 20 Euros to get me started? I'll settle for 15 for a sandwich.

Do you know what is "obviously stupid"?

Statements like "world runs on Linux", what does that even mean?

Does relativity, conservation, evolution, Newtonian dynamics, rotational inertia, all scientific, economic and medial principles run on Linux?

Of do you mean that the world's computers run on Linux?

Problem is the world doesn't have computers, people do and there is no way to quantify how many computers are using Linux based OSes or which Linux based OS they are using.

If you found out that the vast majority of computers running Linux were running Red Hat 7. would you switch to RH7?

As I said, you lack the intelligence, knowledge, and experience to debate me.

[sophisticles]

Haven't you heard? This guy is a Certified™ UNIX™ Sysadmin™ with a university degree™!

I bet he is just so much salty that his education and career investments turned out to be completely worthless that he's got sodium poisoning. You know, when you spend time and money to partake in the sacred knowledge, and then it turns out the sacred knowledge (and the subject of such knowledge) is just an obsolete piece of junk completely supplanted by something freely available as a commodity, it tends to mess with your world view.

You do realize that as a Unix Sys Admin I am qualified to administer Linux systems and have been offered jobs doing so.

The main problem right now is that the market is overly saturated with many people with lots of certifications and experience and the reality is that you don't need that many system admins, once a network is up and running, unless there us a hardware failure, automated systems can keep it humming along just fine.

Add to that people that have managed to quadruple dip, I know a guy making almost a quarter million a year, he is working 4 remote jobs at the same time from his home as a Linux system admin, basically runs cron jobs and makes sure the system is constantly online.

He has 4 laptops remoted into a 4 different companies' network, and he "administers" while playing video games at home.

It's killing the demand for admins.

Still doesn't change the fact that Linux is a half-assed OS.

[sophisticles]

Which good old days are you speaking of when you were somehow unable to get GNU/Linux to do productive work for you?

It depends on what "productive work" you are talking about but I am referring to the days when basic drivers didn't exist for most hardware and you were lucky if you could install Linux without a kernel panic.

On most motherboards you were lucky if you could get the onboard NIC working and to this day for some NICs you need a Windows driver wrapper to get it working.

Forget about having remote meetings, as audio and video were barely functioning and my personal favorite, the security was worse than Windows 95.

I remember smoking root by bypassing LILO and creating cron jobs that ran fork() bombs that brought entire networks down.

I also remember the first time i went to college, all the computers were running BSD, Red Hat, SCO or Suse, they were all networked and for fun I would telnet into someone's computer as they were working on a project and issue either a shutdown or reboot command that would make them lose all their work, and I would sit there an laugh as they lost their minds.

Yeah, it was a great OS, very dependable, I wonder why it never achieved greater market penetration?

Oh, that's right, because it's a toy created by nimrods.

[mrg666]

You do realize that as a Unix Sys Admin I am qualified to administer Linux systems and have been offered jobs doing so.

The main problem right now is that the market is overly saturated with many people with lots of certifications and experience and the reality is that you don't need that many system admins, once a network is up and running, unless there us a hardware failure, automated systems can keep it humming along just fine.

Add to that people that have managed to quadruple dip, I know a guy making almost a quarter million a year, he is working 4 remote jobs at the same time from his home as a Linux system admin, basically runs cron jobs and makes sure the system is constantly online.

He has 4 laptops remoted into a 4 different companies' network, and he "administers" while playing video games at home.

It's killing the demand for admins.

Still doesn't change the fact that Linux is a half-assed OS.

I don't believe you are a sys admin. I challenge you to put copy of your diploma and employment information here. I will send your stupid posts to your employer and verify if you are this incompetent over there too. Can you do that, give us your employer and manager's contact information? If not, stop claiming credentials that nobody asked.

[duby229]

I find it incredibly hard to believe too. He'd get fired on his first day at the job.

[anda_skoa]

I know this question has been asked earlier today, but it's worth asking again - does it make any sense at all to be giving your init system a command that specifically destroys your home directory?

Nobody has even suggested that, let alone implement it.

Maybe you got confused by the name of the program that indicates it comes from the same software project as a well known init does.

A common misunderstanding as many people have not yet realized that community based software organisations can have more than one product the same way software companies have.

It really seems that systemd-homed should not be part of systemd at all - it should be a completely separate program with differently named commands.

It is a separate program, its name merely indicates a vendor relation.

Like when you have Microsoft Word and Microsoft VisualStudio. The common part of the name indicates they are both from the same vendor.

It is quite understandable that this is difficult to grasp as FOSS communities often start with a single product and much later on expand their portfolio.

Other communities had to go through this time of misunderstanding as well.
Back in the day of Mozilla Navigator a lot of people just called it "Mozilla" and it took quite some time (and rebranding of the browser) for people to realize that Mozilla was the "vendor name" and Firefox was the "product name".

Even companies can run into this.
For example Oracle is both the vendor name and the name of their main product.
And people get confused when they read Oracle VirtualBox and, similar to your question above, ask themselves "does it make any sense to give your database a UI to run virtualized operating systems".

[Weasel]

Well, that ignorant dumbass informed the other users of the most popular distro that they are not at risk and they will not be. I am sure this is important to know. What was the point of your post, whining little weasel?

What the fuck has your pathetic little distro to do with the systemd devs you praised?

[duby229]

Nobody has even suggested that, let alone implement it.

Maybe you got confused by the name of the program that indicates it comes from the same software project as a well known init does.

A common misunderstanding as many people have not yet realized that community based software organisations can have more than one product the same way software companies have.


It is a separate program, its name merely indicates a vendor relation.

Like when you have Microsoft Word and Microsoft VisualStudio. The common part of the name indicates they are both from the same vendor.

It is quite understandable that this is difficult to grasp as FOSS communities often start with a single product and much later on expand their portfolio.

Other communities had to go through this time of misunderstanding as well.
Back in the day of Mozilla Navigator a lot of people just called it "Mozilla" and it took quite some time (and rebranding of the browser) for people to realize that Mozilla was the "vendor name" and Firefox was the "product name".

Even companies can run into this.
For example Oracle is both the vendor name and the name of their main product.
And people get confused when they read Oracle VirtualBox and, similar to your question above, ask themselves "does it make any sense to give your database a UI to run virtualized operating systems".

How is it packaged and distributed? If it's part of the systemd package then it is part of systemd.

Which btw is exactly systemd's biggest fault. It's a black hole that sucks in everything no matter what it is or how it might related. It devours projects indiscriminately without caring at all whether or not it has anything whatsoever even remotely to do with systemd... Almost NOTHING in the systemd package is systemd and basically all of it is mostly or even completely unrelated.

[andyprough]

It depends on what "productive work" you are talking about but I am referring to the days when basic drivers didn't exist for most hardware and you were lucky if you could install Linux without a kernel panic.

On most motherboards you were lucky if you could get the onboard NIC working and to this day for some NICs you need a Windows driver wrapper to get it working.

I for one have never had this issue - I've always purchased hardware that was known to run well with GNU/Linux. We used to have HCL's - 'hardware compatibility lists'. If a known compatible NIC wasn't working then the NIC was probably bad. 3M always had reliable NICs if I recall correctly. I think we used to keep a bin full of them at any place I ever worked.

[Teggs]

systemd-microsoftdevs --purge isn't in the manual at all, but they should run it anyway. For science.