> > can someone investigate this ? the code seems to work fine on 3.x > > Someone also sent me a report on that, so it's a real problem. I have a > traceback, but without debugging symbols. it's so easy to reproduce that i hope the vm/vn gurus will not require too much effort to find the bug. in the meantime, what you suggest (for picobsd builds that is) ? use a real floppy ? cheers luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- problem with vnconfig -s labels ... Luigi Rizzo
- Re: problem with vnconfig -s labels ... Andrzej Bialecki
- Re: problem with vnconfig -s labels ... Luigi Rizzo
- Re: problem with vnconfig -s labels ... Andrzej Bialecki
- Re: problem with vnconfig -s labels ... Poul-Henning Kamp
- Re: problem with vnconfig -s labels ... Andrew Atrens
- Re: problem with vnconfig -s labels ... Andrew Atrens
- Re: problem with vnconfig -s labels ... Luigi Rizzo
- Re: problem with vnconfig -s labels ... John Birrell
- Re: problem with vnconfig -s labels ... Poul-Henning Kamp
- Re: problem with vnconfig -s label... John Birrell
- Re: problem with vnconfig -s l... Poul-Henning Kamp
- Re: problem with vnconfig -s labels ... Bruce Evans