On 11/02/2014 09:57 PM, Kenneth Harrison wrote: > On Sun, Nov 2, 2014 at 12:43 PM, Armin K. <[email protected]> wrote: >> Lengthy post ahead, go ahead and grab some popcorn or juice. >> >> Hi everyone, >> >> For some time now you may have noticed a new BLFS branch managed by me >> named "krejzi". >> >> That branch was branched off BLFS trunk while adding and improving >> instructions from BLFS systemd and improving instructions from trunk >> (most of them were cosmetic tweaks as I seem to be a consistency freak). >> >> It's what I call a fork of the BLFS systemd book maintained by me. While >> I do not intend to push back the systemd branch I have received many >> complains about stuff from systemd branch not working very well recently. >> >> As a LFS systemd maintainer I feel like it's my duty to provide a stable >> (or at least "just working") instructions for BLFS, but I had no other >> way to do so than to start my own branch since users don't really care >> about reporting issues on mailing lists or bugzilla and for personal >> reasons, I don't want either. >> >> The branch is now in a usable state - in a state where systemd branch >> should've been - minus two packages that I have yet to review and fix up >> (and, for the latter, to sync with the main book instructions) - lxdm >> and polari. Most if not all of the issues have been addressed (maybe >> some got slipped during the merge). >> >> The book will be published online, but not as an official release (ie, >> won't be visible from main website) and will most likely be placed on my >> personal web space www.lfs.org/~krejzi rather than having a new book at >> www.lfs.org/blfs/view/whatever. >> >> But, I will link from LFS systemd pages (where needed) to the new book >> because of the reasons above and probably will make an official release >> snapshot when the time is right so the users of LFS systemd have a >> stable (as much as trunk is actually, minus the new packages which >> aren't many) and always (or at least 99% of the time) working >> instructions for whatever they need and with help of Bruce's currency >> scripts it will be easy to manage. >> >> But enough about ranting and stuff like that, I have some questions. >> >> What I was unable to think of is a proper name for new book. I went with >> systemd-ng (ng = new generation) but I instantly received a complaint so >> the branch got renamed after just few hours. The branding in the XML >> still remains but I'd like to use some different name if possible and >> I'm interested in suggestions on how to name it. >> >> Also, instead of svn (where it was hosted until yesterday), I moved to >> github and will continue to manage my fork using git fom now on. >> Repository can be found at https://github.com/elkrejzi/BLFS >> >> If any of the current editors want to contribute directly, just mail me >> your public SSH key in order to gain commit access. >> >> I have yet to publish a rendered version, but when the time is right, >> I'll do so and will properly announce it. This mail is just for the >> current developers (and possibly users). >> >> Any comments, rants, critics are welcome. >> >> I ain't sorry for the long post, but I am for all the hastle that this >> post might create. >> >> -- >> Note: My last name is not Krejzi. >> >> >> -- >> http://lists.linuxfromscratch.org/listinfo/blfs-dev >> FAQ: http://www.linuxfromscratch.org/blfs/faq.html >> Unsubscribe: See the above information page >> > > I think since this is going to target both systemd and sysv spec > books, it should possibly be labeled something like, blfs-r-and-d (for > research and development). >
That's a bit odd name, even for something that will "offically" follow LFS systemd book. > The developments in this book could help shed some light on other > problems, even with the main book. One problem I had with the the > systemd book was regarding the networking, where-as if you try to > disable networkd and use dhclient, the network goes completely dead. > I'm not sure if the instructions on that were entirely clear, but the > book did present that you had to disable networkd before enabling > dhclient. I am not sure about that issue. Instructions now say: " Make sure that you disable the systemd-networkd service or configure it not to manage the interfaces you want to manage with DHCP client. " Which is interpretet as "Either issue systemctl disable systemd-networkd or remove the file that represents the interface you are trying to manage (ie, /etc/systemd/network/10-dhcp-eth0.network)", where removing (or renaming) /etc/systemd/network/10-dhcp-eth0.network represents a way of "making systemd-network not to manage eth0". If you don't do this, both dhclient and networkd will try to bring the interface at boot and you don't want that. I haven't tested what happens when you issue "systemctl stop systemd-networkd; systemctl start dhclient", but it may be possible that interface goes down entirely and you have to bring it up manually - something that dhclient should do by itself I believe. Have you tried "ip link set dev eth0 up"? > Even getting wayland going still regardless of init system, > still is undocumented for using Weston and KDE as backends. > This is highly experimental and of no practical use and since kwin4 receives nothing but bugfixes, it's unlikely that it will work at all. I will explain it in Plasma 5 when it's usable enough. Plasma 5.2.0 is next release scheduled to be released before next LFS/BLFS release, so if it reaches a good level of stability, I'll include it in the official book. For now, it lives in a branch (Frameworks 5.3.0 and Plasma 5.1.0). > This could even be good to spark testing with things from the hints as > well, if they mesh well with the rest of the system in up-to-date > format, maybe even research new ideas and projects as well. > Patches are welcome, but I wouldn't accept anything that would make this fork a playground because as I said once, it will be a book that LFS systemd will continue from. -- Note: My last name is not Krejzi.
signature.asc
Description: OpenPGP digital signature
-- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
