On Sun, Sep 01, 2013 at 01:41:30PM +0800, Mark David Dumlao wrote > Case in point - do you enable all the ext4 options, like acls and > whatnot? Let's say no. > > What if you suddenly have to mount an external hard disk to > recover some system on your server and the hard disk uses those ext4 > options? If ext4 is hard built into your kernel, your recompile will > have to basically redo the whole thing, whereas if ext4 was a module > you would only recompile ext4 itself.
Have you ever actually done this? I'd be very leery of pulling such a stunt. The clean way of switching module versions is to... * unload the old module, and * load the new module You obviously can't do this in your setup, because unloading the old module would mean you could no longer access the file system to read in the new module... OOPS. You could run a script that creates /dev/shm/lib/3.1.4.1.5.9-gentoo/ (easy as pie<G>) and copies the new module to that dir. Then unload the old module and load the new one, using modprobe with "-d /dev/shm/". That still looks impossible. The problem is that you generally have a whole bunch of files open at any time. E.g. try... lsof -d txt | grep -v "/proc/" | less ...and look at the output. Shutting down all those open files would be disastrous. But that's not what you're saying. You seem to imply that file system code can be overwritten *IN PLACE, WHILE IN USE*, without any problems. Colour me skeptical about that one. -- Walter Dnes <waltd...@waltdnes.org> I don't run "desktop environments"; I run useful applications
