Re: automount based devfs replacement

From: Andreas Haumer (andreas@xss.co.at)
Date: Fri Apr 28 2000 - 09:26:54 EST


Hi!

Chip Salzenberg wrote:
>
> According to A. Haumer:
> > > cp -a /dev/* /mnt > /dev/null 2>&1
> > > umount /dev/ram1 > /dev/null 2>&1
> > > mount /dev/ram1 /dev -t minix -o rw > /dev/null 2>&1
> > > echo "done."
> >
> > Well, that's what I consider a real "hack". Not what *I* want to
> > have in my production systems... :-)
>
> I use it in a production system. 100% reliable.
>
Fine for you.

> > What if you want to change something in your device structure,
> > e.g. when a new device driver is loaded? You have to rebuild
> > your device ramdisk!
>
> I do the copy in /etc/init.d at each boot. The ramdisk image is
> not stored anywhere.

I do believe you this works. In Unix you can do many things in
many different ways. I didn't say it can't be done without devfs.

But with devfs it can be done in a much more elegant way. And also
faster, easier to setup, configure and maintain. That's why I keep
saying the create-ramdisk-copy-file-umount-mount thing is a hack!

- andreas

-- 
Andreas Haumer                     | mailto:andreas@xss.co.at
*x Software + Systeme              | http://www.xss.co.at
Karmarschgasse 51/2/20             | Tel: +43-1-6060114-0
A-1100 Vienna, Austria             | Fax: +43-1-6060114-71

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Sun Apr 30 2000 - 21:00:15 EST