upstart-0.6.3 in rawhide, tomorrow 2009-12-10

[Bill Nottingham]

https://fedoraproject.org/wiki/Features/Upstart0.6.0

was approved at last week's FESCo meeting. It was built today, and will
land in rawhide tomorrow.

What this means for you:

It's going to be a bit of a bumpy first yum upgrade. You will likely have
to reboot with 'reboot -f', as the job formats have changed
slightly, and the communication with init(8) has changed.

Once you reboot, things should work pretty much the same.

All users have been converted with the exception of readahead[1],
unless we missed some.

Obvious FAQ:

Q: Should we port our SysV scripts to native upstart scripts?

A: No, not at this time.

Bill

[1] because I missed in in the first scan and haven't had a chance to
talk to the maintainer.

[Bill Nottingham]

Bill Nottingham (notting(a)redhat.com) said: 
>  It's going to be a bit of a bumpy first yum upgrade. You will
> likely have
>  to reboot with 'reboot -f', as the job formats have changed
>  slightly, and the communication with init(8) has changed.
>  
>  Once you reboot, things should work pretty much the same. 
One notable change that was made is that we were able to simplify the
jobs to the point where the number of login consoles is now configurable,
without editing or removing upstart job definitions.

This is done by the ACTIVE_CONSOLES parameter in /etc/sysconfig/init;
the default value is "/dev/tty/[1-6]", which means that mingetty
will be started on ttys 1 through 6. Shell globs are accepted.

Bill

[Matthew Miller]

On Thu, Dec 10, 2009 at 03:32:29PM -0500, Bill Nottingham wrote:
>  One notable change that was made is that we were able to simplify
> the
>  jobs to the point where the number of login consoles is now configurable,
>  without editing or removing upstart job definitions.
>  This is done by the ACTIVE_CONSOLES parameter in /etc/sysconfig/init;
>  the default value is "/dev/tty/[1-6]", which means that mingetty
>  will be started on ttys 1 through 6. Shell globs are accepted. 
How hard would it be to make this be different in runlevels 3 and 5? I like
to have lots in runlevel 3, and few if X is available.


-- 
Matthew Miller <mattdm(a)mattdm.org&gt;
Senior Systems Architect 
Cyberinfrastructure Labs / Instructional & Research Computing
Computing & Information Technology 
Harvard School of Engineering & Applied Sciences

[Bill Nottingham]

Matthew Miller (mattdm(a)mattdm.org) said: 
>  > One notable change that was made is that we were able to
> simplify the
>  > jobs to the point where the number of login consoles is now configurable,
>  > without editing or removing upstart job definitions.
>  > This is done by the ACTIVE_CONSOLES parameter in /etc/sysconfig/init;
>  > the default value is "/dev/tty/[1-6]", which means that mingetty
>  > will be started on ttys 1 through 6. Shell globs are accepted.
>  
>  How hard would it be to make this be different in runlevels 3 and 5? I like
>  to have lots in runlevel 3, and few if X is available. 
Given how it's implemented, you could do something truly disgusting like

ACTIVE_CONSOLES=$([ "$RUNLEVEL" = 3 ] && echo '/dev/tty[1-6]' ||
echo '/dev/tty2')

I'm not sure I really want to *support* people doing that, though.

Bill

[Matthew Miller]

On Wed, Dec 16, 2009 at 11:23:31AM -0500, Bill Nottingham wrote:
>  > How hard would it be to make this be different in runlevels 3
> and 5? I like
>  > to have lots in runlevel 3, and few if X is available.
>  Given how it's implemented, you could do something truly disgusting like
>  ACTIVE_CONSOLES=$([ "$RUNLEVEL" = 3 ] && echo '/dev/tty[1-6]'
> || echo '/dev/tty2')
>  I'm not sure I really want to *support* people doing that, though. 
You mean, you don't like the idea of having different numbers of consoles
running in different runlevels, or you don't like the
abusing-shell-script-as-config-file thing?

It's not a big deal, but it's something that's trivially done in traditional
inittab.

-- 
Matthew Miller <mattdm(a)mattdm.org&gt;
Senior Systems Architect 
Cyberinfrastructure Labs / Instructional & Research Computing
Computing & Information Technology 
Harvard School of Engineering & Applied Sciences

[Bill Nottingham]

Matthew Miller (mattdm(a)mattdm.org) said: 
>  > Given how it's implemented, you could do something truly
> disgusting like
>  > ACTIVE_CONSOLES=$([ "$RUNLEVEL" = 3 ] && echo
> '/dev/tty[1-6]' || echo '/dev/tty2')
>  > I'm not sure I really want to *support* people doing that, though.
>  
>  You mean, you don't like the idea of having different numbers of consoles
>  running in different runlevels, or you don't like the
>  abusing-shell-script-as-config-file thing? 
The latter. :)

Bill

[Matthew Miller]

On Wed, Dec 16, 2009 at 04:16:15PM -0500, Bill Nottingham wrote:
>  > > Given how it's implemented, you could do something
> truly disgusting like
>  > > ACTIVE_CONSOLES=$([ "$RUNLEVEL" = 3 ] && echo
> '/dev/tty[1-6]' || echo '/dev/tty2')
>  > > I'm not sure I really want to *support* people doing that, though.
>  > You mean, you don't like the idea of having different numbers of consoles
>  > running in different runlevels, or you don't like the
>  > abusing-shell-script-as-config-file thing?
>  The latter. :) 
Cool, then. :)

-- 
Matthew Miller <mattdm(a)mattdm.org&gt;
Senior Systems Architect 
Cyberinfrastructure Labs / Instructional & Research Computing
Computing & Information Technology 
Harvard School of Engineering & Applied Sciences