touch-packages team mailing list archive

[Adam Conrad <adconrad@xxxxxxx>]

Console logging this early in the boot should be trivial via /dev/kmsg,
if nothing else?   Maybe that's mildly abusive of the interface, but any
attempt to hint at people why their boot is failing to be useful sure
beats just sitting there.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/1096079

Title:
  boot fails when a kernel filesystem can't be mounted (e.g., due to a
  dangling symlink)

Status in “mountall” package in Ubuntu:
  Triaged

Bug description:
  In 2.15.3 (lucid), and probably later, if I have this in fstab, then the boot locks up:
  none /srv/chroots/raring-amd64/dev/shm tmpfs defaults 0 0

  Looking at the target for the mount:
  lrwxrwxrwx 1 root root 8 2012-11-07 23:05 /srv/chroots/raring-amd64/dev/shm -> /run/shm
  On the lucid machine, /run/shm does not exist, of course.

  Changing that to:
  none /srv/chroots/raring-amd64/run/shm tmpfs defaults 0 0
  works around the issue.

  A dangling symlink in fstab should not cause a completely silent
  failure to boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1096079/+subscriptions