Thomas Stromberg wrote: > > It's probably been fixed by now, but what I did when I first had the > mtree > problem was set NO_MTREE in /usr/ports/Mk/bsd.port.mk - Not sure of the > side > affects though (anyone care to enligtnen me?) > > Im sure there is a more elegant solution, I was just looking for a > quicky. > It is not fixed. Th current version of /usr/ports/Mk/bsd.ports.mk still has an OS version test to determine whether to use the -L flag -- committed by Satoshi Asami after the initial "no -L, now -L" move. The move was later backed out, but not this change. The whole issue of mtree behaviour has been discussed ad nauseam on cvs-all. Up until a concensus is reached, it's most probably easier to locally override MTREE_ARGS. Regards, PYD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Panic: lockmgr: pid 5, not exclusive lock holder... Ollivier Robert
- Re: Panic: lockmgr: pid 5, not exclusive lo... Jun Kuriyama
- Re: Panic: lockmgr: pid 5, not exclusiv... Stephan van Beerschoten
- Re: mtree -L problems in ports Thomas Stromberg
- Re: Panic: lockmgr: pid 5, not ... Dampure, Pierre Y.
- Re: Panic: lockmgr: pid 5, not exclusive lo... Brian Fundakowski Feldman
- Re: Panic: lockmgr: pid 5, not exclusive lo... Brian Fundakowski Feldman
- Re: Panic: lockmgr: pid 5, not exclusiv... Ollivier Robert
- Re: Panic: lockmgr: pid 5, not excl... Brian Fundakowski Feldman
- Re: Panic: bqrelse: multiple re... Kirk McKusick
- Re: Panic: lockmgr: pid 5, not exclusiv... Stephan van Beerschoten
- Re: Panic: lockmgr: pid 5, not excl... Ollivier Robert
- Re: Panic: lockmgr: pid 5, not excl... Dampure, Pierre Y.
- Re: Panic: lockmgr: pid 5, not ... Mike Smith
- Re: Panic: lockmgr: pid 5,... Wilko Bulte