From: "roland" <for_spam@gmx.de>
To: Mark Olliver <mpo@thermeoneurope.com>,
user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>, blaisorblade_spam@yahoo.it
Subject: [uml-devel] poll: uml bug management - was: Re: [uml-user] 2.6.6 Kernel mconsole & mem
Date: Wed, 19 May 2004 00:12:40 +0200 [thread overview]
Message-ID: <093601c43d25$42633a20$2000000a@schlepptopp> (raw)
In-Reply-To: 40AA0BD9.7070403@thermeoneurope.com
have seen the same problem with a uml 2.6.6 guest compiled and running on a suse 9.1 host.
(mkstemp failed and left processes after shutdown)
what`s your host OS ?
what`s your guest rootfs?
do you use skas or tt ?
btw: should we file a bug-report at:
http://sourceforge.net/tracker/?group_id=429&atid=100429
or shouldn`t that bugtracker not being used anymore - in general ?
if not, IMHO that bugtracker should be marked "obsolete"(like the SF cvs repository) - otherwise
newbies will file reports there and get pissed , because nobody cares about.
on that page there still are bugs "open" for years now - and nobody knows, if they still exist, or
not.
i think it`s very difficult, to track bugs on the mailinglist, only.
we know, that jeff is collecting the bug reports:
>The bug tracker is the UML mailing lists. I stick bug reports and patches in
>a todo folder and delete them from there when I fix (or merge) them. I pay
>almost no attention to the SF patch and bug report thingies. So if you want
>your bug to get attention, send it to one of the lists.
imho, if uml users/developers probably hit a bug, they should be able to browse the list of
known uml bugs and add comments. this adds transparency and encourages people to try to reproduce.
furthermore, this could encourage people to "debug" some uml code, because they see: ohhh
- that bug has priority 9 for 6 months now - let`s have a look....i`m soo geeky - probably
i get this fixed :)
currently, there isn`t much transparency - users need to dig into the whole "noise" of the
mailinglist - and if a bug is reported on the mailinglist a while ago, jeff is the only person
to know, that this bug exists and still needs to be fixed.
i would like to give an example for a really nice "bug page":
http://rockbox.haxx.se/bugs.shtml
that page is created by a script, which extracts the information from SF and puts it into a
nicely formatted page:
http://cvs.sourceforge.net/viewcvs.py/rockbox/www/getbugs.pl
why not using it, too ?
i vote for it!
:)
comments ?
regards
roland
ps:
since such bug page needs maintenance - i offer doing that job (as good as i can).
----- Original Message -----
From: "Mark Olliver" <mpo@thermeoneurope.com>
To: <user-mode-linux-user@lists.sourceforge.net>
Sent: Tuesday, May 18, 2004 3:12 PM
Subject: [uml-user] 2.6.6 Kernel mconsole & mem
> Hi
>
> I am using a host and guest 2.6.6 kernel with uml and skas patches
> applied. I can get a uml instance to startup ok and can talk to it via
> the network.
>
> However, I can not communicate with it via mconsole, when it boots it
> gives me the error:
> make_umid - mkstemp failed, errno = 2
>
> also when I shut the uml instance down with a shutdown -h 0 is shuts
> down the instance but leaves a few processes running on the host system.
>
> I have been starting the instances using
> ./linux umid=uml127 ubd0=root_fs_cp127 udb1=swapfile-uml127
> eth0=tuntap,,,192.168.xxx.250
>
> Any ideas or suggestions of where I may have gone wrong are welcome.
>
> Thanks
>
> Mark
>
> --
> Mark Olliver
>
> Thermeon Europe Ltd.
>
> e-Card: http://www.thermeoneurope.com/e-Card/mpo
>
> Email mpo@thermeoneurope.com
> Web www.thermeoneurope.com
>
> Support 0906 515 0908
> Int. Support +44 1293 864 341
> Support Email support@thermeoneurope.com
>
> Sales +44 1293 864 334
> Sales Email sales@thermeoneurope.com
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> User-mode-linux-user mailing list
> User-mode-linux-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
>
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&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 parent reply other threads:[~2004-05-18 22:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40AA0BD9.7070403@thermeoneurope.com>
2004-05-18 22:12 ` roland [this message]
2004-05-19 7:47 ` [uml-devel] Re: poll: uml bug management - was: Re: [uml-user] 2.6.6 Kernel mconsole & mem Mark Olliver
2004-05-20 0:14 ` Jeff Dike
2004-05-19 23:59 ` roland
2004-05-20 14:24 ` Henrik Nordstrom
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='093601c43d25$42633a20$2000000a@schlepptopp' \
--to=for_spam@gmx.de \
--cc=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=mpo@thermeoneurope.com \
--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