Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Booting from CF/stik is interesting.
0 views
Skip to first unread message
no.to...@gmail.com
May 1, 2012, 2:35:53 PM5/1/12
to
This interesting/novel log of booting from USBstik and
Compact Flash is relevant to Debian, Slackware and
other distributions, and consequently this post is NOT
inappropriately cross-posted.
All clik-jockeys exit here ->
Debian-Etch boots, but Slackware13 & k [a slak13
derivative] give errors: <can only see the dev/sda1,2,3,4
of the Win-7hard-drive>.
`chrooting` to slak & k from Etch proves nothing, because
you'd apparently be using Etch's drivers.
But here's the interesting symptom IMO: when k
halt's with the error, you see the trace completed
<loading USB drivers> and importantly, the message is
<Ctrl/Alt/Del to reboot and move a dir to C:\>
Now if a system can respond to Ctrl/Alt/Del ,
it's quiet far into the boot process.
And importantly, in this case single-user-ash is
available. So you can mount and chroot to any of
the other distributions: Slak13, DebEtch, DebLenny,
mulinux.
So, if after k has halted, complaining of not being
able to read a critical dir because of <can't do SCSI>;
why can it read that directory, and all other CF &
stik ext2 & ext3, after it's halted and complained?
As explained in a previous post the CF:slak ALSO
suggests a race effect problem. I suspect K, too,
once it's stopped to complain, and some hardware
has settled, IS able to read as would be require to
complete the boot process.
WDYS?
== TIA.
Compact Flash is relevant to Debian, Slackware and
other distributions, and consequently this post is NOT
inappropriately cross-posted.
All clik-jockeys exit here ->
Debian-Etch boots, but Slackware13 & k [a slak13
derivative] give errors: <can only see the dev/sda1,2,3,4
of the Win-7hard-drive>.
`chrooting` to slak & k from Etch proves nothing, because
you'd apparently be using Etch's drivers.
But here's the interesting symptom IMO: when k
halt's with the error, you see the trace completed
<loading USB drivers> and importantly, the message is
<Ctrl/Alt/Del to reboot and move a dir to C:\>
Now if a system can respond to Ctrl/Alt/Del ,
it's quiet far into the boot process.
And importantly, in this case single-user-ash is
available. So you can mount and chroot to any of
the other distributions: Slak13, DebEtch, DebLenny,
mulinux.
So, if after k has halted, complaining of not being
able to read a critical dir because of <can't do SCSI>;
why can it read that directory, and all other CF &
stik ext2 & ext3, after it's halted and complained?
As explained in a previous post the CF:slak ALSO
suggests a race effect problem. I suspect K, too,
once it's stopped to complain, and some hardware
has settled, IS able to read as would be require to
complete the boot process.
WDYS?
== TIA.
Peter Köhlmann
May 1, 2012, 2:48:51 PM5/1/12
to
Dan C
May 1, 2012, 6:40:16 PM5/1/12
to
On Tue, 01 May 2012 18:35:53 +0000, no.top.post wrote:
<SNIP incoherent drivel>
> WDYS?
I say you're a fucking moron. Fuck off and die, and take your bullshit
somewhere else, troll boy.
--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he launched a Maverick.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
Thanks, Obama: http://brandybuck.site40.net/pics/politica/thanks.jpg
<SNIP incoherent drivel>
> WDYS?
I say you're a fucking moron. Fuck off and die, and take your bullshit
somewhere else, troll boy.
--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he launched a Maverick.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
Thanks, Obama: http://brandybuck.site40.net/pics/politica/thanks.jpg
0 new messages