Re: VN bug or pilot error ?
On 22-Jan-01 Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], John Hay write s: But while you're at it, migrate to md(4) instead of vn(4), it does vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices So why not change the release process to use md instead of vn, so that we can make sure it works before vn is axed? I will do, as soon as I have time... If you work up a patch, I can test it in about 4-6 hours time.. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VN bug or pilot error ?
Poul-Henning Kamp [EMAIL PROTECTED] types: But while you're at it, migrate to md(4) instead of vn(4), it does vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices How close is the md rewrite to being able to replace mfs? Thanxm mike Poul-Henning In message [EMAIL PROTECTED], Thierry Herbelot writes: thanks a lot : that was it ! Peter Jeremy wrote: On 2001-Jan-21 10:15:22 +0100, Thierry Herbelot [EMAIL PROTECTED] wrote: I've got a recent current (cvsuped and rebuilt yesterday) on a laptop and I can't use the vn(4) pseudo-driver : I've compiled it in the kernel and I've also tried to kldload vn.ko, but I get consistently "vn0c : device not configured" when I try to use it to mount a locally stored iso image. Change "vn0c" to "vn0". I believe this is the result of PHK's change in mid-December which added cloning to vn. Peter -- Thierry Herbelot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- 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 -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VN bug or pilot error ?
In message [EMAIL PROTECTED], Mike Meyer writes: Poul-Henning Kamp [EMAIL PROTECTED] types: But while you're at it, migrate to md(4) instead of vn(4), it does vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices How close is the md rewrite to being able to replace mfs? Well, it can, but it is still not obviously better than mfs. see mdconfig(8) A real vmfs or tmpfs is more complicated. -- 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
VN bug or pilot error ?
Hello, I've got a recent current (cvsuped and rebuilt yesterday) on a laptop and I can't use the vn(4) pseudo-driver : I've compiled it in the kernel and I've also tried to kldload vn.ko, but I get consistently "vn0c : device not configured" when I try to use it to mount a locally stored iso image. I've switched to Stable and I can mount the exact same image. TfH PS : it seems it's possible to vn-mount a file located on an NFS server, when the man page says it is not possible (which is right ?) -- Thierry Herbelot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VN bug or pilot error ?
On 2001-Jan-21 10:15:22 +0100, Thierry Herbelot [EMAIL PROTECTED] wrote: I've got a recent current (cvsuped and rebuilt yesterday) on a laptop and I can't use the vn(4) pseudo-driver : I've compiled it in the kernel and I've also tried to kldload vn.ko, but I get consistently "vn0c : device not configured" when I try to use it to mount a locally stored iso image. Change "vn0c" to "vn0". I believe this is the result of PHK's change in mid-December which added cloning to vn. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VN bug or pilot error ?
thanks a lot : that was it ! Peter Jeremy wrote: On 2001-Jan-21 10:15:22 +0100, Thierry Herbelot [EMAIL PROTECTED] wrote: I've got a recent current (cvsuped and rebuilt yesterday) on a laptop and I can't use the vn(4) pseudo-driver : I've compiled it in the kernel and I've also tried to kldload vn.ko, but I get consistently "vn0c : device not configured" when I try to use it to mount a locally stored iso image. Change "vn0c" to "vn0". I believe this is the result of PHK's change in mid-December which added cloning to vn. Peter -- Thierry Herbelot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VN bug or pilot error ?
But while you're at it, migrate to md(4) instead of vn(4), it does vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices Poul-Henning In message [EMAIL PROTECTED], Thierry Herbelot writes: thanks a lot : that was it ! Peter Jeremy wrote: On 2001-Jan-21 10:15:22 +0100, Thierry Herbelot [EMAIL PROTECTED] wrote: I've got a recent current (cvsuped and rebuilt yesterday) on a laptop and I can't use the vn(4) pseudo-driver : I've compiled it in the kernel and I've also tried to kldload vn.ko, but I get consistently "vn0c : device not configured" when I try to use it to mount a locally stored iso image. Change "vn0c" to "vn0". I believe this is the result of PHK's change in mid-December which added cloning to vn. Peter -- Thierry Herbelot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- 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 bug or pilot error ?
Poul-Henning Kamp wrote: But while you're at it, migrate to md(4) instead of vn(4), it does vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices If I may, two more questions : - the 4.2 man page for vn says the file must be stored locally (I have tried vn-mounting a NFS file and it worked : certainly the man page could be corrected - or I was lucky ?) - under 4.2-Release, I have trouble using a larger than 20 Megs MD partition (I have increased MDNsect to 8, but I still can't store more the 20 Megs : a "cp" with a 35 Megs file stays blocked, and always at the same place - I will give more details) TfH Poul-Henning In message [EMAIL PROTECTED], Thierry Herbelot writes: thanks a lot : that was it ! -- 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. -- Thierry Herbelot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VN bug or pilot error ?
In message [EMAIL PROTECTED], Thierry Herbelot writes: Poul-Henning Kamp wrote: But while you're at it, migrate to md(4) instead of vn(4), it does vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices If I may, two more questions : Sorry, my misundertstanding, seing that you emailed to current@ I pressumed we were talking about -current here. The new md(4)/mdconfig(8) is only in -current and will not make it into -stable any time soon if at all. Poul-Henning - the 4.2 man page for vn says the file must be stored locally (I have tried vn-mounting a NFS file and it worked : certainly the man page could be corrected - or I was lucky ?) - under 4.2-Release, I have trouble using a larger than 20 Megs MD partition (I have increased MDNsect to 8, but I still can't store more the 20 Megs : a "cp" with a 35 Megs file stays blocked, and always at the same place - I will give more details) TfH Poul-Henning In message [EMAIL PROTECTED], Thierry Herbelot writes: thanks a lot : that was it ! -- 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. -- Thierry Herbelot -- 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 bug or pilot error ?
But while you're at it, migrate to md(4) instead of vn(4), it does vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices So why not change the release process to use md instead of vn, so that we can make sure it works before vn is axed? John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: VN bug or pilot error ?
In message [EMAIL PROTECTED], John Hay write s: But while you're at it, migrate to md(4) instead of vn(4), it does vn(4) will be deprecated RSN. mdconfig(8) configures the md(4) devices So why not change the release process to use md instead of vn, so that we can make sure it works before vn is axed? I will do, as soon as I have time... -- 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
