** Changed in: upstart
Milestone: 0.5-later => None
** Summary changed:
- Fail to enter rc1.d by putting 1 in bootparam in edgy
+ compat: failed to enter rc1.d by putting 1 in boot param
--
compat: failed to enter rc1.d by putting 1 in boot param
https://bugs.launchpad.net/bugs/85014
You re
On Sat, 2009-02-14 at 05:28 +, Pat Regan wrote:
> I offered, although it seems not very strongly, to write up a fix for
> this problem in June of 2007. I asked again a few days ago if a patch
> would be welcome. I assume you're saying that assistance is not
> welcomed, then? The fix is simp
Scott James Remnant wrote:
> On Thu, 2009-02-12 at 02:47 +, Pat Regan wrote:
>> It doesn't really matter who he is addressing. The bug I reported over
>> a year ago that got pointed at this bug still exists today. If you
>> configure a server with a "-s" anywhere in the name AND use the serve
On Thu, 2009-02-12 at 02:47 +, Pat Regan wrote:
> Scott James Remnant wrote:
> > On Wed, 2009-02-11 at 16:05 +, dr.moe wrote:
> >
> >> And so ?
> >> How does this account for anything else ?
> >> (On a side note, the former message was addressing the team, obviously)
> >>
> > What team?
Scott James Remnant wrote:
> On Wed, 2009-02-11 at 16:05 +, dr.moe wrote:
>
>> And so ?
>> How does this account for anything else ?
>> (On a side note, the former message was addressing the team, obviously)
>>
> What team? The only person you're addressing here is me.
It doesn't really mat
On Wed, 2009-02-11 at 16:05 +, dr.moe wrote:
> And so ?
> How does this account for anything else ?
> (On a side note, the former message was addressing the team, obviously)
>
What team? The only person you're addressing here is me.
> As our final communication with Canonical; we decided to
Le mardi 10 février 2009 à 14:30 +, Scott James Remnant a écrit :
> On Thu, 2009-02-05 at 17:33 +, dr.moe wrote:
>
> > can't believe Scott James Remnant once wrote "This should be fixed
> > upstream" (in telinit ! ).
> >
> Scott James Remnant (me) _is_ upstream for telinit.
And so ?
How
On Thu, 2009-02-05 at 17:33 +, dr.moe wrote:
> can't believe Scott James Remnant once wrote "This should be fixed
> upstream" (in telinit ! ).
>
Scott James Remnant (me) _is_ upstream for telinit.
Scott
--
Scott James Remnant
sc...@canonical.com
--
Fail to enter rc1.d by putting 1 in boot
Hi all,
can't believe Scott James Remnant once wrote "This should be fixed
upstream" (in telinit ! ). Well, it still works for any other distro,
and I bet you'd get a good laugh from the upstream folks if they came
across this, which they may have since this issue came up a VERY long
time ago.
Thi
** Changed in: upstart
Target: None => 0.5-later
--
Fail to enter rc1.d by putting 1 in bootparam in edgy
https://bugs.launchpad.net/bugs/85014
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
It is important that this is fixed properly. With jigdo broken and now
this, it's hard for Ubuntu to be taken seriously.
Regarding the proposed "if" statement:
if [ -n "$RL" ]; then
telinit $RL
else
telinit 2
fi
This looks unnec
The problem still exists on Ubuntu 8.10.
--
Fail to enter rc1.d by putting 1 in bootparam in edgy
https://bugs.launchpad.net/bugs/85014
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
** Changed in: upstart
Target: 0.5 => None
--
Fail to enter rc1.d by putting 1 in bootparam in edgy
https://bugs.launchpad.net/bugs/85014
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
I'm happy with
...
elif grep -qE -- "[[:space:]]+[1-5]([[:space:]]|$)" /proc/cmdline; then
RL="$(grep -Eo -- "[[:space:]]+[1-5]([[:space:]]|$)" /proc/cmdline)"
if [ -n "$RL" ]; then
telinit $RL
else
telinit 2
fi
randominternet: ask yourself if you really need
runlevels?
There are two basic runlevel controls in the Unix/Linux world, the
System V way, and BSD way. They both have there own pros and cons, and
I am not going to debate them here. The way init scripts and run levels
work is well defined. It i
I think it's a bit of an overkill removing the standard Linux runlevel
behavior in Ubuntu. It's not "Noobs" that get to fiddle the runlevel,
rather people with more experience in Linux. Since this has no effect on
the "Noob" user interface, why not leave it as it was in good old Linux?
It is a usef
Yes, for myself I do need runlevels.
Say, if I want to turn on sshd in rc1 in some special case, and it would be
very easy for me, just link /etc/init.d/ssh in /etc/rc1.d would work. However,
if I use your method, I have to modify the /etc/init.d/ssh, and I might mess it
up. This is dirty hackin
ask yourself if you really need runlevels? (upstart admins dont' seem to
think so, they say on there site they are there for back compat only)
for my problem (running different non interactive partition to partition
dd scripts from grub option instead of normal bash prompt) I found I
could achieve
This is still broken in hardy:
adding '3' to the end of my grub command line still resulted in runlevel 2. It
appears that the fix mentioned in comment 4 hasn't yet made it to hardy.
--
Fail to enter rc1.d by putting 1 in bootparam in edgy
https://bugs.launchpad.net/bugs/85014
You received this
** Changed in: upstart
Status: Confirmed => Triaged
** Changed in: upstart (Ubuntu)
Status: Confirmed => Triaged
--
Fail to enter rc1.d by putting 1 in bootparam in edgy
https://bugs.launchpad.net/bugs/85014
You received this bug notification because you are a member of Ubuntu
Bugs
** Changed in: upstart (upstream)
Target: 0.3 => 0.5
--
Fail to enter rc1.d by putting 1 in bootparam in edgy
https://bugs.launchpad.net/bugs/85014
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
upstream: missing feature of telinit
Ubuntu: which means it has to be done in the Ubuntu-supplied jobs, badly
--
Fail to enter rc1.d by putting 1 in bootparam in edgy
https://bugs.launchpad.net/bugs/85014
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Tested with Xubuntu Feisty. Nothing happens, whatever is entered in the
grub-menu.lst kernel line.
Ugly.
--
Fail to enter rc1.d by putting 1 in bootparam in edgy
https://bugs.launchpad.net/bugs/85014
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug con
has anyone with feisty tested this?
--
Fail to enter rc1.d by putting 1 in bootparam in edgy
https://launchpad.net/bugs/85014
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I changed it and that didn't work for me either. still booting to
runlevel 2.
--
Fail to enter rc1.d by putting 1 in bootparam in edgy
https://launchpad.net/bugs/85014
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
For feisty, the rc-default is one line different from that in Edgy.
It's
start on stopped rcS
in the beginning.
--
Fail to enter rc1.d by putting 1 in bootparam in edgy
https://launchpad.net/bugs/85014
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/
the workaround fix doesn't work for me. i'm using feisty. is there any
other way to fix this, or is it even being worked on?
--
Fail to enter rc1.d by putting 1 in bootparam in edgy
https://launchpad.net/bugs/85014
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
This should be fixed upstream by adding a --default option to telinit;
and have that check things like the kernel command-line, and inittab
file, and then emit the appropriate runlevel event.
rc-default can then just be exec telinit --default
** Also affects: upstart (upstream)
Importance: Und
Oops... the above is not a good one, should be [0-9], however, if selinux=0 is
assigned in bootparam, upstart will go wrong.
Therefore maybe make it like:
--
start on rcS/stop
script
runlevel --reboot || true
if grep -q -w -- "-s\|single\|S" /proc/cmdline; then
te
OK, my workaround is to modify /etc/event.d/rc-default, and make it like the
following. It works for me. Thanks.
--
start on rcS/stop
script
runlevel --reboot || true
if grep -q -w -- "-s\|single\|S" /proc/cmdline; then
telinit S
elif grep -qE -w -- "[1-5]
This is caused by the rc-default script, which invokes the default
runlevel once the rcS job has stopped.
It does this by a combination of grep on the command-line and
/etc/inittab files, then invoking telinit with whatever argument it
found.
It only handles -s/single/S being on the command line,
31 matches
Mail list logo
