We've removed the RAMRUN option, and any existing setting will be
ignored. /var/run will always be a tmpfs.
** Changed in: sysvinit (Ubuntu)
Status: New => Fix Released
--
Upgrade 8.10 --> 9.04 : ext3 Filesystem read-only
https://bugs.launchpad.net/bugs/371614
You received this bug notif
** Changed in: sysvinit (Ubuntu)
Status: Incomplete => New
--
Upgrade 8.10 --> 9.04 : ext3 Filesystem read-only
https://bugs.launchpad.net/bugs/371614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Please fix the bug for Ubuntu.
Don't breaks the boot process and use of configuration.
It's working in Debian, it should also in Ubuntu.
--
Upgrade 8.10 --> 9.04 : ext3 Filesystem read-only
https://bugs.launchpad.net/bugs/371614
You received this bug notification because you are a member of Ubu
>I'm not sure who added the choice.
>It's certainly not one we support; most of the boot process
>requires /var/run be writable - that's kinda why it's there.
In intrepid I had RAMRUN=false and everything was fine. Something has
changed during upgrade to jaunty.
The manual says:
$ man rcS
>I'm not sure who added the choice.
>It's certainly not one we support; most of the boot process
>requires /var/run be writable - that's kinda why it's there.
In intrepid I had RAMRUN=false and everything was fine. Something has
changed during upgrade to jaunty.
The manual says:
$ man rcS
On Thu, 2009-05-14 at 11:36 +, pjw wrote:
> > How did you install intrepid?
>
> > The default has always been RAMRUN=yes in Ubuntu
>
> Your're right. The normal user would never notice it.
>
> But if the user has a choice, it should not broke the boot process.
>
I'm not sure who added the
Scott
> How did you install intrepid?
> The default has always been RAMRUN=yes in Ubuntu
Your're right. The normal user would never notice it.
But if the user has a choice, it should not broke the boot process.
Peter
--
Upgrade 8.10 --> 9.04 : ext3 Filesystem read-only
https://bugs.launchpad
On Wed, 2009-05-13 at 20:39 +, pjw wrote:
> https://bugs.launchpad.net/ubuntu/+bug/371614/comments/2 should explain
> it.
>
How did you install intrepid?
The default has always been RAMRUN=yes in Ubuntu
Scott
--
Scott James Remnant
sc...@canonical.com
--
Upgrade 8.10 --> 9.04 : ext3 File
https://bugs.launchpad.net/ubuntu/+bug/371614/comments/2 should explain
it.
My Filesystem is fine! No errors, checked 3 times!
Reproduce it with "quiet splash" as kernel parameter and uncomment RAMRUN=yes
/etc/default/rcS (only if you have ext2/ext3 filesystem, see source code).
On my system a "
Please explain your comment: "
error in initscripts
"
right now, this looks like you have a filesystem error that you haven't
fixed
** Changed in: sysvinit (Ubuntu)
Status: New => Incomplete
--
Upgrade 8.10 --> 9.04 : ext3 Filesystem read-only
https://bugs.launchpad.net/bugs/371614
typo: checkroot.sh not checkfs.sh !
Why is it not possible to edit my own comment?
--
Upgrade 8.10 --> 9.04 : ext3 Filesystem read-only
https://bugs.launchpad.net/bugs/371614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
The upgrade intrepid -> jaunty did not write the defaults in
/etc/default/rcS
RAMRUN=yes
is needed, if booted with 'splash quiet' (quiet makes VERBOSE=yes),
because the script /etc/init.d/checkfs.sh (called at
/etc/rcS.d/S20checkroot.sh) needs a writable /var/run:
PROGRESS_FILE=`mktemp -p /var/r
error in initscripts
** Package changed: ubuntu => sysvinit (Ubuntu)
--
Upgrade 8.10 --> 9.04 : ext3 Filesystem read-only
https://bugs.launchpad.net/bugs/371614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
13 matches
Mail list logo
