Re: Issuing "halt" locks up computer and working graphical browser (dillo)
Thanks for the input. I will try repartitioning and sudo once i get home
And good spotted with the iso9660 fs!
> Svante, thanks for answering -- you basically gave the same answers I
> would have given. :-) I only have a few additional recommendations and
> On Fri, 22 Jul 2011 11:22:15 +0200, Svante Signell
> <firstname.lastname@example.org> wrote:
>> On Fri, 2011-07-22 at 00:56 +0200, email@example.com wrote:
>> > I have never been able to make a clean shutdown with hurd. And the
>> > freezes on me every time.
> Given your original text, you're running X. The system will -- as far as
> I know -- not switch back to the text console/Mach console if reboot or
> halt are invoked. Thus, you won't see the shutdown/reboot messages.
> First stop X, then stop the Hurd console, then reboot/halt to see what's
>> > I wouldn't really care if i didn't risk
>> > destroying my filesystem in the process. As you know it takes a while
>> > set everything up and once i have got it running i would like to be
>> > to keep it so for at least a couple of months.
> It is also advisable to have a separate partition for $HOME/ etc.
> Can we have the Debian Install do this automatically? (I always do
> partitioning manually, so I don't know if it's already doing that.)
> Apparently, I forgot to take notes after my last installation, whether I
> manually had to setup the translator and /etc/fstab entries for the
> second ext2fs instance.
> And do backups, of course. Which is especially easy if you're using QEMU
> (or similar), as you can just copy the whole disk image (when the system
> is not running).
>> Are you using qemu/kvm or real hardware? For hopefully a good shutdown,
>> use syncfs --synchronous /, before shutting down with halt (not
>> shutdown), see
>> > Regarding cd reading errors i have had them too even though the
>> > on my disc is okey. I used it to install on qemu and didn't come
>> > the same errors. I solved the problems by using the online installer.
> No idea on that.
>> > Finally, is the ext2fs program eating all your cpu as well or is it
>> > on my system?
> ext2fs is known to be a resource hog. Separating the root filesystem
> with /usr etc. from /home does help, in my opinion; also for system
>> > I hope it doesn't sound like i'm complaining. I have got fvwm2 running
>> > i'm as happy as ever! Yes its slower than running linux. But twice the
>> > fun!
>> > Oh, yes, forgot to mention that sudo just locks the console when i try
>> > issue commands through it. It asks for my password and after it is
>> > accepted nothing happens. Just thought you should know.
> Is it really that it doesn't do anything, or is it rather that it
> stops/hangs *after* doing its task?
>> Currently sudo locks up after command completion. According to Samuel
>> Thibault this is due to: the sudo bug is select() not being able to get
>> interrupted by signals, see
>> For the moment su - is recommended (or log in as root)
> Or, what I do, use ``sudo -i'' in a shell, and leave it running.