diff options
Diffstat (limited to 'hurd/running')
| -rw-r--r-- | hurd/running/chroot.mdwn | 27 | ||||
| -rw-r--r-- | hurd/running/qemu.mdwn | 16 |
2 files changed, 22 insertions, 21 deletions
diff --git a/hurd/running/chroot.mdwn b/hurd/running/chroot.mdwn index 699f05a1..eac67282 100644 --- a/hurd/running/chroot.mdwn +++ b/hurd/running/chroot.mdwn @@ -1,4 +1,5 @@ -[[!meta copyright="Copyright © 2012, 2013 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2012, 2013, 2016 Free Software Foundation, +Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -40,8 +41,22 @@ 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 + # 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 unstable + +They also use sbuild to start the build: + + # sbuild foo_1.2.3-1 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: - - <braunr> youpi: do you remember which linux versions require the - -no-kvm-irqchip option ? - <braunr> your page indicates 2.6.37-38, but i'm seeing weird things on - 2.6.32 - <braunr> looks like a good thing to use that option all the time actually - <gnu_srs> 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 |