You are not logged in.
I like systemd in general,one thing i dislike is kind of randomness in boot initialization - sometimes is just 9 sec another time13 and once for boot it can't find my root partition.
That third random event maybe is related to my schizophrenic bios,or just my hdd is simply go nuts - it's almost 6 years i own it.
But initscript never whining about this so it's MISTERY.
Offline
For a long years Archlinux WAS my favorite linux distibutive. Because it was simple and powerfull, flexible configurabe. It was really best choise for home and for server! And now, archlinux turning into ....even not Unbutu, Arch turning into Windows!!
RIP, beloved ARCH!
P.S.: I WISH LENNART POETTERING TO GO TO HELL!!!
You can still use it, just recompile packages depending on systemd. It is still easier than LFS(I prefer that one).
I agree that RH wants to turn linux into tightly coupled bloatware....
(He is not the source of that, he's just a RH's toy....)
zb3
Offline
Why are you feeding the troll? And your comments about Red Hat are unwelcome as well:
https://wiki.archlinux.org/index.php/Fo … ng_Systems
Offline
I like systemd in general,one thing i dislike is kind of randomness in boot initialization - sometimes is just 9 sec another time13 and once for boot it can't find my root partition.
That third random event maybe is related to my schizophrenic bios,or just my hdd is simply go nuts - it's almost 6 years i own it.
But initscript never whining about this so it's MISTERY.
Use the tools provided to examine/analyse/debug your issue - details in the man and wiki pages.
Offline
In describing the steps for shifting to systemd the wiki clearly covers rc scripts. I don't recall anything pertaining to xinetd scripts being mentioned as a part of this process. However, I have seen some mention elsewhere of xinetd in the context of systemd, as well as in an earlier comment by brain0 regarding the clean up of unneeded scripts [NoExtract=/etc/rc.d/* /etc/xinetd.d/*]. Can anyone tell me if I've missed anything with regard to xinetd scripts that need to be done before cleaning them out? Thanks.
Offline
I've read that thread, but nobody seems to have stepped up.
I could easily install a VM for testing initscripts-git and such, but it appears arch projects mailinglist is the same as arch-dev-public :
read-only for non-devs .
Hard to contribute without being able to post to that mailing list ....
Sidenote :
There are several things i dislike about systemd, especially the things they have taken over from other projects (or intend to take over) like udev, ck , polkit, display managers .
Systemd has many good things in it's design, if systemd development had focused on making a replacement for PID1 as was the original intention instead of becoming a session manager for both kernelspace AND userspace , i'd probably be a supporter of it.
Last edited by Lone_Wolf (2012-10-17 11:26:42)
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
In describing the steps for shifting to systemd the wiki clearly covers rc scripts. I don't recall anything pertaining to xinetd scripts being mentioned as a part of this process. However, I have seen some mention elsewhere of xinetd in the context of systemd, as well as in an earlier comment by brain0 regarding the clean up of unneeded scripts [NoExtract=/etc/rc.d/* /etc/xinetd.d/*]. Can anyone tell me if I've missed anything with regard to xinetd scripts that need to be done before cleaning them out? Thanks.
Systemd can start services on demand and obsoletes most of the xinetd functionality. I have xinetd uninstalled now. For example, I use xinetd for git now:
systemctl enable git-daemon.socket
This is basically the same as enabling the git-daemon xinetd file.
Offline
I could easily install a VM for testing initscripts-git and such, but it appears arch projects mailinglist is the same as arch-dev-public :
read-only for non-devs .
The list is arch-projects, and anyone who subscribes to it can post.
Sidenote :
There are several things i dislike about systemd, especially the things they have taken over from other projects (or intend to take over) like udev, ck , polkit, display managers.
I don't see any takeover of display managers or polkit. Systemd absorbed udev and replaced consolekit with logind.
Offline
Thatis the point, why should systemd absorb udev? Earlier, was it like this?
Satyam eva jayate
Registered linux user #535257
Offline
Hasn't this already been covered? http://lwn.net/Articles/490413/
I thought you left anyway? Why are you sending me spam PMs?
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Thanks brain0, I'm getting the picture now.
Offline
I'm confused about when we 'officially' move to systemd. I presumed now that new installations are using it that we had switched but I just had a thread closed as we haven't officially switched yet.
Offline
We already switched : systemd-sysvcompat and systemd are in core, while "initscripts" is in extra. what else? We're waiting for gnome3.6 to move in testing and then in extra, with all of its rebuilt packages, such as networkmanager, polkit etc etc, with systemd-only support. Then will be switched at 100%.
Offline
Is there a rough estimate of how long it will take to get gnome3.6 to extra?
Offline
Is there a rough estimate of how long it will take to get gnome3.6 to extra?
Offline
when it ready -Allan
But I ask the upcoming are the neede for a pure systemd right or now (alongside removing initscripts) what is the others thinks that I can make for make a Mostest pure (for now) systemd system
Well, I suppose that this is somekind of signature, no?
Offline
I hope the consolekit removal happens rather sonner than later. Locally, I already rebuilt the last user of consolekit (kdebase-workspace) without consolekit support, and my polkit (still patched for hybrid consolekit and logind support) does its job well.
In our staging repository, consolekit support is removed everywhere (somewhat between 10 and 20 packages) and this will likely move when gnome 3.6 moves along with the new polkit.
FYI, Tom tried to get hybrid consolekit/logind support upstream into polkit and they refused. This means that - short of forking polkit - we can't do anything to support consolekit any longer.
Offline
I'm confused about when we 'officially' move to systemd. I presumed now that new installations are using it that we had switched but I just had a thread closed as we haven't officially switched yet.
well, as the systemd and old sysVinit scripts can be installed side-by-side, there is no "we" and it's on users when they decide to switch. the change is that systemd is the default init system and will be supported by the devs in the future, while the old init scripts won't be supported and will be removed when the maintainer of given pkg decideds it's the right time to do so...
but if you want date, it's probably 14th of August http://mailman.archlinux.org/pipermail/ … 23389.html
core i5 4590, x86_64, nvidia 970
Offline
Lone_Wolf wrote:I could easily install a VM for testing initscripts-git and such, but it appears arch projects mailinglist is the same as arch-dev-public :
read-only for non-devs .The list is arch-projects, and anyone who subscribes to it can post.
You are correct, i was mislead by the "no user discussion" part on the arch-projects page :
About arch-projects
English (USA)Development discussion, patches and pull requests for the Arch Linux projects: initscripts, netcfg, devtools, dbscripts.
No user discussion!
It took me a few tries to figure out i needed to use certain tags in the subject line, but that's all.
Thank you for pointing this out.
[ADDED]
DISCLAIMER
Everything below that is not quoted from other posters is my PERSONAL opinion.
While i do believe i am right and will search for relevant quotes to back my opinion , until i do you shoull treat it as :
a purely personal opinion
[/ADDED]
Lone_Wolf wrote:Sidenote :
There are several things i dislike about systemd, especially the things they have taken over from other projects (or intend to take over) like udev, ck , polkit, display managers.I don't see any takeover of display managers or polkit. Systemd absorbed udev and replaced consolekit with logind.
In the past days i've read all blog posts about systemd by mr Poettering, including the comments.
From that i got a strong impression that replacing gdm/kdm/slim/xdm and polkit are next on the (possibly fictional) list of "things to add to systemd"
@wormzy :
In the comments to the blog posts mr poettering did mention that any new additions/improvements to udev would be accepted only if they benefitted systemd.
He also named the main reason to absorb udev into systemd : to force more people to switch to systemd as systemd acceptance was not progressing fast enough.
sorry, can't find the exact comments where this was said by him.
Combining both statements imo translates to :
Udev is now systemd's property, and all non-systemd use of udev must stop asap.
Last edited by Lone_Wolf (2012-10-17 22:39:36)
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
@Lone_Wolf, I think that you are wrong about the "non-systemd use of udev must stop asap". I have read in numerous places that udev will still be supported on its own, but that it will not be improved without the benefit of systemd. So it will still be entirely possible to still use udev without systemd, and it will not even have to be hacked into submission.
Also, I would really be interested in seeing the post by Lennart stating that his intent in merging systemd with udev was the "force more people to switch to systemd". If you find that specific blog post/comment thread, please post a link.
Offline
From that i got a strong impression that replacing gdm/kdm/slim/xdm and polkit are next on the (possibly fictional) list of "things to add to systemd"
I don't think adding polkit to systemd makes any sense, nor have I heard anyone talk about that. Moreover, systemd makes extensive use of polkit, which itself is under active development. Do you have a reference to this polkit discussion?
There are no plans (afaik) to take over the job of gdm/kdm/.... Do you have a reference? What you might have seen is that systemd will be able to take over the job of the session manager from xfce-session/kdeinit/"whatever they are all called". Which will be awesome when it finally gets done.
In the comments to the blog posts mr poettering did mention that any new additions/improvements to udev would be accepted only if they benefitted systemd.
I'm pretty sure you must have misread that, or are misrepresenting the statements. Besides, udev is mostly being taken care of by Kay, not by Lennart. Without a reference it is hard to comment though.
He also named the main reason to absorb udev into systemd : to force more people to switch to systemd as systemd acceptance was not progressing fast enough.
Please provide a reference. There is no way this is a correct quote.
sorry, can't find the exact comments where this was said by him.
If you want to be taken seriously I suggest you don't make highly controversial/implausible claims without being able to provide the references...
Offline
Continuing from https://bbs.archlinux.org/viewtopic.php?id=150855 which is closed.
If syslog-ng is removed from base shouldnt the same be done for logrotate? I dont think its capable of working with systemd's journal, is it?
edit: fix typo
Last edited by dolby (2012-10-17 22:06:21)
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
What you might have seen is that systemd will be able to take over the job of the session manager...
For example, in this interview (10th question).
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
tomegun wrote:What you might have seen is that systemd will be able to take over the job of the session manager...
For example, in this interview (10th question).
Exactly. Note that this has nothing to do with the desktop manager, only with the session manager :-)
Offline
If you want to be taken seriously I suggest you don't make highly controversial/implausible claims without being able to provide the references...
Added a disclaimer to my post 344
Last edited by Lone_Wolf (2012-10-17 22:41:12)
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