cvs commit: doc/en_US.ISO8859-1/books/handbook/desktop
chapter.sgml
doc/en_US.ISO8859-1/books/handbook/linuxemu chapter.sgml
Manolis Kiagias
manolis at FreeBSD.org
Sat Dec 10 21:25:00 UTC 2011
On 10/12/2011 10:40 μμ, Alexander Leidinger wrote:
> On Wed, 7 Dec 2011 21:32:06 +0000 (UTC) Manolis Kiagias
> <manolis at FreeBSD.org> wrote:
>
> CCing re@, emulation@ and nwhitehorn@ due to a possible impact in the
> upcomming release.
>
>> 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
> Looks like a bug in bsdinstall (and linux_base) to me. What you write
> here means that a new release with bsdinstall instead of sysinstall may
> cause problems where /compat is in a small partition and /usr in a big
> partition (even if it creates a big one by default, an user may change
> this). I suggest to fix bsdinstall before the release of 9.0. It also
> changes what is expected by long-term users.
Yes, this was discussed in the PR (see
http://lists.freebsd.org/pipermail/freebsd-doc/2011-December/019270.html
). I think the best and safer way would be for bsdinstall to create the
link if possible.
More information about the cvs-doc
mailing list