On Mon, Jan 18, 2010 at 1:01 AM, Evangelos Foutras wrote:
> On 18/01/2010 12:42 πμ, Tom wrote:
>>>
>>> That code is here:
>>>
>>> http://projects.archlinux.org/initscripts.git/tree/rc.sysinit?id=2009.08-1#n266
>>>
>>> Looks correct to me.
>>
>> Thanks,
>>
>> but then it doesn't skip fsck when hitt
On 18/01/2010 12:42 πμ, Tom wrote:
That code is here:
http://projects.archlinux.org/initscripts.git/tree/rc.sysinit?id=2009.08-1#n266
Looks correct to me.
Thanks,
but then it doesn't skip fsck when hitting control-c but drops
to /sbin/sulogin ?
Maybe fsck doesn't return 32 as it's supposed
> That code is here:
> http://projects.archlinux.org/initscripts.git/tree/rc.sysinit?id=2009.08-1#n266
>
> Looks correct to me.
Thanks,
but then it doesn't skip fsck when hitting control-c but drops
to /sbin/sulogin ?
On 17/01/2010 11:42 μμ, Tom wrote:
All this aside, rc.sysinit is SUPPOSED to handle user cancellation.
Remember fsck returns 32 if the user cancels it.
if [ ${fsckret} -gt 1 -a ${fsckret} -ne 32 ]; then
Could you perhaps post all of the relevant code, because I don't see it
skipping the s
> All this aside, rc.sysinit is SUPPOSED to handle user cancellation.
> Remember fsck returns 32 if the user cancels it.
>
> if [ ${fsckret} -gt 1 -a ${fsckret} -ne 32 ]; then
Could you perhaps post all of the relevant code, because I don't see it
skipping the su-login part!?
Am Fri, 15 Jan 2010 20:12:09 -0500
schrieb Alexander Lam :
> I just tried Control-C during a regularly scheduled fsck on my system
> and it stopped the fsck and booted normally, so that should have
> worked for you.
And if fsck couldn't be stopped by Ctrl-C this would be an upstream
issue and has
Tom,
I just tried Control-C during a regularly scheduled fsck on my system and it
stopped the fsck and booted normally, so that should have worked for you.
Tom wrote:
While it is a hair misleading, entering the root password at this
point gets you to your system.
No, it does not. You get dropped to a promt, I don't know which
'init-level' its on, but it generally does not get you to your system
like a normal boot.
Single user is the init level y
On Fri, Jan 15, 2010 at 1:53 PM, Baho Utot wrote:
> Tom wrote:
>> and went and made myself a nice hot cup of tee,
> I use jfs so a fsck takes very little time. You may want to try it too.
...and ext4 takes about 7 seconds to fsck my 120GB root partition.
Hardly an issue IMO.
On Fri, Jan 15, 2010 at 3:35 PM, Tom wrote:
>> While it is a hair misleading, entering the root password at this
>> point gets you to your system.
>
> No, it does not. You get dropped to a promt, I don't know which
> 'init-level' its on, but it generally does not get you to your system
> like a no
Tom wrote:
I was just forced to waste 10 min of my life because of arch-linux-way
'of doing things'.
*rant mode on*
Let me elaborate,
for quite some time now, I've been unappeased by the way arch-linux
handles the boot-up process, not so much by how it actually does it (it
normally gets the job
> While it is a hair misleading, entering the root password at this
> point gets you to your system.
No, it does not. You get dropped to a promt, I don't know which
'init-level' its on, but it generally does not get you to your system
like a normal boot.
> Also, to shut off automatic fsck at boot
On Fri, Jan 15, 2010 at 2:51 PM, Tom wrote:
> I was just forced to waste 10 min of my life because of arch-linux-way
> 'of doing things'.
>
> *rant mode on*
> Let me elaborate,
> for quite some time now, I've been unappeased by the way arch-linux
> handles the boot-up process, not so much by how i
I was just forced to waste 10 min of my life because of arch-linux-way
'of doing things'.
*rant mode on*
Let me elaborate,
for quite some time now, I've been unappeased by the way arch-linux
handles the boot-up process, not so much by how it actually does it (it
normally gets the job done) but mor
14 matches
Mail list logo
