From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Kernel sources thread
Date: Mon, 26 Jul 2004 10:26:14 -0400 [thread overview]
Message-ID: <1090851973.13632.71.camel@localhost> (raw)
In-Reply-To: <1090772040.16989.34.camel@garath.homelinux.org>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
On Sun, 2004-07-25 at 12:14, Paul Varner wrote:
> Normally, I would completely agree with you. However, vmnet1 and vmnet8
> while being network devices do require a device node. If the following
> nodes don't exist, they don't work!
>
> crw-r--r-- 1 root root 119, 0 Jul 24 22:25 /dev/vmnet0
> crw-r--r-- 1 root root 119, 1 Jul 24 22:25 /dev/vmnet1
> crw-r--r-- 1 root root 119, 8 Jul 24 22:25 /dev/vmnet8
>
> Finally, just to be clear, this is something for vmware to fix with
> their drivers, not the udev developers. I was just pointing out that
> currently vmware doesn't "just work" with a pure udev system.
Bug #54629
--
Chris Gianelloni
Release Engineering QA Manager/Games Developer
Gentoo Linux
Is your power animal a penguin?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-26 14:40 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 22:30 [gentoo-dev] Kernel sources thread Joel Konkle-Parker
2004-07-16 23:36 ` Grant Goodyear
2004-07-16 23:45 ` Ciaran McCreesh
2004-07-17 0:06 ` Greg KH
2004-07-17 0:32 ` Ciaran McCreesh
2004-07-18 17:53 ` Dylan Carlson
2004-07-18 18:10 ` Ciaran McCreesh
2004-07-18 19:18 ` Dylan Carlson
2004-07-21 5:32 ` Greg KH
2004-07-18 21:23 ` Georgi Georgiev
2004-07-21 5:38 ` Greg KH
2004-07-21 5:59 ` Georgi Georgiev
2004-07-21 13:29 ` Paul Varner
2004-07-22 6:55 ` Greg KH
2004-07-25 16:14 ` Paul Varner
2004-07-25 16:55 ` Ciaran McCreesh
2004-07-25 17:51 ` Paul Varner
2004-07-26 14:26 ` Chris Gianelloni [this message]
2004-07-26 21:25 ` Donnie Berkholz
2004-07-26 23:27 ` Georgi Georgiev
2004-07-27 12:38 ` Chris Gianelloni
2004-07-21 20:29 ` Chris Gianelloni
2004-07-21 5:29 ` Greg KH
2004-07-18 22:53 ` Travis Tilley
2004-07-18 23:22 ` Ciaran McCreesh
2004-07-19 0:00 ` Martin Schlemmer
2004-07-21 5:28 ` Greg KH
2004-07-21 7:24 ` Travis Tilley
2004-07-21 10:34 ` Travis Tilley
2004-07-21 11:04 ` Carsten Lohrke
2004-07-22 7:40 ` [gentoo-dev] " Duncan
2004-07-22 10:44 ` Carsten Lohrke
2004-07-21 14:47 ` [gentoo-dev] " Georgi Georgiev
2004-07-21 18:16 ` Greg KH
2004-07-21 19:46 ` Ciaran McCreesh
2004-07-22 19:05 ` Martin Schlemmer
2004-07-24 4:09 ` Greg KH
2004-07-21 20:40 ` Chris Gianelloni
2004-07-22 19:06 ` Martin Schlemmer
2004-07-22 20:11 ` Mike Frysinger
2004-07-22 20:42 ` [gentoo-dev] RFC: factoring logic for selection of "safe" gcc -O flags in ebuilds (uclibc users take note) Gavin
2004-07-23 4:51 ` Andrew Ross
2004-07-22 21:44 ` [gentoo-dev] Kernel sources thread Martin Schlemmer
2004-07-23 3:31 ` Georgi Georgiev
2004-07-24 16:27 ` Martin Schlemmer
2004-07-25 1:43 ` Georgi Georgiev
2004-07-25 6:44 ` Norberto Bensa
2004-07-25 17:56 ` Georgi Georgiev
2004-07-21 16:04 ` Norberto Bensa
2004-07-21 18:07 ` Greg KH
2004-07-21 5:42 ` Greg KH
2004-07-17 5:33 ` Wade Nelson
2004-07-17 6:19 ` Greg KH
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=1090851973.13632.71.camel@localhost \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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