Bug 163102
| Summary: | linprocfs mounted in wrong location in Handbook | ||
|---|---|---|---|
| Product: | Documentation | Reporter: | VoidChicken |
| Component: | Books & Articles | Assignee: | Manolis Kiagias <manolis> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
VoidChicken
2011-12-07 06:10:08 UTC
/compat is a symlink to usr/compat So, nothing is wrong here for me. -- wbr, pluknet On 7/12/2011 9:00 ðì, Sergey Kandaurov wrote: > The following reply was made to PR docs/163102; it has been noted by GNATS. > > From: Sergey Kandaurov<pluknet@gmail.com> > To: bug-followup@FreeBSD.org, VoidChicken@gmail.com > Cc: > Subject: Re: docs/163102: linprocfs mounted in wrong location in Handbook > Date: Wed, 7 Dec 2011 09:22:54 +0300 > > /compat is a symlink to usr/compat > So, nothing is wrong here for me. > > -- > wbr, > pluknet Same here, mounting works on both locations as expected since /compat is just a symlink as stated. Just tried on both 8.2-RELEASE and 9.0-RC2. Maybe this is specific to your installation? Could you please verify that /compat is really a symlink to /usr/compat in your install? On 12/07/2011 04:32, Manolis Kiagias wrote: > On 7/12/2011 9:00 ðì, Sergey Kandaurov wrote: >> The following reply was made to PR docs/163102; it has been noted by >> GNATS. >> >> From: Sergey Kandaurov<pluknet@gmail.com> >> To: bug-followup@FreeBSD.org, VoidChicken@gmail.com >> Cc: >> Subject: Re: docs/163102: linprocfs mounted in wrong location in >> Handbook >> Date: Wed, 7 Dec 2011 09:22:54 +0300 >> >> /compat is a symlink to usr/compat >> So, nothing is wrong here for me. >> >> -- >> wbr, >> pluknet > > Same here, mounting works on both locations as expected since /compat > is just a symlink as stated. Just tried on both 8.2-RELEASE and > 9.0-RC2. Maybe this is specific to your installation? Could you > please verify that /compat is really a symlink to /usr/compat in your > install? $ ls /usr/compat ls: /usr/compat: No such file or directory $ ls -ld /compat drwxr-xr-x 3 root wheel 3 Jan 17 2010 compat It isn't a symlink on my system. At what point in installation is it supposed to have been created? I don't see a mention of that anywhere in the Handbook. Chapter 11.2 even refers to /compat/linux instead of /usr/compat/linux. Le Wed, 7 Dec 2011 15:30:15 GMT, Kevin Baxter <voidchicken@gmail.com> a écrit : > $ ls /usr/compat > ls: /usr/compat: No such file or directory > $ ls -ld /compat > drwxr-xr-x 3 root wheel 3 Jan 17 2010 compat > > It isn't a symlink on my system. At what point in installation is it > supposed to have been created? I don't see a mention of that > anywhere in the Handbook. Chapter 11.2 even refers to /compat/linux > instead of /usr/compat/linux. On 9.0 bsdinstall does not create the /compat symlink. Or even /compat, it is created when you install the linux base. You have to move /compat to /usr/compat and create the link by hand. This is a bug in bsdinstall imho. Sysintall did it. I don't know if this is fixed (I've installed with a 9.0 beta usb key) Regards. On 7/12/2011 7:20 ìì, Patrick Lamaiziere wrote: > The following reply was made to PR docs/163102; it has been noted by GNATS. > > From: Patrick Lamaiziere<patfbsd@davenulle.org> > To: bug-followup@freebsd.org<bug-followup@freebsd.org> > Cc: Kevin Baxter<voidchicken@gmail.com> > Subject: Re: docs/163102: linprocfs mounted in wrong location in Handbook > Date: Wed, 7 Dec 2011 18:02:34 +0100 > > Le Wed, 7 Dec 2011 15:30:15 GMT, > Kevin Baxter<voidchicken@gmail.com> a écrit : > > > $ ls /usr/compat > > ls: /usr/compat: No such file or directory > > $ ls -ld /compat > > drwxr-xr-x 3 root wheel 3 Jan 17 2010 compat > > > > It isn't a symlink on my system. At what point in installation is it > > supposed to have been created? I don't see a mention of that > > anywhere in the Handbook. Chapter 11.2 even refers to /compat/linux > > instead of /usr/compat/linux. > > On 9.0 bsdinstall does not create the /compat symlink. Or > even /compat, it is created when you install the linux base. > You have to move /compat to /usr/compat and create the link by hand. I've checked on 9.0-RC2 and the link is there, but my installs were upgraded from 8.2-RELEASE, so you may have a point there. I'll check on a clean 9.0-RC3 install shortly and report findings. > > This is a bug in bsdinstall imho. Sysintall did it. I don't know if > this is fixed (I've installed with a 9.0 beta usb key) > > Regards. If it happens that 9.0 installs into /compat, we should either add this to the documentation or file a PR so that either the linux_base package or bsdinstall creates the link. But from the current PR it seems the OP was using 8.2-RELEASE which should not exhibit this. On 12/07/2011 10:26, Manolis Kiagias wrote: > On 7/12/2011 7:20 ìì, Patrick Lamaiziere wrote: >> The following reply was made to PR docs/163102; it has been noted by >> GNATS. >> >> From: Patrick Lamaiziere<patfbsd@davenulle.org> >> To: bug-followup@freebsd.org<bug-followup@freebsd.org> >> Cc: Kevin Baxter<voidchicken@gmail.com> >> Subject: Re: docs/163102: linprocfs mounted in wrong location in >> Handbook >> Date: Wed, 7 Dec 2011 18:02:34 +0100 >> >> Le Wed, 7 Dec 2011 15:30:15 GMT, >> Kevin Baxter<voidchicken@gmail.com> a écrit : >> >> > $ ls /usr/compat >> > ls: /usr/compat: No such file or directory >> > $ ls -ld /compat >> > drwxr-xr-x 3 root wheel 3 Jan 17 2010 compat >> > >> > It isn't a symlink on my system. At what point in installation is it >> > supposed to have been created? I don't see a mention of that >> > anywhere in the Handbook. Chapter 11.2 even refers to /compat/linux >> > instead of /usr/compat/linux. >> >> On 9.0 bsdinstall does not create the /compat symlink. Or >> even /compat, it is created when you install the linux base. >> You have to move /compat to /usr/compat and create the link by hand. > > I've checked on 9.0-RC2 and the link is there, but my installs were > upgraded from 8.2-RELEASE, so you may have a point there. I'll check > on a clean 9.0-RC3 install shortly and report findings. > >> >> This is a bug in bsdinstall imho. Sysintall did it. I don't know if >> this is fixed (I've installed with a 9.0 beta usb key) >> >> Regards. > > If it happens that 9.0 installs into /compat, we should either add > this to the documentation or file a PR so that either the linux_base > package or bsdinstall creates the link. > But from the current PR it seems the OP was using 8.2-RELEASE which > should not exhibit this. I'm using a ZFS root, so I used the wiki's RootOnZFS page to install (which doesn't use sysinstall, and doesn't mention /compat). So is this a case of a non-standard installation being unsupported? Should the wiki be changed to include that symlink? Or should one of the install scripts be changed to make the symlink? On 7/12/2011 8:38 ìì, Kevin Baxter wrote: > >> If it happens that 9.0 installs into /compat, we should either add >> this to the documentation or file a PR so that either the linux_base >> package or bsdinstall creates the link. >> But from the current PR it seems the OP was using 8.2-RELEASE which >> should not exhibit this. > > > I'm using a ZFS root, so I used the wiki's RootOnZFS page to install > (which doesn't use sysinstall, and doesn't mention /compat). > Ah, that explains it then. We could add this info to the wiki or just change the Handbook to /compat instead of /usr/compat since this will work in all cases anyway. I'm more inclined to do the latter (maybe with an additional note on custom installs). > So is this a case of a non-standard installation being unsupported? > Should the wiki be changed to include that symlink? Or should one of > the install scripts be changed to make the symlink? > As it happens, bsdinstall on 9.0-RC3 still won't make the link so /compat is again created as a directory rather than a symlink. The default installation now uses a single UFS partition for everything rather than the legacy slice with /tmp /usr/ /var etc. so the probability of installing something on / and going out of disk space is minimal (but not zero, as someone may still opt to use MBR partitions and linux_base needs about 140 Mb of space). A PR for bsdinstall(8) for this is probably a good idea. Responsible Changed From-To: freebsd-doc->manolis Over to me manolis 2011-12-07 21:32:06 UTC
FreeBSD doc repository
Modified files:
en_US.ISO8859-1/books/handbook/desktop chapter.sgml
en_US.ISO8859-1/books/handbook/linuxemu chapter.sgml
Log:
Use /compat/linux/proc instead of /usr/compat/linux/proc as the mount point of
linproc in the examples, since:
- linux_base always installs to /compat and creates it as a directory if it
does not exist as a symlink
- Custom installations (not done by sysinstall(8)) may not have /compat at all
- The linuxemu chapter uses /compat anyway (except a single example, fixed)
- The new bsdinstall(8) does not create /compat either as directory or symlink
PR: docs/163102
Submitted by: Kevin Baxter <VoidChicken at gmail dot com>
Revision Changes Path
1.119 +3 -3 doc/en_US.ISO8859-1/books/handbook/desktop/chapter.sgml
1.143 +1 -1 doc/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
State Changed From-To: open->closed Changes were committed and will appear on the website soon. Thanks for submitting this! |
