From: Jeff Dike <jdike@addtoit.com>
To: Kyrre M Begnum <Kyrre.Begnum@iu.hio.no>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] 2.6.10 command line longer than 512 characters
Date: Tue, 01 Mar 2005 16:36:42 -0500 [thread overview]
Message-ID: <200503012137.j21LagMY009262@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Fri, 07 Jan 2005 11:12:42 +0100." <Pine.LNX.4.58.0501071105351.22595@cube.iu.hio.no>
Kyrre.Begnum@iu.hio.no said:
> I have noticed that when I supply a command line longer than 513
> characters (or was it 512?) the kernel crashes. Output supplied at the
> end of mail. This does not seem to be a problem on the old 2.4.24
> guest kernels. Is there a way I can change this, perhaps during kernel
> configuration?
This is fixed in my long-command-line patch.
Jeff
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
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-03-01 19:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 10:12 [uml-devel] 2.6.10 command line longer than 512 characters Kyrre M Begnum
2005-01-07 10:25 ` Catalin(ux aka Dino) BOIE
2005-01-07 10:56 ` Kyrre M Begnum
2005-01-07 11:02 ` Catalin(ux aka Dino) BOIE
2005-01-08 11:15 ` Blaisorblade
2005-03-01 21:36 ` Jeff Dike [this message]
2005-03-01 19:51 ` Kyrre M Begnum
2005-03-02 16:43 ` 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=200503012137.j21LagMY009262@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=Kyrre.Begnum@iu.hio.no \
--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