Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Jeff Garzik
On 07/14/2010 02:13 PM, Lennart Poettering wrote: On Wed, 14.07.10 13:44, Bill Nottingham (nott...@redhat.com) wrote: Lennart Poettering (mzerq...@0pointer.de) said: There's also the systemd.unit= kernel command line option which you may use to boot into different targets. See the feature

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread drago01
On Wed, Jul 14, 2010 at 8:24 PM, Jeff Garzik jgar...@pobox.com wrote: On 07/14/2010 02:13 PM, Lennart Poettering wrote: On Wed, 14.07.10 13:44, Bill Nottingham (nott...@redhat.com) wrote: Lennart Poettering (mzerq...@0pointer.de) said: There's also the systemd.unit= kernel command line

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 13:45, Matthias Clasen (mcla...@redhat.com) wrote: To achieve what you want to do upstart would need to support something similar: make it possible to install it without insisting on the /sbin/init file name and related ones, and then add in those names via symlinks only

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 13:31, Chris Adams (cmad...@hiwaay.net) wrote: Once upon a time, Lennart Poettering mzerq...@0pointer.de said: Yes this would work, though in a different syntax: ExecStartPre=-/bin/mkdir -p /var/run/foo ; -/sbin/restorecon /var/run/foo (The initial - btw means

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Matthias Clasen
On Wed, 2010-07-14 at 20:48 +0200, Lennart Poettering wrote: On Wed, 14.07.10 13:45, Matthias Clasen (mcla...@redhat.com) wrote: To achieve what you want to do upstart would need to support something similar: make it possible to install it without insisting on the /sbin/init file name

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Daniel J Walsh
On 07/14/2010 02:54 PM, Lennart Poettering wrote: On Wed, 14.07.10 13:31, Chris Adams (cmad...@hiwaay.net) wrote: Once upon a time, Lennart Poettering mzerq...@0pointer.de said: Yes this would work, though in a different syntax: ExecStartPre=-/bin/mkdir -p /var/run/foo ;

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Jeffrey Ollie
I've been trying to test systemd on my dev box but without success so far. My system boots up and I get the usual GDM login screen and VTs but I can't login. SSH fails as well. SSH gives me Unable to get valid context for jcollie shows me the last login date and closes the connection. I think

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 20:25, drago01 (drag...@gmail.com) wrote: Or you could do this: /etc/systemd/system/default.target → /lib/systemd/system/graphical.target to boot into the graphical stuff by default. This is the default as we package it. Or you could just parse inittab and notice

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 14:07, Jeffrey Ollie (j...@ocjtech.us) wrote: I've been trying to test systemd on my dev box but without success so far. My system boots up and I get the usual GDM login screen and VTs but I can't login. SSH fails as well. SSH gives me Unable to get valid context for

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 14:59, Matthias Clasen (mcla...@redhat.com) wrote: On Wed, 2010-07-14 at 20:48 +0200, Lennart Poettering wrote: On Wed, 14.07.10 13:45, Matthias Clasen (mcla...@redhat.com) wrote: To achieve what you want to do upstart would need to support something similar: make

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Jeff Garzik
On 07/14/2010 03:08 PM, Lennart Poettering wrote: I'd also argue that simply changing a symlink in /etc/systemd/system is a lot easier to understand and discoverable than having to edit old and crufty /etc/inittab which to fully understand you really must have a historical Unix background for.

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 14:24, Daniel J Walsh (dwa...@redhat.com) wrote: myapp_t creating a directory in var_run_t will be labeled myapp_var_run_t. I would just need to go through all the policy that uses var_run_t directories and make sure it has this rule. Hmm, if you would be willing to

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Daniel J Walsh
On 07/14/2010 03:20 PM, Lennart Poettering wrote: On Wed, 14.07.10 14:24, Daniel J Walsh (dwa...@redhat.com) wrote: myapp_t creating a directory in var_run_t will be labeled myapp_var_run_t. I would just need to go through all the policy that uses var_run_t directories and make sure it has

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Bill Nottingham
Lennart Poettering (mzerq...@0pointer.de) said: Would alternatives work here ? Yes, the alternatives system would probably work. However, I think there are things where it is a good idea to use and where it isn't. And I think this case is one of the latter. If we go down the switchable

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 15:18, Jeff Garzik (jgar...@pobox.com) wrote: On 07/14/2010 03:08 PM, Lennart Poettering wrote: I'd also argue that simply changing a symlink in /etc/systemd/system is a lot easier to understand and discoverable than having to edit old and crufty /etc/inittab which to

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Bill Nottingham
Adam Williamson (awill...@redhat.com) said: Does it pull this from inittab if there's no other configuration for this? Ok. You got me on this one. Systemd does actually not parse the inittab. That cruft looked a bit too ugly and clumsy and old for us to support. Vaguely a propos

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 15:26, Bill Nottingham (nott...@redhat.com) wrote: Lennart Poettering (mzerq...@0pointer.de) said: Would alternatives work here ? Yes, the alternatives system would probably work. However, I think there are things where it is a good idea to use and where it isn't.

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 15:23, Daniel J Walsh (dwa...@redhat.com) wrote: And stuff like this. And of course this is just cleaner this way, since the files in /var/run and /var/lock are runtime objects that are used for synchronization and establishment of communication channels only. They happen

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 12:34, Adam Williamson (awill...@redhat.com) wrote: Ok. You got me on this one. Systemd does actually not parse the inittab. That cruft looked a bit too ugly and clumsy and old for us to support. Vaguely a propos - does systemd execute /etc/rc.local ? Yes, there is a

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread drago01
On Wed, Jul 14, 2010 at 9:47 PM, Lennart Poettering mzerq...@0pointer.de wrote: On Wed, 14.07.10 12:34, Adam Williamson (awill...@redhat.com) wrote: Ok. You got me on this one. Systemd does actually not parse the inittab. That cruft looked a bit too ugly and clumsy and old for us to

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread James Antill
On Wed, 2010-07-14 at 21:08 +0200, Lennart Poettering wrote: On Wed, 14.07.10 14:24, Jeff Garzik (jgar...@pobox.com) wrote: /etc/systemd/system. You could do this: /etc/systemd/system/default.target → /lib/systemd/system/multi-user.target to avoid the graphical UI, and boot into

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 14:32, Bill Nottingham (nott...@redhat.com) wrote: 1. normal gettys 2. single-user mode 3. ctrl-alt-delete 4. prefdm starting These four things should be covered for alraedy. 5. automatically starting gettys on serial consoles This is currently not dealt with, I have

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Adam Williamson
On Wed, 2010-07-14 at 22:09 +0200, Lennart Poettering wrote: 6. plymouth interactions There's https://bugzilla.redhat.com/show_bug.cgi?id=614245 which currently is an issue when using plymouth in conjunction with systemd. Ray promised to look into this every day now ;-) Plymouth is the

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 14:28, Bill Nottingham (nott...@redhat.com) wrote: And the admin could even define additional targets, to achieve different system profiles he can boot into or switch forth and back to and from, and give it arbitrary names, and even pull in any of the targets we ship by

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Adam Williamson
On Wed, 2010-07-14 at 22:26 +0200, Lennart Poettering wrote: On Wed, 14.07.10 13:16, Adam Williamson (awill...@redhat.com) wrote: On Wed, 2010-07-14 at 22:09 +0200, Lennart Poettering wrote: 6. plymouth interactions There's https://bugzilla.redhat.com/show_bug.cgi?id=614245

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 16:03, James Antill (ja...@fedoraproject.org) wrote: Or you could just parse inittab and notice when runlevel 3 was listed. Keeps everything nice and compatible, including existing manuals and books, and sysadmin knowledge. Is this really such a biggie? I mean

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 16:25, Horst H. von Brand (vonbr...@inf.utfsm.cl) wrote: Lennart Poettering mzerq...@0pointer.de wrote: Heya, as many of you probably know systemd got accepted as feature for F-14 by FESCO a few weeks back. Congratulations. Just a question: Why isn't it

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Jeff Garzik
On 07/14/2010 03:33 PM, Lennart Poettering wrote: On Wed, 14.07.10 15:18, Jeff Garzik (jgar...@pobox.com) wrote: On 07/14/2010 03:08 PM, Lennart Poettering wrote: I'd also argue that simply changing a symlink in /etc/systemd/system is a lot easier to understand and discoverable than having

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread James Antill
On Wed, 2010-07-14 at 22:38 +0200, Lennart Poettering wrote: On Wed, 14.07.10 16:03, James Antill (ja...@fedoraproject.org) wrote: Or you could just parse inittab and notice when runlevel 3 was listed. Keeps everything nice and compatible, including existing manuals and books, and

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 16:34, Bill Nottingham (nott...@redhat.com) wrote: Lennart Poettering (mzerq...@0pointer.de) said: The issue is that this is a behavior change (from both sysvinit and upstart) that will need code to be handled properly in other packages. Anaconda, at least, will

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 17:00, Jeff Garzik (jgar...@pobox.com) wrote: I would have prefered if you would have taken up this fight with the Upstart people when it was added to Fedora. We are just finishing the work Upstart began in this area, and I am not really willing to fight now a battle

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 17:01, James Antill (ja...@fedoraproject.org) wrote: On Wed, 2010-07-14 at 22:38 +0200, Lennart Poettering wrote: On Wed, 14.07.10 16:03, James Antill (ja...@fedoraproject.org) wrote: Or you could just parse inittab and notice when runlevel 3 was listed.

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Chris Lumens
Hmm, I wasn't aware that Anaconda even asks a question about the runlevel. Given that I am too lazy to try this out now, what exactly is this question? i.e. does it ask Are you installing a server or a deskop? or what does it ask? The default runlevel is inferred based upon packages installed

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 16:36, Horst H. von Brand (vonbr...@inf.utfsm.cl) wrote: Lennart Poettering mzerq...@0pointer.de wrote: as many of you probably know systemd got accepted as feature for F-14 by FESCO a few weeks back. Perhaps I'm being unusually dense, but... How do I go ahead and

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Adam Williamson
On Wed, 2010-07-14 at 23:08 +0200, Lennart Poettering wrote: Did you see the post a while back from someone who tried systemd and found it wouldn't boot their system? Just curious. I will try this myself later today. I think I have responded to all mails and bugzilla bugs. Or have I

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 17:23, Chris Lumens (clum...@redhat.com) wrote: Hmm, I wasn't aware that Anaconda even asks a question about the runlevel. Given that I am too lazy to try this out now, what exactly is this question? i.e. does it ask Are you installing a server or a deskop? or what does

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Kevin Fenzi
On Wed, 14 Jul 2010 23:30:44 +0200 Lennart Poettering mzerq...@0pointer.de wrote: Well, if this is all this is about then I wonder why this is there anyway? If no gdm is installed, then runlevel 5 and 3 should be identical anyway, so what's the point of fixing the default runlevel there?

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Adam Williamson
On Wed, 2010-07-14 at 15:42 -0600, Kevin Fenzi wrote: Perhaps someone could put together a wiki page for lazy sysadmins with a QA? ie, I used to do this in upstart/sysvinit, how do I do it with systemd? Jóhann Guðmundsson (viking_ice) has been working on something along these lines:

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Kalev Lember
On 07/14/2010 09:13 PM, Lennart Poettering wrote: /etc/systemd/system/default.target → /lib/systemd/system/graphical.target to boot into the graphical stuff by default. This is the default as we package it. Lets say the admin (or Anaconda) has modified the default.target symlink. What

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 15:42, Kevin Fenzi (ke...@scrye.com) wrote: On Wed, 14 Jul 2010 23:30:44 +0200 Lennart Poettering mzerq...@0pointer.de wrote: Well, if this is all this is about then I wonder why this is there anyway? If no gdm is installed, then runlevel 5 and 3 should be identical

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Bill Nottingham
Lennart Poettering (mzerq...@0pointer.de) said: So, here's my call for help, in order to make this all a big success: So, I've actually played with this now, instead of just asking questions and operating on knowledge from the initial announcement. I must admit... at first glance, I'm not the

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Thu, 15.07.10 00:51, Kalev Lember (ka...@smartlink.ee) wrote: On 07/14/2010 09:13 PM, Lennart Poettering wrote: /etc/systemd/system/default.target → /lib/systemd/system/graphical.target to boot into the graphical stuff by default. This is the default as we package it. Lets say the

Runlevel subsys re-verification via /etc/rc (was RE: [HEADS-UP] systemd for F14 - the next steps)

2010-07-14 Thread Cleaver, Japheth
-Original Message- From: devel-boun...@lists.fedoraproject.org On Behalf Of Lennart Poettering Sent: Wednesday, July 14, 2010 8:43 AM To: devel@lists.fedoraproject.org Subject: Re: [HEADS-UP] systemd for F14 - the next steps 2) You parse some configuration files or similar

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 18:00, Bill Nottingham (nott...@redhat.com) wrote: Lennart Poettering (mzerq...@0pointer.de) said: So, here's my call for help, in order to make this all a big success: So, I've actually played with this now, instead of just asking questions and operating on knowledge

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Matthias Clasen
On Thu, 2010-07-15 at 01:29 +0200, Lennart Poettering wrote: [long comparsion elided...] Or to explain this with a table, showing you what verbs most people would probably use for four kinds (of the ten) of objects that are managed by systemd: Services: Started | Stopped Socket:

Re: Runlevel subsys re-verification via /etc/rc (was RE: [HEADS-UP] systemd for F14 - the next steps)

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 15:55, Cleaver, Japheth (jclea...@soe.sony.com) wrote: 2) How will systemd handle telinit/runlevel cases with the existing runlevel? Is there a way to verify (from a logical init/subsys perspective only) that what should be running in your runlevel is? Not sure I fully grok

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Lennart Poettering
On Wed, 14.07.10 19:42, Matthias Clasen (mcla...@redhat.com) wrote: On Thu, 2010-07-15 at 01:29 +0200, Lennart Poettering wrote: [long comparsion elided...] Or to explain this with a table, showing you what verbs most people would probably use for four kinds (of the ten) of objects

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Bill Nottingham
Stepping back, this is the situation I started with that led me to these observations: Incoming knowledge: - Upstart and init experience - A reading of the initial 'why I did systemd, and what it intends to support' document Testing methodology: - Install it - Boot it - Poke around Is this

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread Adam Williamson
On Thu, 2010-07-15 at 02:37 +0200, Lennart Poettering wrote: It's actually right the first paragraph after the list of options. Not sure how I can make this any more obvious to find. http://0pointer.de/public/systemd-man/systemd.html No-one reads man pages any more, it's all about the wikis

Re: [HEADS-UP] systemd for F14 - the next steps

2010-07-14 Thread James Antill
On Wed, 2010-07-14 at 23:19 +0200, Lennart Poettering wrote: On Wed, 14.07.10 17:01, James Antill (ja...@fedoraproject.org) wrote: But your runlevel is not a service configuration, so I see no reason why you couldn't say if there is an 'id:blah:' line in inittab that's authoritative

[HEADS-UP] systemd for F14 - the next steps

2010-07-13 Thread Lennart Poettering
Heya, as many of you probably know systemd got accepted as feature for F-14 by FESCO a few weeks back. https://fedoraproject.org/wiki/Features/systemd And in case you want to read up what systemd actually is, here's the blog post that introduced it (only slightly out-of-date, we have however

<    1   2   3