From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Michael Richardson <mcr@sandelman.ottawa.on.ca>,
Rob Landley <rob@landley.net>
Subject: Re: [uml-devel] How stable is hostfs (and UML in general)?
Date: Wed, 12 Jan 2005 00:23:05 +0100 [thread overview]
Message-ID: <200501120023.05580.blaisorblade@yahoo.it> (raw)
In-Reply-To: <11049.1105479264@marajade.sandelman.ottawa.on.ca>
On Tuesday 11 January 2005 22:34, Michael Richardson wrote:
> >>>>> "Rob" == Rob Landley <rob@landley.net> writes:
>
> Rob> Chapter 5 of current variants of LFS uses the host system to
> Rob> create a toolchain you can chroot into and build the final
> Rob> system with. Then in chapter 6, you build the final system in
>
> I think the use of chroot is a cop-out.
>
> Rob> This requires root access (as does creating device nodes,
> Rob> mounting /proc or loopback devices... A rather large number of
>
> I use "fakeroot" to do all of that for embedded work that I do...
What's this?
> dd if=/dev/zero bs=1024k count=64 of=MYSWAP
Please add a "mkswap MYSWAP" here (or even inside the guest,
mkswap /dev/ubd1).
> ./linux ubd1=./MYSWAP
>
> Rob> The tee output of four consecutive runs is attached. All I did
> Rob> each time was ctrl-c out of the hang, cursor up, change the
> >> You could hit ^C from a hang?
> Rob> /dev/console attaches to fd0 and fd1. These are not ttys/ptys
> Rob> but file descriptors, hence they controlling tty sends the kill
> Well, usually, once the system is properly initialized, ^C does
> nothing. If you get a kernel panic/hang, I usually have to use kill from
> another window.
Yes, that's because it turns the console to raw mode (don't ask me why).
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-01-11 23:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 2:06 [uml-devel] How stable is hostfs (and UML in general)? Rob Landley
2005-01-09 6:00 ` Frank Sorenson
2005-01-09 22:06 ` Rob Landley
2005-01-10 1:53 ` Henrik Nordstrom
2005-01-10 6:34 ` Rob Landley
2005-01-10 13:47 ` Blaisorblade
2005-01-10 17:08 ` Nix
2005-01-10 14:43 ` Blaisorblade
2005-01-11 6:10 ` Rob Landley
2005-01-10 0:05 ` Michael Richardson
2005-01-10 6:20 ` Rob Landley
2005-01-10 6:41 ` Rob Landley
2005-01-10 8:48 ` Henrik Nordstrom
2005-01-11 5:58 ` Rob Landley
2005-01-10 15:21 ` Michael Richardson
2005-01-11 6:35 ` Rob Landley
2005-01-11 11:27 ` Henrik Nordstrom
2005-01-11 21:34 ` Michael Richardson
2005-01-11 23:23 ` Blaisorblade [this message]
2005-01-12 16:55 ` Michael Richardson
2005-01-12 17:09 ` Blaisorblade
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200501120023.05580.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=mcr@sandelman.ottawa.on.ca \
--cc=rob@landley.net \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox