On 04/05/2014 11:41 PM, Bruce Dubbs wrote:
> Working with systemd, there seem to be lots of "learning" issues.
>
> I was trying to watch the boot sequence and the screen clears and I get
> a login prompt. How to disable clearing the screen? Well that's simple
> enough:
>
> mkdir -p /etc/systemd/system/getty@tty1.service.d
>
> cat > /etc/systemd/system/getty@tty1.service.d/noclear.conf < EOF
> [service]
> TTYVTDisallocate=no
> EOF
>
This is correct way of doing things in systemd. I do agree that this
behaviour isn't that good, but I guess there's also good reason for
that. Even if you wanted, you couldn't catch all the output anyways
since it isn't serialized and it goes way too fast (at least on my
machine). You could use journald to get (almost) the same output you'd
get on boot, without the [ OK ] and [ FAIL ] messages though:
journalctl -b _PID=1
This command will output messages of pid 1, which is
/lib/systemd/systemd or rather a symlink to it, /sbin/init. -b means it
outputs messages from last boot.
> <sarcasm>
> Isn't that special! How intuitive! Compare to the standard login that
> does nothing unless you specify a clear tty sequence in /etc/issue.
> Who says the user knows more than the systemd developers? See how easy
> systemd is to learn?
> </sarcasm>
>
> Now I come to setting up udev and networking. I have the rule:
>
> /etc/udev/rules.d/70-persistent-net.rules
>
> The contents are
>
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", \
> ATTR{address}=="00:11:11:79:4d:17", ATTR{dev_id}=="0x0", \
> ATTR{type}=="1", KERNEL=="enp*", NAME="eth0"
>
> It doesn't work in udev-211, although it did using udev-208. I can add
> net.ifnames=0 to the kernel command line and get eth0, but why doesn't
> the custom udev rule work?
>
> Actually, when I run
>
> # udevadm test-builtin net_id /sys/class/net/enp0s25
>
> Then the rule kicks in and renames the interface, but it doesn't seem to
> run automatically. Armin, do you have any insight?
>
> -- Bruce
>
I've just tried this one:
$ cat /etc/udev/rules.d/99-network.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="correct
mac address goes here", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth1"
The trick is, LFS uses /etc/udev/rules.d/70-persistent-net.rules but
systemd udev has /lib/udev/rules.d/80-net-setup-link.rules. The latter
one appears to be ran after persistent-net.rules and it's the one that
does renaming to enpwhatever. That's why 99-network.rules worked for me.
--
Note: My last name is not Krejzi.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
