summaryrefslogtreecommitdiff
path: root/hurd/running
diff options
context:
space:
mode:
Diffstat (limited to 'hurd/running')
-rw-r--r--hurd/running/chroot.mdwn54
-rw-r--r--hurd/running/debian/after_install.mdwn72
-rw-r--r--hurd/running/debian/dhcp.mdwn12
-rw-r--r--hurd/running/qemu.mdwn10
4 files changed, 72 insertions, 76 deletions
diff --git a/hurd/running/chroot.mdwn b/hurd/running/chroot.mdwn
new file mode 100644
index 00000000..29b00a8f
--- /dev/null
+++ b/hurd/running/chroot.mdwn
@@ -0,0 +1,54 @@
+[[!meta copyright="Copyright © 2012 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
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
+
+This documents the currently-needed tricks to successfully build a
+[[glibc/chroot]] in GNU/Hurd.
+
+# Preparation
+
+For proper translator startup, the chroot storage needs to be handled by a
+separate translator, for instance:
+
+ # dd [...] < /dev/zero > storage
+ # mke2fs storage
+ # settrans -c chroot /hurd/ext2fs $PWD/storage
+
+# Unpack
+
+Debootstrap should be able to build the content:
+
+ # debootstrap sid chroot
+
+# Tricks
+
+One current issue to know about chroots is that since passive translators (e.g.
+`/servers/socket/1`) are started by the root translator, which is not aware
+of the chrooting, these passive translators are started non-chrooted, leading to
+a few issues.
+[[!tag open_issue_hurd]]
+
+## Sockets
+
+Since the passive [[translator/pflocal]] translator will not be chrooted, local
+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 chroot/servers/socket/1 /hurd/firmlink /servers/socket/1
+ # settrans chroot/tmp /hurd/firmlink /tmp
+ # settrans -c chroot/var/lib/dbus /hurd/firmlink /var/lib/dbus
+
+## Network
+
+Unless using a separate IP for the chroot, it is preferrable to share the
+[[translator/pfinet]] translator:
+
+ # settrans chroot/servers/socket/2 /hurd/firmlink /servers/socket/2
+ # settrans chroot/servers/socket/26 /hurd/firmlink /servers/socket/26
diff --git a/hurd/running/debian/after_install.mdwn b/hurd/running/debian/after_install.mdwn
index 36c37281..72ea70a9 100644
--- a/hurd/running/debian/after_install.mdwn
+++ b/hurd/running/debian/after_install.mdwn
@@ -1,35 +1,7 @@
First steps after installation.
-So you have managed to get past the first `native-install` runs in single-user
-mode?
-
-Time to get to work.
-
-[[!toc]]
-
-
-### Get Networking Running
-
-[[Network]].
-
-Check if your NIC was detected by GNU Mach:
-
- # devprobe eth0
-
-`devprobe` (run as user *root*) will print `eth0` on successful detection. If
-it doesn't, your NIC was not detected correctly. You can then try to do the
-following (also as user *root*) for getting details:
-
- # cat /dev/klog > ~/klog
- [Wait a second, then press `Ctrl-C'.]
-
-Now examine the `~/klog` file.
-
-If the NIC was detected:
-
- # settrans -fgap /servers/socket/2 /hurd/pfinet -i eth0 -a 192.168.1.3 -g 192.168.1.1 -m 255.255.255.0
-
-Or read about how to configure [[DHCP]].
+See <http://www.debian.org/ports/hurd/hurd-install> for configuration bits and
+tips and tricks.
# Setup GRUB
@@ -41,45 +13,5 @@ you. See [[GRUB]]'s page for this.
# Setup `apt-get`
-Sometimes getting `apt-get` to work is not straightforward. Good mirrors to
-put in `/etc/apt/sources.list` are:
-
- deb http://ftp.debian.org/debian unstable main contrib
- deb-src http://ftp.debian.org/debian unstable main contrib
- deb http://ftp.debian-ports.org/debian unreleased main
- deb-src http://ftp.debian-ports.org/debian unreleased main
-
-`apt-get` update a couple of times if some file fails to download.
-
-If when doing your first `apt-get`, `dpkg` complains of missing programs, get root in a login shell (`su -`).
-
Installing packages without having a network connection is described
[[Distrib/DebianAptOffline]].
-
-# [[translator/Random]]
-
-You often need `scp` and `ssh`. There is now a `random-egd` package available which uses
-a random translator by Ryan Hunter and the entropy gathering daemon as entropy source.
-
-See [[Translator/random]] for more information.
-
-# [[Console]]
-
-The latest Hurd package in Debian, plus the `native-install` script, creates
-all necessary device nodes and other magic. You just need to edit
-`/etc/default/hurd-console` to tune the parameters and tell it to start at
-bootup.
-
-You can also call the Hurd console manually with the proper arguments:
-
- console -d vga -d pc_kbd --repeat=kbd -d pc_mouse --repeat=mouse \
- -d generic_speaker -c /dev/vcs
-
-
-# [[Hurd/DebianXorg]]
-
-You first must have setup the virtual console. See above.
-
-# What about package XYZ?
-
-See if you can find a useful tip in [[package_troubleshooting]].
diff --git a/hurd/running/debian/dhcp.mdwn b/hurd/running/debian/dhcp.mdwn
index 8d351aae..afa46799 100644
--- a/hurd/running/debian/dhcp.mdwn
+++ b/hurd/running/debian/dhcp.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2011, 2012 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
@@ -10,16 +10,16 @@ License|/fdl]]."]]"""]]
[[!tag open_issue_porting]]
-In order to use DHCP, you need to install the `ifup` and `isc-dhcp-client`
-packages, and manually create the following two symbolic links:
+In order to use DHCP, you need to install the `ifupdown` and `isc-dhcp-client`
+packages, and manually create the following symbolic link:
- # ln -s ../rcS.d/S06ifupdown-clean ../rcS.d/S11networking /etc/rc.boot/
+ # ln -s ../rcS.d/S10networking /etc/rc.boot/
-During execution at boot time, the `S11networking` script will emit some error
+During execution at boot time, the `S10networking` script will emit some error
messages while trying to configure the loopback interface. These are not
fatal.
-Debian GNU/Hurd doesn't currently execute's Debian standard `/etc/rcS.d/*` boot
+Debian GNU/Hurd doesn't currently execute Debian standard `/etc/rcS.d/*` boot
scripts, but has its own `/libexec/rc` script -- which integrates scripts from
`/etc/rc.boot/` instead.
diff --git a/hurd/running/qemu.mdwn b/hurd/running/qemu.mdwn
index 512ea602..3648c7d6 100644
--- a/hurd/running/qemu.mdwn
+++ b/hurd/running/qemu.mdwn
@@ -105,6 +105,16 @@ If your machine supports hardware acceleration, you should really use the kvm va
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
+
/!\ Note that there are known performance issues with KVM on Linux 2.6.39
kernels, compared to 2.6.32: [[!debbug 634149]]. We're preparing on a change
on our side to work around this.