On Tue, 12 Aug 2014 21:14:48 +0300 Andrei POPESCU <andreimpope...@gmail.com> wrote:
> On Ma, 12 aug 14, 14:31:29, Joe wrote: > > > > > I believe there is, though I have not yet tried to use it. The > > point is that, going back two of your paragraphs, it is a *change*, > > and if not manually corrected will therefore break existing systems > > on upgrade. I would have preferred to see it done the other way > > around, i.e. that unfamiliar mount points listed in fstab would > > need some sort of 'abort the boot if this doesn't mount' flag to be > > added. > > See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756103#35 > > > By the way, if the boot is aborted, it would be nice to have some > > sort of shell access available. When this fstab issue bit me, there > > was no control available at all other than the Big Red Switch. Even > > grub2 drops you into a rescue shell when it's unhappy, as I know > > well. > > That's probably one of #755581 or #751624. > Yes, I'm sure it's not intended behaviour. But there's only so much point in trying to fix sid at the moment. Is there a word for 'beyond unstable'? I've installed apt-cacher-ng on my server to try to keep the downloads within some sort of reason. I have five sids, and they're all hungry, all the time... -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140812205531.76b43...@jresid.jretrading.com
