[Bug 484234] Re: Always wait for all filesystems

2009-12-21 Thread Scott James Remnant
** Changed in: mountall (Ubuntu)
Milestone: None = lucid-alpha-2

-- 
Always wait for all filesystems
https://bugs.launchpad.net/bugs/484234
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 484234] Re: Always wait for all filesystems

2009-12-21 Thread Launchpad Bug Tracker
This bug was fixed in the package mountall - 2.0

---
mountall (2.0) lucid; urgency=low

  [ Scott James Remnant ]
  * mount event changed to mounting, to make it clear it happens
before the filesystem is mounted.  Added mounted event which
happens afterwards.
  * Dropped the internal hooks, these are now better handled by Upstart
jobs on the mounted event.
  * Dropped the call to restorecon for tmpfs filesystems, this can also be
handled by an Upstart job supplied by SELinux now.
- mounted-dev.conf replaces /dev hook, uses MAKEDEV to make devices.
- mounted-varrun.conf replaces /var/run hook
- mounted-tmp.conf replaces /tmp hook.
  + Hook will be run for any /tmp mountpoint.  LP: #478392.
  + Switching back to using find fixes $TMPTIME to be in days again,
rathern than hours.  LP: #482602
  * Try and make mountpoints, though we only care about failure if the
mountpoint is marked optional since otherwise the filesystem might
make the mountpoint or something.
  * Rather than hiding the built-in mountpoints inside the code, put them
in a new /lib/init/fstab file; that way users can copy the lines into
/etc/fstab if they wish to override them in some interesting way.
  * Now supports multiple filesystem types listed in fstab, the whole
comma-separated list is passed to mount and then /proc/self/mountinfo
is reparsed to find out what mount actually did.
* /dev will be mounted as a devtmpfs filesystem if supported by the
  kernel (which then does not need to run the /dev hook script).
  * Filesystem checks may be forced by adding force-fsck to the kernel
command-line.
  * Exit gracefully with an error on failed system calls, don't infinite
loop over them.  LP: #469985.
  * Use plymouth for all user communication, replacing existing usplash and
console code;
* When plymouth is running, rather than exiting on failures, prompt the
  user as to whether to fix the problem (if possible), ignore the problem,
  ignore the mountpoint or drop to a maintenance shell.  LP: #489474.
* If plymouth is not running for whatever reason, the fallback action
  is always to start the recovery shell.
  * Adjust the set of filesystems that we wait for by default: LP: #484234.
* Wait for all local filesystems, except those marked with the
  nobootwait option.
* Wait for remote filesystems mounted as, or under, /usr or /var, and
  those marked with the bootwait option.
  * Always try network mount points, since we allow them to fail silently;
SIGUSR1 now simply retries them once more.  LP: #470776.
  * Don't retry devices repeatedly.  LP: #480564.
  * Added manual pages for the events emitted by this tool.

  [ Johan Kiviniemi ]
  * Start all fsck instances in parallel, but set their priorities so that
thrashing is avoided.  LP: #491389.
 -- Scott James Remnant sc...@ubuntu.com   Mon, 21 Dec 2009 23:09:23 +

** Changed in: mountall (Ubuntu)
   Status: Fix Committed = Fix Released

-- 
Always wait for all filesystems
https://bugs.launchpad.net/bugs/484234
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 484234] Re: Always wait for all filesystems

2009-12-13 Thread Scott James Remnant
** Changed in: mountall (Ubuntu)
   Status: Triaged = Fix Committed

** Changed in: mountall (Ubuntu)
 Assignee: (unassigned) = Scott James Remnant (scott)

-- 
Always wait for all filesystems
https://bugs.launchpad.net/bugs/484234
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 484234] Re: Always wait for all filesystems

2009-12-07 Thread Scott James Remnant
** Summary changed:

- fsck on /home needs graphical feedback
+ Always wait for all filesystems

** Changed in: mountall (Ubuntu)
   Status: Incomplete = Triaged

** Changed in: mountall (Ubuntu)
   Importance: Medium = Critical

** Description changed:

- In Karmic;
+ In previous releases to Karmic, we always waited for all filesystems
+ listed in /etc/fstab to be mounted before continuing the boot.  In
+ Karmic we tried something new, we only waited for FHS filesystems to
+ be mounted, assuming that others wouldn't be needed during the boot.
  
- If the system is set up to use a separate partition for /home, fsck will
- sometimes need more time to check the file system than upstart to boot
- the system. If a users tries to log in, (s)he is confronted with lot of
- strange error messages. The user's home directory will seem empty, the
- configration will seem lost.
+ I think that in theory this was a great idea, but in practice it was a
+ terrible one.
  
- Proposed solution: display a progress notification or switch to a file
- system with online file system check.
+ So we'll revert to waiting for everything for lucid, this will solve all
+ the fsck and passphrase under X type issues, as well as the my system
+ doesn't boot.
+ 
+ This is unlikely to be backported to Karmic.

-- 
Always wait for all filesystems
https://bugs.launchpad.net/bugs/484234
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs