Hi,
after talked with Michael on IRC, here is the patch to see a systemd
Welcome message on Debian systems.
FYI: I had to remove "quiet" from Kernel-command-line to see it.
"Stolen from Gentoo" :-) [1,2]?
Kind Regards,
- Sedat -
[1] http://lists.freedesktop.org/archives/systemd-devel/2010-September/000267.html
[2] http://cgit.freedesktop.org/systemd/commit/?id=0d37b36b2890fdf8149d12460ebb00822e555977
From 76d860ca774cb8724de25c3ed3c455ebe5d548e3 Mon Sep 17 00:00:00 2001
From: Sedat Dilek <sedat.dilek@gmail.com>
Date: Sun, 12 Sep 2010 23:02:22 +0200
Subject: [PATCH] util: add Debian welcome message
Include the "Debian" string as /etc/debian_version contains only the Distribution name like "squeeze".
Use Light Red color for Debian.
Based on a proposal patch of Michael Biebl <biebl@debian.org>
Add unit files to call
/etc/init.d/umountnfs.sh stop (network file systems)
/etc/init.d/umountfs stop (local file systems)
/etc/init.d/umountroot stop ("/" file system)
in the right order and hook them up in the umount.target so they are run
on shutdown and reboot.
On Debian sysinit is not a single script but a separate runlevel.
Split of fsck.target into separate unit file as otherwise we get an
unbreakable cycle on shutdown/reboot.
It contains things like:
#ifndef _LINUX_TYPES_H
#define _LINUX_TYPES_H
#include <stdint.h>
typedef uint32_t __u32;
typedef __u32 __le32;
...
which result in:
/usr/include/asm-generic/int-ll64.h:30:42: error: conflicting types for ‘__u64’
/usr/include/sys/capability.h:39:18: note: previous declaration of ‘__u64’ was here
make[1]: *** [src/libsystemd_core_la-unit.lo] Error 1
make[1]: Leaving directory `/home/kay/work/src/systemd'
make: *** [all] Error 2
So, include linux/types.h to get around that.
Lennart has convinced me that it's more helpful to participate than to sit
on the sidelines and complain. So, hello everyone.
I'm starting by giving up the battle to change the systemctl "isolate"
command to "switch-to". Can't win them all. :) I've got a suggested patch
to expand the documentation a bit, hopefully making it more clear to new
systemd users.
Is there an easy way to list all units where AllowIsolate is enabled? That
should be included alongside this, I think.
