Re: /dev nullfs and schroot

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 06/06/2012 22:10, xavier grave a écrit : > Le 06/06/2012 22:06, Steven Chamberlain a écrit : >> On 06/06/12 20:57, xavier grave wrote: >>> Do you know how if this can be "ported" to my schroot problem ? > >> I haven't tried it myself, but here's so

Re: /dev nullfs and schroot

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 06/06/2012 22:06, Steven Chamberlain a écrit : > On 06/06/12 20:57, xavier grave wrote: >> Do you know how if this can be "ported" to my schroot problem ? > > I haven't tried it myself, but here's someone else's > /etc/schroot/default/fstab config

Re: /dev nullfs and schroot

On 06/06/12 20:57, xavier grave wrote: > Do you know how if this can be "ported" to my schroot problem ? I haven't tried it myself, but here's someone else's /etc/schroot/default/fstab config file for kfreebsd-*: # proc/proc linprocfs defaults 0 0

Re: /dev nullfs and schroot

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 06/06/2012 16:43, Steven Chamberlain a écrit : > Hi Xavier, > > I have this in my pbuilderrc, probably what you are looking for: > >> USEDEVPTS=no >> USEDEVFS=yes Thanks a lot, it did the trick ! Do you know how if this can be "ported" to my sch

Re: /dev nullfs and schroot

Hi Xavier, I have this in my pbuilderrc, probably what you are looking for: > USEDEVPTS=no > USEDEVFS=yes Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debia

/dev nullfs and schroot

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, In a chrooted environment, I have mounted a nullfs from /dev/ to /debian/unstable/dev But I can't use the /debian/unstable/dev/null special file, I get a : No such device or address I'm quite sure this should be a known issue, but I can't find t

Re: OpenJDK-7 on kFreeBSD (feedback)

Hi, On 16/05/12 06:18, Christoph Egger wrote: > Changing kernels did not fix this problem in any way. What did make > openjdk-7 compile was switching from stable's sbuild/schroot to > wheezy's. Would doing this have updated any of the build-essential packages, particularly binutils, eglibc? > L

Re: q4wine: Errors of linking during package building

Hi, >>>   And it is present: >>>   Linking CXX executable q4wine-helper >>>   /usr/bin/c++  ... -lkvm ../q4wine-lib/libq4wine-core.so ... >>>   .. >>> >>>   Any other ideas? >>> >>  Yes, change to >> >>  /usr/bin/c++ ...  ../q4wine-lib/libq4wine-core.so -lkvm ... >> >>  Especially with --as-needed