15 May
2002
15 May
'02
7:28 a.m.
--- Rick Murphy <rmurphy(a)itm-inst.com> wrote:
At 03:49 PM 5/14/02 -0700, Ethan Dicks wrote:
>I'm trying to break into (my own) DEC Alpha running Digital Unix V3.2...
Use:
>>> b -flags 0,1 dkc0
Why the 0? I did this (Thanks, Doc!)
>> b dkc0 -flags 1
... and I got in just fine.
Once you're in single-user mode, "mount -r
/" to remount the root...
Right. I know what to do once I'm in. The only thing that threw me
about Digital Unix vs other stuff I've used is that if you _don't_
use vipw to edit the passwd file, you have to manually run mkpasswd
to update the hashed password file (I'm used to a shadow file, or,
for older stuff, _just_ the /etc/passwd file and nothing else).
...mount -a to get everything mounted...
In my experience, if you intend to go from single-user mode to
multi-user (i.e., you don't reboot from single-user), it's
safest to not leave anything mounted that isn't mounted when
you got your prompt. I'm not saying this is the case for Digital
Unix, but for older BSDish stuff I used in the past, if you,
say, mounted /usr/home while in single user mode, then ^D to
exit your shell and allow the system to start up, but haven't
unmounted /usr/home first, the startup scripts complain about
a busy mount point or some other complaint. I always leave the
system the way I found it, which is / mounted read-only, everything
else unmounted. What you suggest might work these days, but I
cut my teeth on 4.0BSD and Ultrix 1.1. This is just my first
experience with Digital Unix on an Alpha.
Still curious about the "0" in your sample line, though.
Thanks for the tip,
-ethan
__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com
15 May
15 May
7:57 a.m.
Ethan,
the "-flags" option of the "boot" command takes _one_or_two_
longwords
as an argument, so specifying "-fl 1" defaults to "-fl 0,1". Both set
the high-order longword to zero, and the low-order longword to one,
which for Unix seems to mean single-user mode. For VMS, it would mean
conversational bootstrap.
I believe DEC put the comma in for readability. With a VAX' comparable
/R5:n option, you could have up to eight hex digits, which is
acceptable, but sixteen hex digits with "-flags n" would just be too
much to read comfortably.
BTW: If dkc0 is set as your default boot device (bootdef_dev), you
should be able to just "b" into normal (multiuser) operating mode, or "b
-fl 1" if you need something special.
Andreas
Ethan Dicks wrote:
--- Rick Murphy <rmurphy(a)itm-inst.com> wrote:
...
At 03:49 PM 5/14/02 -0700, Ethan Dicks wrote:
>I'm trying to break into (my own) DEC Alpha running Digital Unix V3.2...
Use:
>>> b -flags 0,1 dkc0
Why the 0? I did this (Thanks, Doc!)
>> b dkc0 -flags 1
... and I got in just fine. Still curious about the "0" in your sample
line, though.
Thanks for the tip,
-ethan
--
Andreas Freiherr
Vishay Semiconductor GmbH, Heilbronn, Germany
http://www.vishay.com
8:14 a.m.
--- Andreas Freiherr <Andreas.Freiherr(a)vishay.com> wrote:
Ethan,
the "-flags" option of the "boot" command takes _one_or_two_
longwords
as an argument...
Thanks for the clarification. I'm used to the older /R5:00000000...
method.
BTW: If dkc0 is set as your default boot device
(bootdef_dev), you
should be able to just "b" into normal (multiuser) operating mode, or "b
-fl 1" if you need something special.
It is not. 'b' by itself referenced a disk array that is no longer
attached to this machine (I got it from surplus and I appear to have
gotten the CPU cabinet but not an expansion cabinet). I have two
trays of RZ26s (3 each), one RZ73 and one tray with no power converter,
just a 50-pin blue-ribbon SCSI-1 connector for attachment to the
"missing" 6 drives (according to the logs I've been perusing).
When 'b' didn't work, I just started booting the first drive on
every shelf until it came up... third time's the charm in this case.
Thanks for the exposition on flags.
-ethan
__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com
8:32 a.m.
On Wednesday 15 May 2002 17:28 pm, Ethan Dicks wrote:
--- Rick Murphy <rmurphy(a)itm-inst.com> wrote:
^^^^^ Hmm....I seem to have not got Rick's message for some reason.
> At 03:49 PM 5/14/02 -0700, Ethan Dicks wrote:
> >I'm trying to break into (my own) DEC Alpha running Digital Unix
> > V3.2...
I'm trying to do the same on OSF1/Digital Unix v4.0
> Once you're in single-user mode, "mount
-r /" to remount the root...
This doesn't want to work for me - keeps saying 'device busy'. I can't get
a man page for 'mount' up, because the root fs (and therefore /tmp) is
read-only, and I don't have another Digital Unix 4.0 box to get a man
page up on :-) Could anyone kindly point me towards the right options for
remounting a mounted filesystem read-write?
Thanks,
Dan
--
If you eat a live frog in the morning, nothing worse will happen to
either of you for the rest of the day.
10:29 p.m.
At 06:32 PM 15/05/2002 +0100, Dan Kolb wrote:
This doesn't want to work for me - keeps saying
'device busy'. I can't get
a man page for 'mount' up, because the root fs (and therefore /tmp) is
read-only, and I don't have another Digital Unix 4.0 box to get a man
page up on :-) Could anyone kindly point me towards the right options for
remounting a mounted filesystem read-write?
Assuming that you have another box with an internet connection and a web
browser, the Tru64 doc set can be found at
http://www.tru64unix.compaq.com/docs/pub_page/doc_list.html
Huw Davies | e-mail: Huw.Davies(a)kerberos.davies.net.au
| "If God had wanted soccer played in the
| air, the sky would be painted green"
12:14 p.m.
At 09:28 AM 5/15/02 -0700, Ethan Dicks wrote:
Right. That's why I suggested mounting everything and using "passwd" :-)
True. I usually fix the password and reboot to avoid the startup problems.
Arguably, your approach of cleaning up what you changed then exiting the
shell will get you back running faster.
-Rick
--- Rick Murphy <rmurphy(a)itm-inst.com> wrote:
The command I learned is "-flags 0,1". The first digit sets the root being
booted, the second is a bitmap where the "1" bit means conversational boot.
(See the VMS ALPHA FAQ.) However, "-flags 1" usually works just as well; I
just learned the long way back when I worked on DEC UNIX.
At 03:49 PM 5/14/02 -0700, Ethan Dicks wrote:
>I'm trying to break into (my own) DEC Alpha running Digital Unix V3.2...
Use:
>>> b -flags 0,1 dkc0
Why the 0? I did this (Thanks, Doc!) >> b dkc0
-flags 1
... and I got in just fine.
Once you're in single-user mode, "mount
-r /" to remount the root...
Right. I know what to do once I'm in. The only thing that threw me
about Digital Unix vs other stuff I've used is that if you _don't_
use vipw to edit the passwd file, you have to manually run mkpasswd
to update the hashed password file (I'm used to a shadow file, or,
for older stuff, _just_ the /etc/passwd file and nothing else). ...mount -a to
get everything mounted...
In my experience, if you intend to go from single-user mode to
multi-user (i.e., you don't reboot from single-user), it's
safest to not leave anything mounted that isn't mounted when
you got your prompt.
10:24 p.m.
At 09:28 AM 15/05/2002 -0700, Ethan Dicks wrote:
Still curious about the "0" in your sample
line, though.
It's because the flag register is a 64 bit quantity. The first digit is the
top 32 bits, the digit after the comma is the lower. AFAIK the top 32 bits
aren't used in Tru64 but when booting OpenVMS they are used to indicate the
system root to boot from when you have a shared system disk.
Huw Davies | e-mail: Huw.Davies(a)kerberos.davies.net.au
| "If God had wanted soccer played in the
| air, the sky would be painted green"
8104
days inactive
8105
days old
6 comments
5 participants
participants (5)
-
Andreas.Freiherr＠Vishay.com -
dankolb＠ox.compsoc.net -
erd_6502＠yahoo.com -
Huw.Davies＠kerberos.davies.net.au -
rmurphy＠itm-inst.com