Bug#737759: marked as done (hurd: Add init.d script to create /var/run/mtab)

2017-06-26 Thread Debian Bug Tracking System
Your message dated Tue, 27 Jun 2017 06:18:45 +0200
with message-id <2flefu69i6y@diskless.uio.no>
and subject line Re: Bug#737759: hurd: Add init.d script to create /var/run/mtab
has caused the Debian Bug report #737759,
regarding hurd: Add init.d script to create /var/run/mtab
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
737759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: hurd
Version: 1:0.5.git20140203-1
Severity: important
Tags: patch

At the moment in unstable when booting Hurd using sysvinit, df and
friends do not work because /var/run/mtab do not exist.  It should point
to /proc/mounts, and this is done in /etc/hurd/rc when not booting using
sysvinit.

Instead of creating the symlink in /etc/hurd/rc, I suggest to create a
new init.d script to create this symlink, and drop the code from
/etc/hurd/rc.  The following script is tested and found to be working
well.  It creates /run/mtab because /var/run is a symlink to /run.

#! /bin/sh
### BEGIN INIT INFO
# Provides:  hurd-mtab
# Required-Start:mountkernfs
# Required-Stop:
# Default-Start: S
# Default-Stop:
# Short-Description: Create /run/mtab -> /proc/mount symlink on Hurd
### END INIT INFO

# Author: Petter Reinholdtsen

# PATH should only include /usr/* if it runs after the mountnfs.sh script
PATH=/sbin:/bin

# Load the VERBOSE setting and other rcS variables
. /lib/init/vars.sh

# Define LSB log_* functions.
# Depend on lsb-base (>= 3.2-14) to ensure that this file is present
# and status_of_proc is working.
. /lib/lsb/init-functions

case "$1" in
  start)
[ "$VERBOSE" != no ] && log_action_begin_msg "Creating /run/mtab 
symlink"
ln -s /proc/mount /run/mtab
case "$?" in
0|1) [ "$VERBOSE" != no ] && log_action_end_msg 0 ;;
2) [ "$VERBOSE" != no ] && log_action_end_msg 1 ;;
esac
;;
  stop|restart|force-reload|status)
;;
  *)
echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
exit 3
;;
esac

:

-- 
Happy hacking
Petter Reinholdtsen
--- End Message ---
--- Begin Message ---

[Samuel Thibault]
> AIUI, now that we have /etc/mtab as a symlink to /proc/mounts, tools
> are happy already.

Right.  Then I close this issue to get it out of my list of open issues
to track.

-- 
Happy hacking
Petter Reinholdtsen--- End Message ---


Re: Ideal Hardware for Hurd ?

2017-06-26 Thread Patrick

On 06/26/2017 07:33 PM, Samuel Thibault wrote:

Patrick, on dim. 25 juin 2017 11:56:12 -0400, wrote:

As a side note, does anyone think that Hurd might be stable and production
ready in 1-2 years?

There's very little probability that what you call "stable and
production ready" (even if I'm really unsure what level you are meaning
here) will be achieved in 1-2 years. Unless much more energy is poured
into it than there is currently.

Samuel


Hi Samuel

Thanks for answering my posts. It's okay if it will not be ready for 
really critical work anytime soon, I very much appreciate the hard work 
that has and is going into it. Hopefully I can pour energy into it 
someday soon but I will have to catch up for a year or so.


Merci-Patrick



Re: Ideal Hardware for Hurd ?

2017-06-26 Thread Samuel Thibault
Patrick, on dim. 25 juin 2017 11:56:12 -0400, wrote:
> As a side note, does anyone think that Hurd might be stable and production
> ready in 1-2 years?

There's very little probability that what you call "stable and
production ready" (even if I'm really unsure what level you are meaning
here) will be achieved in 1-2 years. Unless much more energy is poured
into it than there is currently.

Samuel



Re: Missing mtab

2017-06-26 Thread Samuel Thibault
Narcis Garcia, on dim. 25 juin 2017 09:44:07 +0200, wrote:
> A Debian-live-Hurd could help in this situations, to perform a proper
> grub-install in this situation.

I don't think there is any grub issue here.

> I don't know if Debian-live-Linux can damage installation with same action.

I don't know. That's probably really not easy to do. To get the
parameters right, usually you just run grub-installer from a chroot
session, but you can't do that here.

That said you can just use the hurd debian installer as a rescue disk to
do the same.

Samuel



Re: Missing mtab

2017-06-26 Thread Samuel Thibault
Patrick, on sam. 24 juin 2017 18:10:48 -0400, wrote:
> Now that I am booting up the installed system I am getting errors about
> /dev/hd0s1 having errors and missing mtab. I am now at a rescue shell.

A screenshot would be way better for us to understand what happens than
vague sentences :)

The missing mtab thing is probably just a warning, and the real problem
is the errors on hd0s1, which you just need to fix by running e2fsck by
hand from the rescue shell.

> P.S this is an old laptop that could have bad sectors. I was able to install
> Minix 3 and Xubuntu on it but I am not 100% confident of it.

Bad sectors are really a bad thing.  To avoid them, I'd advise to use
a rescue disk to run badblocks and then pass the result to "mke2fs -o
hurd", and then run the installer and make it use the already-formated
volumes instead of reformating them.

Samuel