Change log for sysvinit package in Ubuntu

sysvinit (2.86.ds1-6ubuntu13) dapper; urgency=low

  * Remove the stop-bootlogd script.
  * Move mountdevsubfs to S02, as there is now an early S01udev script that
    at least makes /dev/null exist.
  * Move hostname.sh to S03.

 -- Scott James Remnant <email address hidden>   Thu, 23 Feb 2006 13:46:08 +0000

sysvinit (2.86.ds1-6ubuntu12) dapper; urgency=low

  * Force recrection of /var/run and /var/lock directories underneath
    mounted /var ... it seems more people than first thought got bitten
    by the bad upgrade path; and this should fix it for them too.

 -- Scott James Remnant <email address hidden>   Thu, 23 Feb 2006 13:03:13 +0000

sysvinit (2.86.ds1-6ubuntu11) dapper; urgency=low

  * If /dev/.udev.log exists, move it to /var/log/udev.log.

 -- Scott James Remnant <email address hidden>   Tue, 21 Feb 2006 16:13:31 +0000

sysvinit (2.86.ds1-6ubuntu10) dapper; urgency=low

  * Change the permissions of /var/lock back to 1777 -- this is the
    permissions they should be, the change to 0755 was a mistake.
    Ubuntu: #30637.

 -- Scott James Remnant <email address hidden>   Tue, 21 Feb 2006 14:58:35 +0000

sysvinit (2.86.ds1-6ubuntu9) dapper; urgency=low

  * Use the progress bar for both K and S scripts in all run levels.
  * Update the progress bar at all opportunities (Adam Conrad).
  * Don't rely on /tmp being on the root filesystem when mounting /var
    and moving /var/run and /var/lock out of the way.
  * Keep /var/run and /var/lock in place as long as possible, and make
    sure they're still there even when /var is unmounted again.

 -- Scott James Remnant <email address hidden>   Tue, 14 Feb 2006 12:55:38 +0000

sysvinit (2.86.ds1-6ubuntu7) dapper; urgency=low


  * Create /var/run and /var/lock with mode 0755, otherwise naughty people
    could do "mkdir /var/run/console; touch /var/run/console/$USER:7" and
    have magic things happen
  * Move mountvirtfs to S01 again, so we can use S00 for readahead.

 -- Scott James Remnant <email address hidden>  Fri,  3 Feb 2006 14:49:06 +0000

sysvinit (2.86.ds1-6ubuntu8) dapper; urgency=low


  * Disable SElinux again, nobody gave me a patch to fix the annoying
    message.

 -- Scott James Remnant <email address hidden>  Fri,  3 Feb 2006 17:54:55 +0000

sysvinit (2.86.ds1-6ubuntu6) dapper; urgency=low


  * Create /var/run and /var/lock, even if we have to quickly move /var
    out of the way first; so they're always there.  (Ubuntu #28943)
  * Don't bother creating the /var/* directories in the init script, the
    filesystem is almost certainly readonly.  (Ubuntu #29637)
  * On initial installs of this package create the /var/run and /var/lock
    tmpfs, moving over anything from the old directories into them.
  * For step-through-dapper upgrades, continue cleaning the /var/run and
    /var/lock filesystems "underneath" but only this once.

 -- Scott James Remnant <email address hidden>  Wed, 25 Jan 2006 14:54:48 +0000

sysvinit (2.86.ds1-6ubuntu5) dapper; urgency=low


  * Clean up the old /var/run and /var/lock filesystems after upgrading.

 -- Scott James Remnant <email address hidden>  Tue, 24 Jan 2006 17:21:08 +0000

sysvinit (2.86.ds1-6ubuntu4) dapper; urgency=low


  * Remove the message when setting the hostname, it doesn't take any
    time to complete and shouldn't ever fail.

 -- Scott James Remnant <email address hidden>  Tue, 24 Jan 2006 14:48:47 +0000

sysvinit (2.86.ds1-6ubuntu3) dapper; urgency=low


  * Drop S18bootlogd from the ordinary boot process; it needs a writable
    /var/log and access to /dev/pts which means it would have to start so
    late that there'd be nothing worth logging.  Nobody can ever remember
    this working in Ubuntu, and nobody's sure it even can work with usplash.
    Everything's still shipped, so those who want it can figure it out, it's
    just not tried by default.

 -- Scott James Remnant <email address hidden>  Mon, 23 Jan 2006 15:38:43 +0000

sysvinit (2.86.ds1-6ubuntu1) dapper; urgency=low


  [ Ongoing Merge Process ]
  * Resynchronise with Debian.

  [ Scott James Remnant ]
  * Use our 99_ubuntu_01_sulogin.dpatch in favour of Debian's sulogin_lockedpw
    patch, as that prints scary warnings to all of our users.
  * During shutdown and reboot take the progress bar from 100 to 0.
  
  * Update sulogin.dpatch to fix Ubuntu #12676 by only checking whether the
    first character of the root password indicates a lock, rather than the
    entire thing.
  
  * Change boot ordering to match the grand streamlined boot plan.
  * Split domount function from mountvirtfs script into functions.sh.
  * Separate out mounting of /dev/shm and /dev/pts into mountdevsubfs script
    that is be run after udev has been started.
  * Separate out updating of /etc/mtab with virtual filesystems into mtab
    script that is run after the root filesystem has been checked and
    remounted.
  * Slim down mountvirtfs script now it just does exactly what it needs to
    and no more.
  
  * Mount /var/run and /var/lock as tmpfs to avoid race conditions with
    needing writable places during boot, we'll ensure anything needing a
    subdir doesn't assume that it exists first.
  * Make sure that we don't clobber those mounts if we /var is a separate
    filesystem
  * Drop cleaning of /var/run and /var/lock as this is just wasting time

 -- Scott James Remnant <email address hidden>  Mon,  9 Jan 2006 10:44:01 +0000

sysvinit (2.86.ds1-5ubuntu5) dapper; urgency=low


  * Look for our progress state file in /dev/.initramfs, since the
    initramfs state directory just moved in the last upload.

 -- Adam Conrad <email address hidden>  Mon,  9 Jan 2006 21:25:07 +1100

sysvinit (2.86.ds1-5ubuntu6) dapper; urgency=low


  * Brown paper bag fix: More the initialising of the progress_size
    variable outside the if block that prevents it from working if
    you're booting from an older initramfs (say, a backup kernel).

 -- Adam Conrad <email address hidden>  Tue, 10 Jan 2006 00:38:00 +1100

sysvinit (2.86.ds1-5ubuntu3) dapper; urgency=low


  * Give runlevel 0 and 6 a first_step as well, since having your shutdown
    stop suddenly halfway through with a shell error is unseemly.

 -- Adam Conrad <email address hidden>  Thu,  5 Jan 2006 15:41:45 +1100

sysvinit (2.86.ds1-5ubuntu2) dapper; urgency=low


  * Disable the selinux patch, it makes an annoying message on boot.

 -- Scott James Remnant <email address hidden>  Thu,  8 Dec 2005 02:06:49 +0000

sysvinit (2.86.ds1-1.1ubuntu6) breezy; urgency=low


  * Make -H work correctly and end up with system halted rather than
    dumping the user into single user mode.

 -- Tollef Fog Heen <email address hidden>  Mon, 26 Sep 2005 12:46:46 +0200

sysvinit (2.86-5ubuntu6) hoary; urgency=low


  * Now, we'll actually check that we're on battery. GAR.

 -- Thom May <email address hidden>  Fri,  7 Jan 2005 18:16:27 +0000

sysvinit (2.85-22ubuntu12) warty; urgency=low


  * Backport fix for Debian bug #255849: explicitly specify the filesystem
    type with mount -t when initializing mtab (Closes: Warty#1848)

 -- Matt Zimmerman <email address hidden>  Mon,  4 Oct 2004 00:05:14 -0700