mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-kernel@vger.kernel.org
Subject: more on UMSDOS
Date: Thu, 15 Jan 2004 07:56:10 -0600	[thread overview]
Message-ID: <20040115135610.GA19462@dbz.icequake.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]


I did some more experimenting along the lines of my previous post ("some
UMSDOS issues").

I verified that the 2.2.19 kernel from ZipSlack 8.0 at least finds init
and starts running startup scripts like it should within the 9.1 setup,
so there is nothing wrong with the installation.

I also verified that the files 2.4.24 claims is missing (/etc/rc.d/rcS,
/sbin/agetty, et.al) actually do exist in the filesystem.

Slack 9.1 ships with 2.4.18, which I tried first, and it as well as
2.4.24 produce the same results; unable to find files that clearly exist
in the UMSDOS filesystem.

I find it hard to believe that ZipSlack 9.1 would have shipped broken.
More likely, some strange interaction with my system is happening:
AMD 386DX-40
16MB RAM
2G Quantum ATA HD
ISA IDE & I/O controller
S3 928 2MB ISA video
1.44MB & 360k fdds
SB16 SCSI-2 w/2X SCSI CD
NE2000 at 0x280 irq 3

It all works fine with ZipSlack 8.0 which ships with a 2.2.19 kernel,
and that 2.2.19 kernel used in ZipSlack 9.1 gets the boot process past
the part where it can't find files with the 2.4.18 and 2.4.24 kernels.

any ideas?

-- 
Ryan Underwood, <nemesis@icequake.net>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2004-01-15 13:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040115135610.GA19462@dbz.icequake.net \
    --to=nemesis-lists@icequake.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®