Re: [systemd-devel] Trying to build on a new LFS system.
2011/6/20 Marius Tolzmann tolzm...@molgen.mpg.de: Hi there.. we are also using a self-maintained LFS based gnu/linux here. we switched to systemd in Nov 2010 and it worked fine from the start.. What version are you using? And what version of kernel? Did you have to tune your kernel?? (for example devfs..) Stef ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Trying to build on a new LFS system.
On 06/21/11 08:24, Stef Bon wrote: 2011/6/20 Marius Tolzmann tolzm...@molgen.mpg.de: Hi there.. we are also using a self-maintained LFS based gnu/linux here. we switched to systemd in Nov 2010 and it worked fine from the start.. What version are you using? currently systemd v27 on production workstations and v29 on my workstation.. it works.. And what version of kernel? Did you have to tune your kernel?? (for example devfs..) kernel 2.6.35.x patched with the 676db4af linux-git commit (cgroupfs: create /sys/fs/cgroup to mount cgroupfs on) and kernel 2.6.39.x .. as far as i can tell from the build logs i activated cgroups, autofs4 and devtmpfs.. i currently don't know the exact kernel options activated to get systemd working but i think they were mentioned in this list some time ago and may be explained somewhere else ?!? - i could send you my kernel config if interested.. bye m. -- Dipl.-Inf. Marius Tolzmann marius.tolzm...@molgen.mpg.de --.-- MPI f. molekulare Genetik | Ihnestrasse 63-73, D-14195 Berlin | == MarIuX GNU/Linux == Phone: +49 (0)30 8413 1709| --^-- God put me on earth to accomplish a certain number of things. Right now I am so far behind.. ..I will never die. by calvin from calvinhobbes ;) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Trying to build on a new LFS system.
On Tue, 21.06.11 20:06, Stef Bon (stef...@gmail.com) wrote: Hi, thanks for your info. I've got the following log output. Somewhere the message appears: remount-rootfs.service: cgroup is empty This is just a debug message, not really a problem. You only get this when debug logging is enabled and a cgroup runs empty. Jun 21 18:33:07 systemd[1]: Job dev-tty4.device/start timed out. Jun 21 18:33:07 systemd[1]: Job dev-tty4.device/start finished, result=timeout Jun 21 18:33:07 systemd[1]: Job getty@tty4.service/start finished, result=dependency Jun 21 18:33:07 systemd[1]: Job getty@tty4.service/start failed with result 'dependency'. Jun 21 18:33:07 systemd[1]: Job dev-tty4.device/start failed with result 'timeout'. So the gettys cannot be started since their tty devices never show up. This is most likely because your udev isn't properly set up (not run, or the systemd rules file /lib/udev/rules.d/99-systemd.rules is not properly installed). Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Trying to build on a new LFS system.
Hi, I'm trying to build systemd on a shiny new LFS system. I roughly followed the instructions here: http://www.linuxfromscratch.org/lfs/view/development/index.html Since this is a very minimal system, you have to add extra software: gperf libcap attr expat libxml2 dbus No PAM, no gtk, no tcpwrap, I even try to ignore sysV init scripts. If this works a will add this as an alternative to SysV init scripts. Or is SysV init a requirement? Right now the output of configure is: systemd 29 Distribution:other SysV compatibility: yes SysV init scripts: /etc/init.d SysV rc?.d directories: /etc/rc.d Gtk: no libcryptsetup: no tcpwrap: no PAM: no AUDIT: no SELinux: no binfmt: yes prefix: /usr/local root dir: udev rules dir: /lib/udev/rules.d pam modules dir: /lib/./security dbus policy dir: /etc/dbus-1/system.d dbus session dir:/usr/share/dbus-1/services dbus system dir: /usr/share/dbus-1/services/../system-services dbus interfaces dir: /usr/share/dbus-1/services/../interfaces (prefix /usr/local has to be changed...) Stef ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Trying to build on a new LFS system.
Stef Bon stef...@gmail.com on Mon, 20 Jun 2011 15:15:57 +0200: Thanks a lot, And how do I select the services to be started at boot time?? I've seen lots of documentation, and possibly I did not read good enough. Just add init=/bin/systemd to you boot options. -- Schoene Gruesse Chris ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Trying to build on a new LFS system.
On Mon, 20.06.11 15:15, Stef Bon (stef...@gmail.com) wrote: Heya, And how do I select the services to be started at boot time?? Use systemctl enable and systemctl disable to enable or disable a service in systemd. http://0pointer.de/blog/projects/three-levels-of-off Note that a number of services shipped along with systemd are so basic that they are unconditionallty enabled (i.e. systemctl enable will not work for them). If you nonetheless want to disable them use masking as described in this blog article. Lennart -- Lennart Poettering - Red Hat, Inc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Trying to build on a new LFS system.
Hi there.. we are also using a self-maintained LFS based gnu/linux here. we switched to systemd in Nov 2010 and it worked fine from the start.. since we started a new LFS we decided not to integrate any support for sysv anymore by compiling systemd with --with-distro=other --with-sysvinit-path= --with-sysvrcd-path= --with-rootdir= from the first day.. it may be a good idea not to include any sysv initscripts anymore in LFS to really get a clean system.. if you can't boot your LFS anymore you may just switch back to the chrooted environment or try to fix things by providing init=/bin/bash Be sure to get a recent enough DBUS and udev and activate all the needed kernel options for cgroup support and autofs.. since LFS didn't provided this back in Nov 2010 we had some minor trouble there.. but as i said: it just worked.. and we never ended booting up an unusable system.. bye marius.. On 06/20/11 10:56, Stef Bon wrote: Hi, I'm trying to build systemd on a shiny new LFS system. I roughly followed the instructions here: http://www.linuxfromscratch.org/lfs/view/development/index.html Since this is a very minimal system, you have to add extra software: Right now the output of configure is: systemd 29 Distribution:other SysV compatibility: yes SysV init scripts: /etc/init.d SysV rc?.d directories: /etc/rc.d Gtk: no libcryptsetup: no tcpwrap: no PAM: no AUDIT: no SELinux: no binfmt: yes prefix: /usr/local root dir: udev rules dir: /lib/udev/rules.d pam modules dir: /lib/./security dbus policy dir: /etc/dbus-1/system.d dbus session dir:/usr/share/dbus-1/services dbus system dir: /usr/share/dbus-1/services/../system-services dbus interfaces dir: /usr/share/dbus-1/services/../interfaces -- Dipl.-Inf. Marius Tolzmann marius.tolzm...@molgen.mpg.de --.-- MPI f. molekulare Genetik | Ihnestrasse 63-73, D-14195 Berlin | == MarIuX GNU/Linux == Phone: +49 (0)30 8413 1709| --^-- God put me on earth to accomplish a certain number of things. Right now I am so far behind.. ..I will never die. by calvin from calvinhobbes ;) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Trying to build on a new LFS system.
2011/6/20 Marius Tolzmann tolzm...@molgen.mpg.de: Hi there.. we are also using a self-maintained LFS based gnu/linux here. we switched to systemd in Nov 2010 and it worked fine from the start.. since we started a new LFS we decided not to integrate any support for sysv anymore by compiling systemd with --with-distro=other --with-sysvinit-path= --with-sysvrcd-path= --with-rootdir= from the first day.. it may be a good idea not to include any sysv initscripts anymore in LFS to really get a clean system.. Good to know it works for you. I had simular options like you. I get my system booting, but it hangs after Started recreate volatile files and directories after a minute or so i get messages about being timed out: systemd[1]: Job getty@tty2.service/start failed with result 'dependency' and some more about swap I've looked buy going into chroot again the various files in tmpfiles.d, and they do nothing spectacular, creating files, removing old ones... But about your suggestion, I guess it's the best not to exclude things, but give users a choice, with good comments about the differences and consequences. So offer them both (or more) in the LFS (or Clfs) book. If I'm ready with this, I will write the guide for LFS/CLFS. Stef ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
