From: sms@2BSD.COM (Steven M. Schultz)
Subject: [pups] Progress on 2.11BSD kernel
Date: Fri, 21 Mar 2003 10:26:17 -0800 (PST) [thread overview]
Message-ID: <200303211826.h2LIQH906763@moe.2bsd.com> (raw)
Hi -
> From: "Ian King" <iking at killthewabbit.org>
> Now I know I'm missing something. I tried following your advice, using the
> disklabel utility running under the old kernel. From what you say below, I
Which part of the advice? ;)
The part of the advice that might be most useful was to put a
copy of the standalone disklabel program in / and boot it - NOT
run the usermode version while the system is running.
cd /sys/pdpstand
make
cp disklabel /
then reboot the system and at the ':' prompt enter ra(0,0)disklabel
there are things that can be done with the standalone version that
are either impractical under a kernel (because the 'a'/root partition
is open/busy) or because the standalone version has no safety checks.
> assume you are referring to the 'fstype' parameter on the partition, not the
> 'type' parameter for the drive, correct? The drive type is MSCP, and the
> partition fstype is 2.11BSD.
'fstype' is what I had in mind.
a: 16720 0 2.11BSD 1024 1024 # (Cyl. 0 - 39)
> I tried changing the partition type with disklabel -e -r but, when I exited
> vi, I got an error message saying that the type I'd provided was not valid.
> Viewing the label (with disklabel -r) showed the fstype set to 'unknown'.
Now I am confused. 2.11BSD is correct - but then it's "unknown" and
that would cause the 'iinit' panic that started this thread of
discussion.
Down the path of logic that results in a 'iinit' panic and the
'no fs' there's a check for the filesystem type and "unknown" was the
likely cause (or at least that was the hope).
If the standalone disklabel program says it's "2.11BSD" then there's
something else going on - the next likely thought is that 'rootdev'
or related entity isn't set to the device that is the actual root
filesystem.
> Just for grins, I tried modifying the drive type, too - no success there,
> either. The disklabel utility isn't having any of that; again it claims
> 'unknown'.
That's not used for anything important.
> Oh well, while I'm waiting for your reply I can rebuild my kernel with a
> higher MAXUSERS parameter. :-)
~12 is a good number - not much need for more than that as a rule.
Steve
next reply other threads:[~2003-03-21 18:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 18:26 Steven M. Schultz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-21 18:33 Steven M. Schultz
2003-03-19 23:52 Steven M. Schultz
2003-03-19 23:08 Steven M. Schultz
2003-03-19 23:15 ` David Evans
2003-03-19 23:34 ` Johnny Billquist
2003-03-19 19:09 Steven M. Schultz
2003-03-19 19:30 ` David Evans
2003-03-19 19:06 Carl Lowenstein
2003-03-19 19:14 ` David Evans
2003-03-19 20:12 ` David C. Jenner
2003-03-19 17:51 Steven M. Schultz
2003-03-19 18:08 ` David Evans
2003-03-19 17:36 Steven M. Schultz
2003-03-19 17:46 ` David Evans
2003-03-19 18:24 ` Ian King
2003-03-19 18:59 ` David Evans
2003-03-21 18:08 ` Ian King
2003-03-19 7:44 Ian King
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=200303211826.h2LIQH906763@moe.2bsd.com \
--to=sms@2bsd.com \
/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;
as well as URLs for NNTP newsgroup(s).