Re: [Vectorlinux-devel] Hardware Config

[Tony B. <tb...@gm...>]

I did some testing last night and it made no difference.  I also found that
hotplug is running but it is sysvinit.  I made a coldplug script but it
didn't work.

The other option we have is the udevsynthesize patch for udev.  It removes
the need for udevstart and coldplug and can actually go through and setup
all the /dev/ entries and load modules in about 1 second on a
1.7Gigprocessor.  Hotplug on my AthlonXP 2400+(which is overclocked
like a 2900+
or better) takes 7 seconds in addition to the udevstart time.

Also while looking into the whole udev thing there is a lot of confusion.
The VL package on SOHO says 0.71 version but in the package contents it is
udev-0.64.  What is this about?  It looks like the packlage was created
manually so an uninstall of that package would fail as the slack tools stri=
p
out the 1st 2 characters which should be ./ so whomever packaged that up
really needs to package it up using this type of command from the root of
the filesystem:

tar cvzpf udev-0.71.....tgz ./install ./usr...... etc - there must always b=
e
a ./ before the folder name so that the slack install doesn't strip it out.

If you folks want, I can patch udev with udevsynthesize and create a proper
new package.  This would completely eliminate the need for hotplug but we
would have to make sure all of our udev rules, scripts, and permissions
files were complete.

Regards,
Tony


On 3/8/06, Tony Brijeski <tb...@gm...> wrote:
>
> I have done some digging and coldplug is actually just the old hotplug
> *.rc scripts.  We have hotplug installed and there but it needs to be cal=
led
> after udev is started.
>
> rc.hotplug is what coldplug really is.  If it is run after udev, then the
> devices will be setup.  I will do some testing and if all is well, this
> should be a wash to just add to rc.S after starting udev.
>
> I'm testing it now and will let you all know.
>
> Regards,
> Tony
>
>
>
>
>
>
>
> On 3/7/06, uel archuletta < ue...@gm...> wrote:
> >
> > I also have the udev and rules from zenwalk and it replaces hotplug as
> > well
> > so besides X setup like you said se have other options.
> >
> >
> > Uel
> >
> >
> >
> > On 3/7/06, Tony Brijeski <tb...@gm...> wrote:
> > >
> > > How much of vlsetup is still being used to configure the hardware and
> > > how much of udev/hotplug are we now using?
> > >
> > > I think we should concentrate on setting up udev to handle pretty muc=
h
> > > everything vlsetup used to but it will be on the fly during boot.
> > >
> > > Mandriva has setup some great scripts and rules for udev to take care
> > > of most of the hardware so a hardware probe is not necessary anymore =
other
> > > than for X setup.
> > >
> > > Let me know your thoughts on this.  If we still want to keep vlsetup,
> > > then I will either have to try to find the source for it in one of my=
 very
> > > old backups or I will have to take a look at the current hwsetup from
> > > knoppix and start from scratch again.
> > >
> > > I am thinking that the current state of udev makes most of vlsetup
> > > useless.  If we have the right scripts and rules, there should be no
> > > problems with letting udev take care of all of it.
> > >
> > > Regards,
> > > Tony
> > >
> > >
> >
>