If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
Awesome, looking forward to putting the "you forgot to mention GNU" issue to rest.
And then there will only be Linux left. I doubt systemd devs will request a name like systemd/Linux since systemd was written specifically for Linux anyway.
And then there will only be Linux left. I doubt systemd devs will request a name like systemd/Linux since systemd was written specifically for Linux anyway.
Don't underestimate the assholeness of the systemd developers.
No, they wouldn't want it to be called systemd/Linux, they would just pull Linux into their repository (as they did with udev) and simply call it just systemd.
Don't underestimate the assholeness of the systemd developers.
No, they wouldn't want it to be called systemd/Linux, they would just pull Linux into their repository (as they did with udev) and simply call it just systemd.
I would cut out the name calling. It makes you more of what you call other people and devalues whatever technical arguments you may have.
systemd didn't just pull udev into its repository and result isn't not simply called systemd. The udev maintainer is one of the primary systemd developers and the code repository was merged to shared core functionality with full agreement of the developers involved and the result is called systemd-udev.
Distributions like Debian even have split the package off and Fedora is doing the same thing recently as well.
Great! Glad to get rid of one of the stupidest mis-features that Linux was unfortunate to inherit.
Actually, I've got fed up of these "your /etc/mtab is possibly stale" warnings from userland tools when it happened my rootfs is readonly (rather common occurence in embedded, etc). At the end of day tools were asking to use /proc/mounts to see REAL list. Hopefully now tools would just use it on their own and GTFO with silly complaints. Directing user to do things right is lame. Do a right thing in tools in first place, dammit. Sticking to (potentially stale) file in usual filesystem when you can see REAL state of things in procfs... isn't best idea ever for sure.
Whatever, but being unable to view proper state of mounts by using usermode tools if my rootfs is RO is a bullshit. And its great they all are in mood to fix it.
Last edited by SystemCrasher; 18 November 2015, 09:10 PM.
Comment