raidtools and MAKEDEV

[Steve G]

Hi,

I was starting to test some of the newer MAKEDEV, udev, hal stuff and ran into
something that I don't remember anyone mentioning. Raidtools now dies on
installation:

93:procmail               ########################################### [ 42%]
  94:raidtools              ########################################### [ 42%]
/var/tmp/rpm-tmp.42736: line 2: ./MAKEDEV: No such file or directory
error: %post(raidtools-1.00.3-8) scriptlet failed, exit status 127
  95:rootfiles              ########################################### [ 42%]
  96:slocate

Looking at the raidtools spec file:

%post
cd /dev
./MAKEDEV -m 16 md

So I change raidtools to use /sbin/MAKEDEV and then it spews errors:

MAKEDEV: /dev/md0: unable to reset file creation context
MAKEDEV: /dev/md1: unable to reset file creation context

and this continues for all 16 devices. (I saw a new parameter in today's rawhide
report to suppress this kind of thing.) The installation is successful, though.

Does anyone else see raidtools die like this or is it just my setup and anaconda
takes care of these details? Do you want this in bugzilla? raidtools hasn't been 
updated for a long time.

Thanks,
-Steve Grubb

_______________________________
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.
http://promotions.yahoo.com/goldrush

[Alexandre Oliva]

On Sep  8, 2004, Steve G  wrote:
> %post
> cd /dev
> ./MAKEDEV -m 16 md

Looks definitely wrong for a udev system.  Please file this in
bugzilla, if you haven't done so yet.

[Harald Hoyer]

Alexandre Oliva wrote:
> On Sep  8, 2004, Steve G  wrote:
> > %post
> > cd /dev
> > ./MAKEDEV -m 16 md
>
> Looks definitely wrong for a udev system.  Please file this in
> bugzilla, if you haven't done so yet.

Well, /dev/MAKEDEV is a symlink to /sbin, if system was started with the new udev.

[Steve G]

> Looks definitely wrong for a udev system.  Please file this in
> bugzilla, if you haven't done so yet.
>
> Well, /dev/MAKEDEV is a symlink to /sbin, if system was started with the new 
> udev.

I just backed out my patch and it still fails. The problem is that udev is not
running when I do the installation. When the full path is given, there's no
problem during installation. This is not using anaconda, this is installing to a
test partition after building. You would never want udev to make entries into a
chroot test partition during install. Its fine when the system reboots to that
partition.

So what's the consensus? A quirk of my build system, or do you want to make
./MAKEDEV into a full path for raidtools? It should be simple enough to fix
raidtools to do this:

%post
cd /dev
%if [ -x ./MAKEDEV ] ; then
  ./MAKEDEV -m 16 md
%else
  /sbin/MAKEDEV -m 16 md
%fi

This solves it for old and new systems.

Thanks,
-Steve Grubb

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

[Jeremy Katz]

On Wed, 2004-09-08 at 13:58 -0700, Steve G wrote:
> Looking at the raidtools spec file:
>
> %post
> cd /dev
> ./MAKEDEV -m 16 md
>
> So I change raidtools to use /sbin/MAKEDEV and then it spews errors:

[snip]
> Does anyone else see raidtools die like this or is it just my setup and anaconda
> takes care of these details? Do you want this in bugzilla? raidtools hasn't been 
> updated for a long time.

This is broken... of course, the plan is to finish the switchover of
everything to using mdadm instead of raidtools (the only thing
outstanding is initscripts), at which point raidtools will die the death
it deserves. :)

Jeremy