Magiilaro

When I got into the company I was allowed to use Linux. But a few years ago the company was bought and merged with a much bigger company and the new IT policy made Windows mandatory.

I have a Postscript 3 compatible ipp network color laser printer for about 15 years now and it works without any issues with Linux, way better then it does from Windows. So I never understood way they say that printing is cumbersome with Linux.

Unfortunately many of the routers provided by ISPs I have seen where not configured that way by default. They only used NAT as firewall, so without configured port forwarding nothing could be reached with IPv4. But for IPv6: If you know the IPv6 for any system on the local network it is free available on all ports. It is the first thing I check when someone asks me to check their network or configure their internet, and only Fritz!Box have a sane default for IPv6 (but to be honest my other experiences are mostly with shitty Vodafone and german Telekom routers so it is a very limited set, and I really hope that most others are better.)

Yes, but exactly that was/is the issue of this bug. cups-browsed was attaching itself to every available IP on the system. And cups-browsed can’t only be bind to localhost, it would defeat the whole purpose of that tool. For it to be able to find other printers in the network it needs to be bound to a non-localhost-IP address. So, not much to sandbox

No port forwarding needed when the ISP provides a proper IPv6 subnet. Normal IPv6 router advertisement will then provide a public reachable address for every IPv6 capable device.

But with the size of IPv6 it makes searching for that not really easy, so it only a small attack vector.

I have cups (but not cups-browsed) installed, but I only start the service when I need to print something a few times a year. Until then it is only a binary sitting in a folder, nothing more.

I don’t know if I would like to have my personal data that I needed to print out on any system in a print shop. Printers and Copy machines in print shops often have internal HDD where the files are stored for caching reasons, often for months or even years (depending of the size of the HDD and how much the device is used) until some internal cleanup process deletes them.

I fear that the situation will not be better after nearly a decade.

Just read http://judecnelson.blogspot.fr/2014/09/systemd-biggest-fallacies.html and I see now that I was in error with my claim. So yes, I accept all the down votes in shame.

You do know that systemd is modular and every part of it does only one thing? Don’t see a real conflict with the Unix Philosphy

Sounds like you want savapage https://www.savapage.org/

It by default runs on its own port but that is easy fixable with a reverse proxy.

The structure is changing, many distributions already are merging more and more of the duplicated subdirectories in /usr/ with the counterparts in / but it takes time to complete that and at the moment those subdirectories are often still there but as symlinks to be compatible with older software (and sysadmins).

Yes, that is true. I was speaking in the context of very early Unix/Linux before initrd was a thing.

And I still don’t know what’s the point in separating /bin, /sbin, /usr/bin and /usr/sbin.

This goes back to the olden days when disk space was measured in kilo and megabytes. /sbin/ and /usr/sbin have the files needed to start a bare bone Unix/Linux system, so that you could boot from a 800kb floppy and mount all other directories via network or other storage devices as needed.

It gets even more complicated nowadays because most DE will mount removable drives somewhere in folders like /run/$USER/

Mostly historical reasons, /home was often a network mounted directory, but /root must be local.

And only regular users have their home in /home

Well then the answer will most likely be: because they can and want to do it.

Maybe because that person uses systemd everywhere else and just doesn’t want the overhead of maintaining two different init systems.

There is no indication that anyone will be pruning systemd from distros in the near or far future. Systemd is here to stay and if anything it will only spread into more and more places as can be seen with projects like this.

Yeah, they should have used the names in alphabetical order, like Ubuntu with their codenames.