You are not logged in.
Pages: 1
http://lwn.net/Articles/490413/
I had a long post about this, but the forum ate it.
Suffice to say I'm not a hotshot programmer, so my opinion doesn't really count; but I have some misgivings about this. Specifically that it seems to be yet another step towards Linux-only-ness on the open source desktop, which IMO is a step in the wrong direction.
But anyway... What do you think of the code merger?
Offline
I wouldn't be surprised if e.g. Ubuntu fork udev.
Offline
They'll still stay separate. They *need* a standalone udev, for initramfs. I'm not a fan of the everything-including-the-kitchen-sink systemd, but udev is ok. So as long as there's a standalone udev, I'm cool.
Offline
Suffice to say I'm not a hotshot programmer, so my opinion doesn't really count; but I have some misgivings about this. Specifically that it seems to be yet another step towards Linux-only-ness on the open source desktop, which IMO is a step in the wrong direction.
IMO, there is no such thing as `Linux-only-ness' in an Open Source environment. Everything is portable on the source code level by definition, so everyone is free to copy the stuff relevant to systemd from the Linux Kernel in order to support it. Now, the BSD people, for example, have their reasons for not doing that, but that's no excuse for preventing the Linux crowd from moving in another direction.
But anyway... What do you think of the code merger?
I don't think it's all that interesting in itself. It's more or less a matter of logistics/maintainability.
Last edited by csn (2012-04-16 23:06:23)
Offline
IMO, there is no such thing as `Linux-only-ness' in an Open Source environment. Everything is portable on the source code level by definition, so everyone is free to copy the stuff relevant to systemd from the Linux Kernel in order to support it.
Don't quote me on it, but I'm pretty sure that is usually much easier said than done.
(And it also entails duplication of effort.)
Offline
Quote from the original article:
After udev is merged into the systemd tree you can still build it for usage outside of systemd systems, and we will support these builds officially.
So other than the fact that this might push the use of systemd a bit, I don't really see this as being too much of an issue. You might have to pull the full systemd tarball in order to build udev from it, but that shouldn't a big deal.
Burninate!
Offline
So other than the fact that this might push the use of systemd a bit, I don't really see this as being too much of an issue.
More than its already pushed by most of the 'big' distros adopting or planning to adopt it? Not sure how being in the same tarball is going to push the adoption rate any more than it currently is.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
More than its already pushed by most of the 'big' distros adopting or planning to adopt it? Not sure how being in the same tarball is going to push the adoption rate any more than it currently is.
True. I was just trying to say that if for whatever reason someone doesn't want to make the move towards systemd; this change is not something that'll "force" them to do so.
Burninate!
Offline
I've removed systemd on some systems because it's just not what I want/need, and because sometimes it just doesn't behave the way it should without manual intervention... like with intel raids...
*sigh*
You know you're paranoid when you start thinking random letters while typing a password.
A good post about vim
Python has no multithreading.
Offline
Personally i feel systemd ( and pulseaudio) don't add anything I NEED/WANT to my system.
In my opinion Linux basic philosophy has always been about : having the right tool for the job.
Both systemd and pulseaudio seem to be jack-of-all-trades types of software, and i prefer specialist tools.
Systemd seems to be replacing consolekit, now they add udev to systemd.
Guess it's time for me to search for alternatives.
Last edited by Lone_Wolf (2012-04-17 11:46:59)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Well, given how it's even been copy/pasted here that udev still has a separate build target, forgive me for not entirely sharing your knee-jerk sentiments.
Also nice off-topic jab at pulse and the pointless waving of the Unix philosophy. Wouldn't be a hate thread without it ^^
Last edited by ZekeSulastin (2012-04-17 13:57:30)
Offline
Pages: 1