Some kind of unionfs seems to be required for our compat stuff.
Forgive me if I dont know what I'm talking about but isn't it true
that a unionfs would just override those files in /usr that existed
in the Linux emulation space ?
I suppose there would be problems when Linux binaries would 'see'
Tom Embt wrote:
> Now another question: Have you been able to get to /usr? When I try to
> bring it up I get /compat/linux/usr instead. At least /home works.. :)
I guess, thats the way our linux mode works. If the application asks
for a special directory, it's prefixed with /usr/compat (or ev
At 09:51 AM 9/11/99 +1200, you wrote:
>YOU DA MAN.. that works fine on -current also
I'll second that, THANK YOU for this silly but effective solution!
>"Gray, David W." wrote:
>
>> MOVE YOUR /usr/compat DIRECTORY aside - rename it temporarily. Run compupic
>> once. You should now be able
>> to
YOU DA MAN.. that works fine on -current also
"Gray, David W." wrote:
> MOVE YOUR /usr/compat DIRECTORY aside - rename it temporarily. Run compupic
> once. You should now be able
> to move /usr/compat back into place (or /compat, if you left it there...)
> Why? I dunno. Found it by accident.
T
A quick preface, I am using Release3.2 off the CDROM.
Compupic works. I don't use the install script, just unpack everything from
the innermost tar
file to /usr/local/compupic. Brandelf -t Linux the compupic binary, and put
a symlink in /usr/local/bin
to run with. Now for the SEKIT!
MOVE YOUR /
