cvs commit: doc/en_US.ISO8859-1/books/handbook/desktop chapter.sgml doc/en_US.ISO8859-1/books/handbook/linuxemu chapter.sgml

[Nathan Whitehorn]

On 12/11/11 08:24, Alexander Leidinger wrote:
> On Sat, 10 Dec 2011 15:29:38 -0600 Nathan Whitehorn
> <nwhitehorn at freebsd.org>  wrote:
>
>> On 12/10/11 15:06, Manolis Kiagias wrote:
>>> 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.
>> This is very easy to do, and the correct place is in
>> /usr/src/usr.sbin/bsdinstall/scripts/config. I don't have a good
>> sense of what the correct logic is, however, and so would appreciate
>> either guidance or patches from emulation-types.
> mkdir /usr/compat
> ln -s /usr/compat /compat
>
> To be checked (maybe): can or are parts of this already handled in mtree
> files?
>   - Is /usr/compat already in a mtree file and if not why not?
>   - Can the link be handled in a mtree file and if yes, should it be
>     added there instead?
>

/usr/compat is not currently part of anything. There's also the problem 
that the user may not actually want it on /usr (e.g. if /usr is 
read-only or small). I think that for the purposes of 9.0, your 
suggested patch will do the job, but longer-term, moving them to 
LOCALBASE seems better. But that's my two cents.
-Nathan