Re: [gentoo-user] problems getting systemd to work

[covici@ccs.covici.com]

Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Wed, May 14, 2014 at 4:43 AM,  <covici@ccs.covici.com> wrote:
> > Canek Peláez Valdés <caneko@gmail.com> wrote:
> >
> >> On Mon, May 12, 2014 at 11:52 AM,  <covici@ccs.covici.com> wrote:
> >> > Canek Peláez Valdés <caneko@gmail.com> wrote:
> >> >
> >> >> On Mon, May 12, 2014 at 11:31 AM,  <covici@ccs.covici.com> wrote:
> >> >> [snip]
> >> >> > OK, I will try dracut,
> >> >>
> >> >> I hope it works with dracut. This is my kernel command line and
> >> >> RAID/LVM related stuff from GRUB2:
> >> >>
> >> >> GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash"
> >> >> GRUB_PRELOAD_MODULES="lvm mdraid1x"
> >> >>
> >> >> And this is my dracut.conf (minus comments):
> >> >>
> >> >> add_dracutmodules+="crypt lvm mdraid systemd"
> >> >> add_drivers+="autofs4 ipv6 dm-crypt aes sha256"
> >> >> fscks="umount mount /sbin/fsck* e2fsck"
> >> >>
> >> >> That's it. I didn't touched anything else to make dracut+systemd work
> >> >> with LVM and RAID (and LUKS, but that doesn't matter).
> >> >>
> >> >> Also, dracut comes with extensive and very clear documentation; check
> >> >> the man pages included.
> >> >>
> >> >> > but I still want to know what systemd is doing,
> >> >> > what processes its spawning, etc.  -- how can I find this out -- I
> >> >> > thought to use the confirm_spawn, but it times out and keeps going, what
> >> >> > can I do instead?
> >> >>
> >> >> You can use bootchart:
> >> >>
> >> >> man 1 systemd-bootchart
> >> >>
> >> >> It will produce a chart with all the processes, and how long it takes
> >> >> for every one of them. But remember, the order depends on which one
> >> >> finishes before, and that can change from boot to boot.
> >> >>
> >> >> > Thanks people for all your responses, this is a great list.
> >> >>
> >> >> Regards.
> >> >> --
> >> >> Canek Peláez Valdés
> >> >> Profesor de asignatura, Facultad de Ciencias
> >> >
> >> > Well, since I am unable to see, the graph would not do me any good, any
> >> > way to get it in text form?  What I want to see (and I know the order
> >> > may change) is which starts first and so on, to make sure targets,
> >> > etc. do what I want them to do.
> >>
> >> Try adding this to your kernel command line:
> >> systemd.log_target=console systemd.log_level=debug. It will add a lot
> >> of output, including what is being executed.
> >
> > I also in my kernel command line said rd.lvm=1 just to make sure.
> 
> John, which version of dracut are you using? Also, what was the
> command line you used to generate it?

I am using version 037 and the command line was very simple
dracut --force -M
and here is its output:
 Script started on Wed 14 May 2014 04:52:19 AM EDT
Executing: /usr/bin/dracut --force -M
00bootchart: Could not find command '/sbin/bootchartd'!
00dash: Could not find command '/bin/dash'!
50plymouth: Could not find command 'plymouthd'!
50plymouth: Could not find command 'plymouth'!
90btrfs: Could not find command 'btrfs'!
90dmraid: Could not find command 'dmraid'!
90mdraid: Could not find command 'mdadm'!
90multipath: Could not find command 'multipath'!
95fcoe-uefi: Could not find command 'dcbtool'!
95fcoe-uefi: Could not find command 'fipvlan'!
95fcoe-uefi: Could not find command 'lldpad'!
95iscsi: Could not find command 'iscsistart'!
95iscsi: Could not find command 'iscsi-iname'!
95nbd: Could not find command 'nbd-client'!
97biosdevname: Could not find command 'biosdevname'!
bash
caps
caps: does not work with systemd in the initramfs
modsign
dracut-install: ERROR: installing '/usr/bin/keyctl'
/usr/libexec/dracut-install -D /var/tmp/initramfs.dpEwDV /usr/bin/keyctl
i18n
network
crypt
dm
Skipping udev rule: 64-device-mapper.rules
Skipping udev rule: 60-persistent-storage-dm.rules
Skipping udev rule: 55-dm.rules
kernel-modules
Omitting driver i2o_scsi
lvm
Skipping udev rule: 64-device-mapper.rules
Skipping udev rule: 56-lvm.rules
Skipping udev rule: 60-persistent-storage-lvm.rules
cifs
nfs
resume
rootfs-block
terminfo
udev-rules
Skipping udev rule: 91-permissions.rules
Skipping udev rule: 80-drivers-modprobe.rules
systemd
usrmount
base
fs-lib
shutdown
*** Including modules done ***
*** Installing kernel module dependencies and firmware ***
*** Installing kernel module dependencies and firmware done ***
*** Resolving executable dependencies ***
*** Resolving executable dependencies done***
*** Stripping files ***
*** Stripping files done ***
*** Store current command line parameters ***
*** Creating image file ***
*** Creating image file done ***

Script done on Wed 14 May 2014 04:52:50 AM EDT



-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com