colinux-users

[coLinux-users] Enable config_hotplug in kernel .config

[Ron H. <he...@gm...>]

I am in the process of building a custom kernel for use with coLinux to
enable hotplug support.  I am assuming  that since coLinux prevents
interaction directly with the hosts hardware, hotplug support was deemed
unnecessary.

However, devices such as /dev/net/tun need hotplug support to work properly
with udev.  May I suggest that future coLinux default kernel configurations
have config_hotplug enabled?

Ron Helzer
he...@gm...

Re: [coLinux-users] Enable config_hotplug in kernel .config

[George P B. <geo...@gm...>]

Let us know how your custom kernel goes...  If you don't experience
too many problems with it enabled, then we can test it and see how it
makes out.

On 9/9/06, Ron Helzer <he...@gm...> wrote:
> I am in the process of building a custom kernel for use with coLinux to
> enable hotplug support.  I am assuming  that since coLinux prevents
> interaction directly with the hosts hardware, hotplug support was deemed
> unnecessary.
>
> However, devices such as /dev/net/tun need hotplug support to work properly
> with udev.  May I suggest that future coLinux default kernel configurations
> have config_hotplug enabled?

-- 
George

Re: [coLinux-users] Enable config_hotplug in kernel .config

[Ron H. <he...@gm...>]

I enabled config_hotplug and the kernel compiled and worked fine, but it
didn't solve my problem of no /dev/net/tun device file upon modprobing the
tun module.  I am not a hotplug or udev guru, I'm a devfs kind of guy, so I
may be doing something else wrong.  I decided once I was able to customize
the coLinux kernel, instead of modular tun and hotplug nonsence I would just
make tun part of the kernel and that fixed it for good.

I am running Gentoo in my coLinux, and they provide an option in
/etc/conf.d/rc to tar the contents of the /dev tempfs to be restored at next
boot which would also solve the problem if you makedev the /dev/net/tun
device yourself.

I would like to know if what I was attempting with hotplug is possible in
coLinux and where I went wrong.  If I find the time, I'll boot a test
instance and look into it more fully.

Ron Helzer
he...@gm...

On 9/9/06, George P Boutwell <geo...@gm...> wrote:
>
> Let us know how your custom kernel goes...  If you don't experience
> too many problems with it enabled, then we can test it and see how it
> makes out.
>
> On 9/9/06, Ron Helzer <he...@gm...> wrote:
> > I am in the process of building a custom kernel for use with coLinux to
> > enable hotplug support.  I am assuming  that since coLinux prevents
> > interaction directly with the hosts hardware, hotplug support was deemed
> > unnecessary.
> >
> > However, devices such as /dev/net/tun need hotplug support to work
> properly
> > with udev.  May I suggest that future coLinux default kernel
> configurations
> > have config_hotplug enabled?
>
> --
> George
>

Re: [coLinux-users] Enable config_hotplug in kernel .config

[George P B. <geo...@gm...>]

On 9/9/06, Ron Helzer <he...@gm...> wrote:
> I enabled config_hotplug and the kernel compiled and worked fine, but it
> didn't solve my problem of no /dev/net/tun device file upon modprobing the
> tun module.  I am not a hotplug or udev guru, I'm a devfs kind of guy, so I
> may be doing something else wrong.  I decided once I was able to customize
> the coLinux kernel, instead of modular tun and hotplug nonsence I would just
> make tun part of the kernel and that fixed it for good.

I'm no good with udev either. Sorry!  I wasn't even ever good at
devfs...  I tend to manually create and maintain my /dev
directories...  I know... I know...  For me it works and it's a big
deal.

> I would like to know if what I was attempting with hotplug is possible in
> coLinux and where I went wrong.  If I find the time, I'll boot a test
> instance and look into it more fully.

I'm not 100%, but I believe we disabled it is because with it enabled,
some distros (Fedora?, Ubuntu? mabye) would crash/die on boot-up
because they where trying to access hardware directly with hotplug,
which is always a bad thing in coLinux.  I'll play with hotplug
enabled a default and a few distros and see what comes of it.

-- 
George

Re: [coLinux-users] Enable config_hotplug in kernel .config

[Anders E. C \(KI/EAB\) <and...@er...>]

=20

>=20
> On 9/9/06, Ron Helzer <he...@gm...> wrote:
> > I enabled config_hotplug and the kernel compiled and worked=20
> fine, but it
> > didn't solve my problem of no /dev/net/tun device file upon=20
> modprobing the
> > tun module.  I am not a hotplug or udev guru, I'm a devfs=20
> kind of guy, so I
> > may be doing something else wrong.  I decided once I was=20
> able to customize
> > the coLinux kernel, instead of modular tun and hotplug=20
> nonsence I would just
> > make tun part of the kernel and that fixed it for good.
>=20
> I'm no good with udev either. Sorry!  I wasn't even ever good at
> devfs...  I tend to manually create and maintain my /dev
> directories...  I know... I know...  For me it works and it's a big
> deal.
>=20

I can attest that hotplug is needed (in my experience) with >2.6.15
kernels to get any signals from the kernel to the udev daemon
on startup. Otherwise your udev managed /dev ends up with only a
handfull of entries.=20

/Anders