From 31733b3eec44aafa94202eab8cc0e322e7827e98 Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Wed, 6 Jul 2016 23:46:36 +0200 Subject: Add more tricks for chroots --- hurd/running/chroot.mdwn | 2 ++ 1 file changed, 2 insertions(+) (limited to 'hurd/running') diff --git a/hurd/running/chroot.mdwn b/hurd/running/chroot.mdwn index 699f05a1..4bda626f 100644 --- a/hurd/running/chroot.mdwn +++ b/hurd/running/chroot.mdwn @@ -45,3 +45,5 @@ programs inside the chroot need to be able to access them: # settrans chroot/tmp /hurd/firmlink /tmp # settrans -c chroot/var/lib/dbus /hurd/firmlink /var/lib/dbus # settrans -c chroot/run/dbus /hurd/firmlink /run/dbus + # settrans -kp chroot/proc /hurd/firmlink /proc + # settrans -c $CHROOT/$HOME/.dbus /hurd/firmlink /$HOME/.dbus -- cgit v1.2.3 From 32e9a8ab6b914f7ca88e150178823f6799ab3b72 Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Sun, 28 Aug 2016 22:08:26 +0200 Subject: Complete commit 1f6eff (Drop -no-kvm-irqchip) we don't have the issue without it any more, and it actually seems to pose other problems --- hurd/running/qemu.mdwn | 16 +--------------- open_issues/libpthread.mdwn | 2 +- 2 files changed, 2 insertions(+), 16 deletions(-) (limited to 'hurd/running') diff --git a/hurd/running/qemu.mdwn b/hurd/running/qemu.mdwn index ef89ec12..369ceab6 100644 --- a/hurd/running/qemu.mdwn +++ b/hurd/running/qemu.mdwn @@ -95,21 +95,7 @@ Check that the kvm module is loaded: More info on kvm at: http://www.linux-kvm.org/page/FAQ -If your machine supports hardware acceleration, you should really use the kvm variant of qemu, as it speeds things quite a lot. Note however that kvm tends to make assumptions when accelerating things in the linux kernel, you may need some -no-kvm-something option. At the moment in Debian you need to pass - - -no-kvm-irqchip - -to the command line, see below, if you are running Linux kernels 2.6.37 or 2.6.38 else IRQs may hang sooner or later. The kvm irq problems will be solved in kernel 2.6.39. - -IRC, freenode, #hurd, 2012-08-29: - - youpi: do you remember which linux versions require the - -no-kvm-irqchip option ? - your page indicates 2.6.37-38, but i'm seeing weird things on - 2.6.32 - looks like a good thing to use that option all the time actually - seems like kvm -h says: -no-kvm-irqchip and man kvm says: - -machine kernel_irqchip=off +If your machine supports hardware acceleration, you should really use the kvm variant of qemu, as it speeds things quite a lot. # HAP/EPT/NPT acceleration diff --git a/open_issues/libpthread.mdwn b/open_issues/libpthread.mdwn index 0294b008..274e7e32 100644 --- a/open_issues/libpthread.mdwn +++ b/open_issues/libpthread.mdwn @@ -1061,7 +1061,7 @@ Most of the issues raised on this page has been resolved, a few remain. kvm -m 1024 -net nic,model=rtl8139 -net user,hostfwd=tcp::5562-:22 -drive cache=writeback,index=0,media=disk,file=hurd-experimental.img -vnc :6 - -cdrom isos/netinst_2012-07-15.iso -no-kvm-irqchip + -cdrom isos/netinst_2012-07-15.iso what is the file system type where your disk image is stored ? ext3 and how much physical memory on the host ? -- cgit v1.2.3 From 4ca8da2cf6b6048351ef44cda9a098d5c29a5b25 Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Sun, 4 Sep 2016 18:09:15 +0200 Subject: more details about buildds --- hurd/running/chroot.mdwn | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) (limited to 'hurd/running') diff --git a/hurd/running/chroot.mdwn b/hurd/running/chroot.mdwn index 4bda626f..ddba6217 100644 --- a/hurd/running/chroot.mdwn +++ b/hurd/running/chroot.mdwn @@ -40,10 +40,18 @@ socket creation will actually happen in the root filesystem. To make things work correctly the programs inside the chroot need to be able to access them: - # settrans -kp chroot/servers /hurd/firmlink /servers - # settrans -kp chroot/dev /hurd/firmlink /dev - # settrans chroot/tmp /hurd/firmlink /tmp - # settrans -c chroot/var/lib/dbus /hurd/firmlink /var/lib/dbus - # settrans -c chroot/run/dbus /hurd/firmlink /run/dbus - # settrans -kp chroot/proc /hurd/firmlink /proc + # CHROOT=$PWD/chroot + # settrans -kp $CHROOT/servers /hurd/firmlink /servers + # settrans -kp $CHROOT/dev /hurd/firmlink /dev + # settrans $CHROOT/tmp /hurd/firmlink /tmp + # settrans -c $CHROOT/var/lib/dbus /hurd/firmlink /var/lib/dbus + # settrans -c $CHROOT/run/dbus /hurd/firmlink /run/dbus + # settrans -kp $CHROOT/proc /hurd/firmlink /proc # settrans -c $CHROOT/$HOME/.dbus /hurd/firmlink /$HOME/.dbus + +# Buildds + +Debian build daemons use a specialized script instead of debootstrap: + + # mkdir ~/chroots + # /usr/share/sbuild/create-chroot sid -- cgit v1.2.3 From ae50505561cd9b00b7ef1d61c47cb9eb0c52c480 Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Sun, 4 Sep 2016 18:10:21 +0200 Subject: more details about buildds --- hurd/running/chroot.mdwn | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'hurd/running') diff --git a/hurd/running/chroot.mdwn b/hurd/running/chroot.mdwn index ddba6217..c5022c0a 100644 --- a/hurd/running/chroot.mdwn +++ b/hurd/running/chroot.mdwn @@ -55,3 +55,7 @@ Debian build daemons use a specialized script instead of debootstrap: # mkdir ~/chroots # /usr/share/sbuild/create-chroot sid + +They also use sbuild to start the build: + + # sbuild foo_1.2.3-1 -- cgit v1.2.3 From 836271112c114d53c724e988a6b6526fac6ab2ae Mon Sep 17 00:00:00 2001 From: Samuel Thibault Date: Sat, 17 Sep 2016 20:47:28 +0200 Subject: Use symbolic name --- hurd/running/chroot.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'hurd/running') diff --git a/hurd/running/chroot.mdwn b/hurd/running/chroot.mdwn index c5022c0a..66ecc24c 100644 --- a/hurd/running/chroot.mdwn +++ b/hurd/running/chroot.mdwn @@ -54,7 +54,7 @@ programs inside the chroot need to be able to access them: Debian build daemons use a specialized script instead of debootstrap: # mkdir ~/chroots - # /usr/share/sbuild/create-chroot sid + # /usr/share/sbuild/create-chroot unstable They also use sbuild to start the build: -- cgit v1.2.3