On Wed 26 Mar 2003 05:01, Pixel posted as excerpted below: > Duncan <[EMAIL PROTECTED]> writes: > > The resulting fstab is attached as fstab.munched. Not only are all those > > notes about options gone, but so is my nice ordering by function. > > Furthermore, all my devfs-failure-safe paths have disappeared [] > > this is the contrary. If devfs fail to mount, your solution is bad. It > is if devfsd fail to run that your solution is better.
Aye. My mistake then. All I know is it didn't work, and these paths did. > handling everything the way everyone want need artificial > intelligence. > > more precisely, having it keep the order could be done. Keeping > spacing could be done too. But this is not easy, and will introduce > bugs for sure. > > same (but even worse) for XFdrake I figured XFdrake was to much to hope for, as that gets /very/ complicated to try and get it all right, with multiple screens, etc. Perhaps someday.. as MSWormOS seems to handle it all pretty well automatically, multiple screens and all. (You can even set up comments in separate value/data entries in the registry, and the automated thing doesn't touch them -- it ignores them as something it doesn't know about.) However, in that respect, Linux (not just Mdk) still has some ways to go. Still, would be nice to have automated tools that leave the current situation as-is in fstab, if all you are doing is adding a mount entry, given that there's no reason it would need to change the order. Even changing an entry shouldn't in theory be impossible or even incredibly difficult to do in place, leaving all other lines as they are. That's certainly easier than it would be in a critically sectionaized ordering such as XF86Config. However, at least it doesn't miss-parse comments as mount-points, as it did, to my dismay, in Mdk 8.1 or so. <g> Thus, what remains isn't so critical. Thanks! -- Duncan "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -- Benjamin Franklin
