[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Installing Debian GNU/Hurd in qemu/kvm using the Debian Installer (f

From: Samuel Thibault
Subject: Re: Installing Debian GNU/Hurd in qemu/kvm using the Debian Installer (first draft)
Date: Tue, 29 Mar 2011 23:50:59 +0200
User-agent: Mutt/1.5.12-2006-07-14

olafBuddenhagen@gmx.net, le Tue 29 Mar 2011 18:17:34 +0200, a écrit :
> Does KVM really use different images than plain QEMU?


> Or is it the same utility, but uses a different name depending on
> which package you installed?...


> > deb http://ftp.debian-ports.org/debian unstable main
> That should be "unreleased".


> BTW, doesn't the installer set this up correctly?...

Nope, it's not easy to make it fit the standard way which is simply to
use the mirror used at installation, which is jkoenig's mirror because
d-i doesn't support mutiple mirrors.

> > A few words about the Mach console:
> > ===================================
> > This console is very primitive and does not have any scrolling facilities.
> > Use the mach console only for basic work.
> Note that the Hurd console also has a number of drawbacks. (One of which
> you actually mention later on: not seeing kernel messages. But there are
> other issues too.) So the preference is not at all clear. There is a
> reason why it's not enabled by default...

I'm not really sure such reason make it not a sane default for lambda

> > 2) Hurd console after boot: Log in to the Mach console and run the
> > executable script: hurd-console
> > 
> > a) As user: sudo ./hurd-console (add yourself to the sudoers with visudo)
> > b) As root ./hurd-console
> > 
> > hurd.-console:
> > console -d vga -d pc_mouse --repeat=mouse -d pc_kbd --repeat=kbd -d 
> > generic_speaker -c /dev/vcs
> I don't see much point in creating a script for this -- once used, the
> command can be easily fetched from shell history...

And we should actually rather simply provide a /etc/init.d/hurd-console
script, which can thus be started (or not) the usual way.

> > Create .xinitrc:
> > xrandr -s 1024x768 &
> Can't that be specified in xorg.conf instead?

Yes. It's not the simplest way, though.

> > As user: sudo startx
> > As root: startx (not recommended)
> Why root? It works fine as normal user here... It's generally not
> recommended to run a whole X session as root.

Maybe the default parameter of the Xorg wrapper is to accept only
console-logged in users (which doesn't work yet on the Hurd).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]