arla 0.21 Oops on Linux 2.2.1
Neulinger, Nathan R.
nneul at umr.edu
Fri Feb 5 22:55:20 CET 1999
> -----Original Message-----
> From: Magnus Ahltorp [mailto:map at stacken.kth.se]
> Sent: Friday, February 05, 1999 3:28 PM
> To: chuckl at netscape.com
> Cc: arla-drinkers at stacken.kth.se
> Subject: Re: arla 0.21 Oops on Linux 2.2.1
>
>
> > btw, it would be really cool if the default "make install" process
> > (on Linux, anyway) put xfs.o in /lib/modules/`uname
> -r`/fs/xfs.o instead
> > of in /usr/arla/bin.
>
> I will look into that.
Please don't. At least not as part of the "install" target. A
"modules_install" target or something would be better. I'd actually like it
to 'install' to $(prefix)/bin, and then make a copy into the modules tree.
If you wanted to name it according to the kernel version, that would be fine
as well.
The reason for my objection is that once you start wiring paths based on
anything other than $(prefix), it becomes a pain to maintain for numbers of
machines. In particular, locally we install everything to AFS, and
occasionally overlay that onto the local machine.
I personally really dislike it when I tell a product to install to
/some/path and it goes and put's something in another directory. (Netatalk
went and installed stuff into my pam directory for example.) If I hadn't of
been paying complete attention, I never would have been able to take that
install to another machine and have it work, since I wouldn't have been
aware of that pam config file.
> > is arlad also dependent on the kernel version?
>
> No.
>
> /Magnus
> map at stacken.kth.se
>
More information about the Arla-drinkers
mailing list