Debian bug report logs - #762, boring messages

Message sent to debian-devel@pixar.com:

Subject: Bug#762: Comments about and bugs in 0.93R5 base system
Reply-To: rjk1002@hermes.cam.ac.uk (Richard Kettlewell),         iwj10@cus.cam.ac.uk (Ian Jackson), debian-bugs@pixar.com
Resent-To: debian-devel@pixar.com
Resent-From: iwj10@cus.cam.ac.uk (Ian Jackson)
Resent-Sender: iwj10@cus.cam.ac.uk
Resent-Date: Sat, 08 Apr 1995 16:48:01 GMT
Resent-Message-ID: <debian-bugs-handler.762.040816432415573@pixar.com>
Message-Id: <m0rxbP3-0000YjZ.ijackson@nyx.cs.du.edu>
Date: Sat, 8 Apr 95 15:22 BST
From: iwj10@cus.cam.ac.uk (Ian Jackson)
To: Debian bugs submission address <debian-bugs@pixar.com>
Cc: rjk1002@hermes.cam.ac.uk (Richard Kettlewell)

Package: base
Version: 0.93R5

** Host/domain name

Perhaps there should be some advice about what to do about domain
names for machines not connected to the net.  I follow something
similar to the Dave Holland convention...

** Boot disk

When making a bootdisk, IMO an option should be offered to do run
fdformat; currently one must have a formatted disk to hand.

** During installation

*** Mount/unmount

In the mount/unmount menu after booting with the bootdisk/rootdisk
pair, I see the message:

        /sbin/dinstall: 361648: no such file or directory

Everything seems to work as expected otherwise, however.

[ I've reported this already, I believe. - iwj ]

** Booting Up

*** root password, user account

/root/.bash_profile~ did not appear to exist, which caused a rather
irritating loop when setting initial passwords, etc.  I don't know if
it was my fault that it did not exist (though I strongly believe that
it wasn't).

As a consequence of this -- or at least of my botched fix to it --
/sbin was not in root's PATH when I came to configure installed
packages; and when dpkg tried to configure the libc package, it
couldn't find ldconfig and left the libc.so.4 link stale (ditto libm).
All binaries requiring it failed to run.

However, after I fixed things and added /sbin to root's path, libc
installed without any problems.

[ I've reported this already, I believe. - iwj ]

(This bug is reported to me by Richard Kettlewell,
rjk1002@hermes.cam.ac.uk.  He doesn't have email connectivity at the
moment as it's out of term now and he's at home.)

Message sent:

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: rjk1002@hermes.cam.ac.uk (Richard Kettlewell),         iwj10@cus.cam.ac.uk (Ian Jackson)
Subject: Bug#762: Acknowledgement (was: Comments about and bugs in 0.93R5 base system)
In-Reply-To: <m0rxbP3-0000YjZ.ijackson@nyx.cs.du.edu>
References: <m0rxbP3-0000YjZ.ijackson@nyx.cs.du.edu>

Thank you for the problem report you have sent regarding Debian GNU/Linux.
This is an automatically generated reply, to let you know your message has
been received.  It is being forwarded to the developers' mailing list for
their attention; they will reply in due course.

If you wish to submit further information on your problem, please send
it to debian-bugs@pixar.com, but please ensure that the Subject
line of your message starts with "Bug#762" or "Re: Bug#762" so that
we can identify it as relating to the same problem.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Ian Jackson
(maintainer, debian-bugs)

Message sent:

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: imurdock@debian.org (Ian Murdock)
In-Reply-To: <m0t36vB-0001eDC@imagine.imaginit.com>
References: <m0t36vB-0001eDC@imagine.imaginit.com> <m0rxbP3-0000YjZ.ijackson@nyx.cs.du.edu>
Subject: Bug#762: marked as done (was: Comments about and bugs in 0.93R5 base system)

Your message dated Wed, 11 Oct 95 14:34 EST
with message-id <m0t36vB-0001eDC@imagine.imaginit.com>
and subject line Bug#762:
has caused the attached bug report to be marked as done.

It is your now responsibility to ensure that the bug report is dealt
with.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Ian Jackson
(maintainer, debian-bugs)

Received: with rfc822 via encapsulated-mail id 040816432415573;
          Sat, 08 Apr 1995 16:43:25 GMT
From cus.cam.ac.uk!iwj10 Sat Apr  8 09:42:20 1995
Return-Path: <iwj10@cus.cam.ac.uk>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0rxdaU-0005o7C; Sat, 8 Apr 95 09:42 PDT
Received: from bootes.cus.cam.ac.uk by pixar.com with SMTP id AA24734
  (5.65c/IDA-1.4.4 for <debian-bugs@pixar.com>); Sat, 8 Apr 1995 09:42:08 -0700
Received: by bootes.cus.cam.ac.uk
	(Smail-3.1.29.0 #30) id m0rxdaI-000BzfC; Sat, 8 Apr 95 17:42 BST
Received: by chiark
	id m0rxbP3-0000YjZ
	(Debian /\oo/\ Smail3.1.29.1 #29.30); Sat, 8 Apr 95 15:22 BST
Message-Id: <m0rxbP3-0000YjZ.ijackson@nyx.cs.du.edu>
Date: Sat, 8 Apr 95 15:22 BST
From: iwj10@cus.cam.ac.uk (Ian Jackson)
To: Debian bugs submission address <debian-bugs@pixar.com>
Cc: rjk1002@hermes.cam.ac.uk (Richard Kettlewell)
Reply-To: rjk1002@hermes.cam.ac.uk (Richard Kettlewell),
        iwj10@cus.cam.ac.uk (Ian Jackson)
Subject: Comments about and bugs in 0.93R5 base system

Package: base
Version: 0.93R5

** Host/domain name

Perhaps there should be some advice about what to do about domain
names for machines not connected to the net.  I follow something
similar to the Dave Holland convention...

** Boot disk

When making a bootdisk, IMO an option should be offered to do run
fdformat; currently one must have a formatted disk to hand.

** During installation

*** Mount/unmount

In the mount/unmount menu after booting with the bootdisk/rootdisk
pair, I see the message:

        /sbin/dinstall: 361648: no such file or directory

Everything seems to work as expected otherwise, however.

[ I've reported this already, I believe. - iwj ]

** Booting Up

*** root password, user account

/root/.bash_profile~ did not appear to exist, which caused a rather
irritating loop when setting initial passwords, etc.  I don't know if
it was my fault that it did not exist (though I strongly believe that
it wasn't).

As a consequence of this -- or at least of my botched fix to it --
/sbin was not in root's PATH when I came to configure installed
packages; and when dpkg tried to configure the libc package, it
couldn't find ldconfig and left the libc.so.4 link stale (ditto libm).
All binaries requiring it failed to run.

However, after I fixed things and added /sbin to root's path, libc
installed without any problems.

[ I've reported this already, I believe. - iwj ]

(This bug is reported to me by Richard Kettlewell,
rjk1002@hermes.cam.ac.uk.  He doesn't have email connectivity at the
moment as it's out of term now and he's at home.)

Message sent:

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: richard@elmail.co.uk (Richard Kettlewell),         iwj10@cus.cam.ac.uk (Ian Jackson)
Subject: Bug#762 acknowledged by developer (was: Comments about and bugs in 0.93R5 base system)
References: <m0t36vB-0001eDC@imagine.imaginit.com> <m0rxbP3-0000YjZ.ijackson@nyx.cs.du.edu>
In-Reply-To: <m0rxbP3-0000YjZ.ijackson@nyx.cs.du.edu>

This is an automatic notification regarding your bug report.

Responsibility for it has been taken by one of the developers, namely
imurdock@debian.org (Ian Murdock).

You should be hearing from them with a substantive response shortly, if
you have not already done so.  If not, please contact them directly,
or email debian-bugs@pixar.com or myself.

Ian Jackson
(maintainer, debian-bugs)

Ian Jackson / iwj10@thor.cam.ac.uk, with the debian-bugs tracking mechanism

This page last modified 07:43:01 GMT Wed 01 Nov