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

Bug#35435: marked as done ([Fixed for potato] Slink script to create /dev/sbpcd failure)

Your message dated 12 Aug 2000 17:33:00 -0400
with message-id <oawvhm9ncj.fsf@arroz.fake>
and subject line Processed: fixed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Darren Benham
(administrator, Debian Bugs database)

Received: (at submit) by bugs.debian.org; 1 Apr 1999 23:26:27 +0000
Received: (qmail 5766 invoked from network); 1 Apr 1999 23:26:26 -0000
Received: from bowe.ccm.net (maney@
  by master.debian.org with SMTP; 1 Apr 1999 23:26:26 -0000
Received: from localhost (maney@localhost)
	by bowe.ccm.net (8.9.1a/8.9.1) with ESMTP id RAA22213
	for <submit@bugs.debian.org>; Thu, 1 Apr 1999 17:27:11 -0600 (CST)
X-Authentication-Warning: bowe.ccm.net: maney owned process doing -bs
Date: Thu, 1 Apr 1999 17:27:11 -0600 (CST)
From: Martin Maney <maney@pobox.com>
X-Sender: maney@bowe.ccm.net
To: submit@bugs.debian.org
Subject: Slink script to create /dev/sbpcd failure
Message-ID: <Pine.BSI.4.05L.9904011700030.15905-100000@bowe.ccm.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Package: unknown

The scenario: installing slink on a machine with a known good SB and
"Panasonic" interfaced CD-ROM (Teac CD-55); both have been used in Linux
systems without problems, and installed correctly on this machine in the
separate partitions that contain Caldera 1.3.  Installation is from the
standard resc1440 & drv1440 floppies, written on a Hamm machine from the
Slink CD-ROM (Linux Central's, which sppears to be from the official
master image).

What happened: the module installed fine, but there appears to be a script
that runs after the module is installed; this script aborted after
creating the /dev/cdrom symlink to /dev/sbpcd0, but apparently prior to
creating the latter device file.  Of course the cdrom didn't work after
that.  The error referred to EOF in backquote [context?], and printed a
line of shell script that setup the symlink.

I'm sorry not to have more details, but after this happened for the second
time, which was when I actually read all of what was reported, I decided
it was much simpler to put the Slink CD into the Hamm machine and install
over NFS, which, as usual, worked just fine.

Received: (at 35435-done) by bugs.debian.org; 12 Aug 2000 21:32:39 +0000
>From adam@onshore.com Sat Aug 12 16:32:39 2000
Return-path: <adam@onshore.com>
Received: from relay03.netaddress.usa.net [::ffff:] 
	by master.debian.org with smtp (Exim 3.12 1 (Debian))
	id 13NitS-0005bg-00; Sat, 12 Aug 2000 16:32:38 -0500
Received: (qmail 12279 invoked from network); 12 Aug 2000 21:32:37 -0000
Received: from dsl-234-232-186-216.cust.dslnetworks.net (HELO arroz.fake) (postfix@
  by relay03.netaddress.usa.net with SMTP; 12 Aug 2000 21:32:37 -0000
Received: by arroz.fake (Postfix, from userid 421)
	id 3A8C893802; Sat, 12 Aug 2000 17:33:01 -0400 (EDT)
Sender: apharris@arroz.fake
To: 35435-done@bugs.debian.org (Debian Bug Tracking System)
Subject: Re: Processed: fixed
References: <20000806201857.C28908@finlandia.infodrom.north.de> <handler.s.C.9655859407342.transcript@bugs.debian.org>
From: Adam Di Carlo <adam@onshore.com>
Date: 12 Aug 2000 17:33:00 -0400
In-Reply-To: owner@bugs.debian.org's message of "Sun, 06 Aug 2000 14:49:47 -0500"
Message-ID: <oawvhm9ncj.fsf@arroz.fake>
Lines: 8
User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: 35435-done@bugs.debian.org

This has been fixed in the Potato version of the boot-floppies.
Thanks for reporting it.

PS: If Joey says so, good enough for me.

.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>

Reply to: