Re: support for mounting md(4) based filesystem at boot [PATCHES]
Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Johny Mattsson writes: This archive contains a number of files, including four rc.d scripts, a rc.conf diff, a couple of datafiles and some manpages for said data files. Okay, I probably made that sound a lot worse than it actually is. There is only one new fileformat in there (and it's documented). But I understand where your concern is coming from. I think we need somebody to reconsider how we configure our filesystems in the future, in order to avoid a confusion of config files whose interrelationship users will have no chance of figuring out. Are you referring just to the (currently messy) disk config/attach/whatever order, or a more drastic overhaul of how we configure disk settings? I haven't worked with CCD, Vinum, or GBDE (yet), so I'm not sure if I'll be a good person to tackle it, but I'll certainly give it some thought though. Sounds like an interesting little challenge that I may just be able to find time for :) Cheers, /Johny -- Johny Mattsson - System Designer ,-. ,-. ,-. There is no truth. http://www.earthmagic.org _.' `-' `-' There is only perception. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: support for mounting md(4) based filesystem at boot [PATCHES]
In message [EMAIL PROTECTED], Johny Mattsson writes: I think we need somebody to reconsider how we configure our filesystems in the future, in order to avoid a confusion of config files whose interrelationship users will have no chance of figuring out. Are you referring just to the (currently messy) disk config/attach/whatever order, or a more drastic overhaul of how we configure disk settings? I haven't worked with CCD, Vinum, or GBDE (yet), so I'm not sure if I'll be a good person to tackle it, but I'll certainly give it some thought though. Sounds like an interesting little challenge that I may just be able to find time for :) I don't know exactly what I am looking for, if I did, I'd just implement it, but I think that we should be able describe our disk configuration with just one single file in a human+program parseable format, rather than having to have one file per gadget. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: support for mounting md(4) based filesystem at boot [PATCHES]
Poul-Henning Kamp wrote: I don't know exactly what I am looking for, if I did, I'd just implement it, but I think that we should be able describe our disk configuration with just one single file in a human+program parseable format, rather than having to have one file per gadget. Sounds to me like if we indeed do this, we might have to move away from the traditional fstab (in order to deal better with dependencies), which I'm not sure is such a good idea. Then again, prior to 5.2 is probably the best chance we'll have for another couple of years to make such a drastic change. I'll give it some thought and come up with a draft proposal (unless someone else does it first). If anyone has recommendations on manpages, URLs, etc that they think would be useful background info, please let me know - for many of the 'gadgets' I'll be learning as I go. Cheers, /Johny -- Johny Mattsson - System Designer ,-. ,-. ,-. There is no truth. http://www.earthmagic.org _.' `-' `-' There is only perception. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
support for mounting md(4) based filesystem at boot [PATCHES]
Hi all, As promised a couple of days ago, here's the patch set to allow for mounting of md(4) based filesystems at boot time: http://www.earthmagic.org/~lonewolf/FreeBSD/mdmount.tar.gz This archive contains a number of files, including four rc.d scripts, a rc.conf diff, a couple of datafiles and some manpages for said data files. What this allows is to create/mount the various types of md nodes (vnode, malloc, swap) at boot time. I've been trying to think real hard on where in the boot order they need to go in order to provide the most benefit. There have been two conflicting directions; On the one hand there is the want to be able to attach to files residing on remote hosts (via nfs or samba), and on the other there is the need to cater for a swap backed /tmp filesystem. And also not to scribble on the swap before savecore has had a chance to run. I'm not sure I have got the position nailed down, and I'm open to constructive criticism. To take care of the permissions on a fresh /tmp, I have provided a 'fsperm' script which takes fs=mode pairs in an rc.conf variable and chmod's accordingly. Also of perhaps dubious validity is the fact that one of the scripts PROVIDE:s 'mountall', in the belief that this will not only provide a missing dependency, but also fill in the gap between mountcritremote and where mountall sits on NetBSD. I'm not terribly fussed either way, it was mainly just a convenient way to get rid of some of the errors rcorder(8) spits out, and make sure that things that depend on 'mountall' actually are run after all the filesystems have been made available. While I believe that these scripts are somewhat mature (read: hasn't newfs'd the wrong slice yet), the standard disclamer applies, ESPECIALLY SINCE NEWFS(8) IS RUN! Well, under certain circumstances it is, anyway. Questions, comments, and requests are very welcome. I'd very much like to see this (or something functionally equivalent) added in time for 5.2. As always, it's because it's a personal itch of mine :) I've tried to make it a more generic scratch so that it'll be useful across the board, however. Seeing as we have such a nifty thing as md(4) (thanks phk!) it's a shame not being able to use it at boot by default. Since this is my first stab at rcNG scripts (and manpages for that matter), feel free to bash style etc accordingly. Regards, /Johny -- Johny Mattsson - System Designer ,-. ,-. ,-. There is no truth. http://www.earthmagic.org _.' `-' `-' There is only perception. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: support for mounting md(4) based filesystem at boot [PATCHES]
In message [EMAIL PROTECTED], Johny Mattsson writes: Hi all, As promised a couple of days ago, here's the patch set to allow for mounting of md(4) based filesystems at boot time: http://www.earthmagic.org/~lonewolf/FreeBSD/mdmount.tar.gz This archive contains a number of files, including four rc.d scripts, a rc.conf diff, a couple of datafiles and some manpages for said data files. I have not read you patch, and as such have no opinion on if it should go into the tree or not, but I have some general comments to make on this overall subject. I think we need somebody to reconsider how we configure our filesystems in the future, in order to avoid a confusion of config files whose interrelationship users will have no chance of figuring out. We have CCD, GBDE, MD and in the future likely other technologies for configuring the underlying devices, we have FSCK, UFS and NFS and other filesystems to mount. Somebody must be able to come up with some creative stuff here... ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: support for mounting md(4) based filesystem at boot [PATCHES]
+---[ Poul-Henning Kamp ]-- | | I think we need somebody to reconsider how we configure our filesystems | in the future, in order to avoid a confusion of config files whose | interrelationship users will have no chance of figuring out. | | We have CCD, GBDE, MD and in the future likely other technologies for | configuring the underlying devices, we have FSCK, UFS and NFS and | other filesystems to mount. | | Somebody must be able to come up with some creative stuff here... ? We want A REGISTRY! Ni! Ni! Ni! Ni! Ni! Ni! -- Totally Holistic Enterprises Internet| | Andrew Milton The Internet (Aust) Pty Ltd | M:+61 416 022 411 | ACN: 082 081 472 ABN: 83 082 081 472 |[EMAIL PROTECTED]| Carpe Daemon ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
