vn, vnconfig and MFS death-warrant!
I have made mount_mfs and vnconfig print a warning and sleep for 15 seconds before continuing. Please convert to using mdconfig(8) for TMPFS uses. March 1st I will remove the functionality from mount_mfs and vnconfig, leaving only the message which will be an error obviously. April 1st I will remove vn, vnconfig and mount_mfs entirely. -- 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. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vn, vnconfig and MFS death-warrant!
"Poul-Henning Kamp" [EMAIL PROTECTED] wrote in message news:29877.980850630@critter... I have made mount_mfs and vnconfig print a warning and sleep for 15 seconds before continuing. Please convert to using mdconfig(8) for TMPFS uses. March 1st I will remove the functionality from mount_mfs and vnconfig, leaving only the message which will be an error obviously. April 1st I will remove vn, vnconfig and mount_mfs entirely. Could these modifications be ported to -STABLE to ease up the transition from -STABLE to -CURRENT ? I don't know if this is tied deeply on other changes in -CURRENT, but if it is not I'd like to use the new facility. Let me know if you want me to do some testing prior to committing the changes to -STABLE. I will happily contribute any help I can. Patrick. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vn, vnconfig and MFS death-warrant!
In message [EMAIL PROTECTED], "Patrick Bihan-F aou" writes: Could these modifications be ported to -STABLE to ease up the transition from -STABLE to -CURRENT ? I don't know if this is tied deeply on other changes in -CURRENT, but if it is not I'd like to use the new facility. I think I would rather leave -stable out of this for now. There are too many deployed production systems I think. -- 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. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vn, vnconfig and MFS death-warrant!
At Tue, 30 Jan 2001 11:30:30 +0100, Poul-Henning Kamp [EMAIL PROTECTED] wrote: March 1st I will remove the functionality from mount_mfs and vnconfig, leaving only the message which will be an error obviously. April 1st I will remove vn, vnconfig and mount_mfs entirely. I think we should postpone the complete removing for a year (on release of 5.2), to give people a migration sugar. System upgrading (4.x - 5.x) will cause confusing situation, for example, living old 4.x vnconfig binary and new and splendid mdconfig. -- Motomichi Matsuzaki [EMAIL PROTECTED] Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: vn, vnconfig and MFS death-warrant!
Hi, Could these modifications be ported to -STABLE to ease up the transition from -STABLE to -CURRENT ? I don't know if this is tied deeply on other changes in -CURRENT, but if it is not I'd like to use the new facility. I think I would rather leave -stable out of this for now. There are too many deployed production systems I think. Just to make my intentions clear, I am not asking to remove vn/vnconfig(8)/mfs from -STABLE, I was just asking for the inclusion of md/mdconfig in -STABLE so that people (at least me :) ) can get ready for the day 5.0 will becomes -STABLE... My other problem is that I use vn's heavily and I find that some of their limitations are really annoying. While I could hack the relevent code to make myself happy, I think that there is little value in me doing that when it is obvious that they are going away in the not so distant future (5.0). Anyway, this is not a big deal. Patrick. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vn, vnconfig and MFS death-warrant!
Uh, self castigation. Sorry for inconvenience. At Tue, 30 Jan 2001 11:30:30 +0100, Poul-Henning Kamp [EMAIL PROTECTED] wrote: March 1st I will remove the functionality from mount_mfs and vnconfig, leaving only the message which will be an error obviously. April 1st I will remove vn, vnconfig and mount_mfs entirely. I think we should postpone the complete removing for a year till (on release of 5.2), to give people a migration sugar. == Otherwise System upgrading (4.x - 5.x) will cause confusing situation, ^ for example, living old 4.x vnconfig binary and together new and splendid mdconfig. ^ -- Motomichi Matsuzaki [EMAIL PROTECTED] Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vn, vnconfig and MFS death-warrant!
Just a note. phk March 1st I will remove the functionality from mount_mfs and phk vnconfig, leaving only the message which will be an error obviously. Before March 1st, src/release/Makefile, src/release/scripts/doFS.sh, src/release/texts/FLOPPIES.TXT, and some PicoBSD stuffs need some work to convert from vnconfig(8) to mdconfig(8). Is Anybody working on this? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
