The road to systemd for openSUSE 12.1

**malcolmlewis** · 10-Jun-2011, 11:14

Hi all,
systemd is coming for next openSUSE (12.1) scheduled next fall.... read more here;

[opensuse-factory] The road to systemd for openSUSE 12.1

ab · 10-Jun-2011, 20:49

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gotta admit... some good stuff to be read in there and some really neat
features. I, for one, welcome our new Systemd overlords. :-)

Good luck.

On 06/10/2011 11:36 AM, malcolmlewis wrote:
>
> Hi all,
> systemd is coming for next openSUSE (12.1) scheduled next fall.... read
> more here;
>
> '[opensuse-factory] The road to systemd for openSUSE 12.1'
> (http://lists.opensuse.org/opensuse-f.../msg00210.html)
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJN8tfXAAoJEF+XTK08PnB5R+sQAKa2ovWC0p/Lt5Q7I3VGuRH6
daxL1FfbTgccyzJYHr3LdOaSRXFPaCejkmxmfJ4m6o22waUxqKYEEbvj9sRWthem
8q51U9Sm5ykAfrYby+CBxQ8ofdPe90rF7GZwyq+7oKCTqKlX1EFWd4jlp9O9/CxE
g7jWCIjsstIQkOMAP88sU5zV9BYJc+1j+5x5n85idC+M/mBpEi3JeIp2gQKXTWvK
cG29bytNom6oHbmGQo1LchlkWaX6DHid/vjoHUn+AUE3UxiyL6OxR2dC7jfFmInz
NiasvG95/BS9wWMTS9qWznUbs2Dcft01iRFOU6lqcaUlrLiiqjP5BZjOx3ap4f1x
hxBpJaXeVgwTEJQb2aBlFM4aaAA7mSNvQ+IRdWy0tnNtlGdbPJFH7QsTTx73AWyx
jsT2lEEQywr78D+a2rRI2krQWGhEEVgKzaeWdBPkXMbFXs+8nNRMJBzS8VDS2+rh
HUwC18jzvZ99pOd+PU4dN0iEtijg28kzs3PgH0jL83dR7Us2ZJm0F2U1/+lJ5mGS
baEpsnUB0dNMx+6Jd1rWCk16WNM98eYa9jgu1FfcyDHrdCF/asOyne8bEUYNn+j0
F5MCwAgEM37+Z7mHYg7WGFeh53MdcT+SdN66RYvzSjFleqUJeN+mT4CKI+5dR7eW
kj2qTEV0OY7B7SeRkiuD
=zHrT
-----END PGP SIGNATURE-----

**ah7013** · 10-Jun-2011, 21:53

This looks very interesting. Thanks for the link malcolmlewis

**oldcpu** · 11-Jun-2011, 04:25

Originally Posted by malcolmlewis

Hi all,
systemd is coming for next openSUSE (12.1) scheduled next fall.... read more here;

[opensuse-factory] The road to systemd for openSUSE 12.1

Thanks malcomlewis. I also noted that on [opensuse-project] in addition to [opensuse-factory] and I suspect it could be on a few other mailing lists as well. Its quite significant.

It makes me wonder if this increases the risk when testing an openSUSE-12.1 milestone release on a PC with multiple partitions. For example, on my Sandbox PC I have 2 hard drives, with the 1st hard drive having 3 boot partitions: freedos, openSUSE-11.4, and tumbleweed-11.4.

The second hard drive is carved up but nothing inside the partitions. I was thinking of putting 12.1 milestones on this PC for testing, but now I'm thinking twice , as I want to understand the implications of systemd and the risk to breaking my nominal grub boot.

Here are my partitions:

Code:

Disk /dev/sda: 320.1 GB, 320072933376 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63     1044224      522081    6  FAT16
/dev/sda2   *     1044225    52243379    25599577+  83  Linux
/dev/sda3        52243380    54283634     1020127+  82  Linux swap / Solaris
/dev/sda4        54283635   625137344   285426855    5  Extended
/dev/sda5        54283698   515076029   230396166   83  Linux
/dev/sda6       515076093   566275184    25599546   83  Linux
/dev/sda7       566275248   625137344    29431048+  83  Linux

Disk /dev/sdb: 163.9 GB, 163928604672 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048    52436991    26217472   83  Linux
/dev/sdb2        52436992   104871935    26217472   83  Linux
/dev/sdb3       104871936   110446591     2787328   82  Linux swap / Solaris
/dev/sdb4       110446592   320172031   104862720    f  W95 Ext'd (LBA)
/dev/sdb5       110448640   215302143    52426752   83  Linux
/dev/sdb6       215304192   320143359    52419584   83  Linux

Where sda1 is freedos, sda2 is openSUSE-11.4, and sda6 is tumbleweed-11.4. Other Linux partitions on sda are /home partitions.

So I am now tempted to put 12.1 in either sdb1 or sdb2 (with the corresponding /home in sdb5 or sdb6). But will systemd impact my MBR and my current boot ? Clearly, I will need to back up my MBR before doing anything.

**ken_yap** · 11-Jun-2011, 04:45

I don't think it interacts with the bootloader at all. It springs into action after the kernel and initrd are loaded. It takes the place of init.

**oldcpu** · 11-Jun-2011, 04:49

Originally Posted by ken_yap

I don't think it interacts with the bootloader at all. It springs into action after the kernel and initrd are loaded. It takes the place of init.

I hope so. I noted this quote:

phase 1: detecting current issues with systemd. Install systemd package and "manually" boot with it, by adding "init=/bin/systemd" at you kernel boot command line. In this setup, we want to find ALL the issues caused by switching to systemd, so please, check systemd on Factory status page[2] and follow the instructions there to fill bug reports. We also want to ensure there is no regression, when using legacy sysvinit initscripts with systemd as boot manager

I'm trying to wrap my head around this (and even though its past 12noon I'm still one-half asleep).

So initially there is a boot code to test this. But later presumably that line needs to be put in grub's menu.lst .... which may mean I need to be careful with any custom grub edits.

**ken_yap** · 11-Jun-2011, 04:57

What happens is that the initrd knows what process to make the process id 1, the parent of all processes. Normally this is is /sbin/init. However it can be overridden from the boot parameters for rescue or testing purposes. Presumably when systemd is stable, /sbin/init will be an alias for it.

That description of systemd as boot manger is a little bit misleading, as people like you have inferred some connection with the bootloader. Initialisation manager is probably closer to it.

init - Wikipedia, the free encyclopedia

**oldcpu** · 13-Jun-2011, 12:40

Has any tried booting with the boot code:

Code:

init=/bin/systemd

The need to test that was noted above.

I tried this on my 32-bit openSUSE-12.1 milestone1 LXDE install. I can't notice any difference.

What should I test ? What should I look out for ?

Should I test both with and with out it and compare the two different dmesg ? Look for new errors ?

I have not a clue !

**oldcpu** · 19-Jun-2011, 12:16

Reference systemd, there is an interesting thread on the opensuse-factory mailing list. [opensuse-factory] Tumbleweed systemd does not allow my computer to boot

Apparently systemd appears to some not to support a separate /usr partition (without other changes being done to GNU/Linux). The explanation are given here : freedesktop.org - Software/systemd/separate-usr-is-broken

**robin_listas** · 19-Jun-2011, 19:08

On 2011-06-19 20:36, oldcpu wrote:
> Apparently systemd appears to some not to support a separate /usr
> partition (without other changes being done to GNU/Linux). The

Yes, that alone would impede me from using systemd at all. Not for factory,
but for installing 11.2 as stable when the time comes.

--
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 "Celadon" at Telcontar)