19 Apr
2002
19 Apr
'02
4:38 a.m.
Hi All again.
I have to say the Vax I got last week has been heaps of fun, picked up a
couple of bits for it today, like about 20 backup tapes (unfortunatly not
TK50 tapes) And a Nice VT420 Terminal.
Anyway decided to let VMS wait for a little before I try and learn this
odd but interesting system, (I am going to be joind decus so I can get new
VMS media as the machine didn't come with any) so I have had a look at the
other avalible OSes that are avalible for the VAX.
A quick question was ULTRIX ever avalible for the uVAX 3100/80?
The two "free" operating systems that seem to be avalible for the 3100/80
are NetBSD and OpenBSD (there seems to be a version of linux but it seems
to be quite imature.)
I now have had a play with both (and If anyone ever needs a hand setting
up either of these just give me a yell.)
The NetBSD install was realy easy, I booted the vax via the network, and
then did a [ctrl] + [z] and then using ftp pulled the .tgz files to the
vax and installed the os from the local hard drive. The only issue was
that the NetBSD install was sparse to say the least, and after compiling a
couple of things (which was quite slow, but no where as slow as my first
linux pc ;) I decided to give OpenBSD a go.
OpenBSD is great, still it doesn't have all that I want, but has a lot
more than NetBSD. The install is a little hairy in places, and it took me
a while to configure the FreeBSD i386 box I am using for a boot server
(the OpenBSD net boot process is a little differnt that NetBSD) but the
install went painlessly.
To sum up, and sorry if this is a little off topic. If anyone is looking
for something other than VMS to run on their Vaxes, I would reccomend
OpenBSD over NetBSD.
I Hope I havent bored you too much....
Benjamin
19 Apr
19 Apr
5:27 a.m.
Hi All again.
I have to say the Vax I got last week has been heaps of fun, picked up
a couple of bits for it today, like about 20 backup tapes
(unfortunatly not TK50 tapes) And a Nice VT420 Terminal.
Anyway decided to let VMS wait for a little before I try and learn this
odd but interesting system, (I am going to be joind decus so I can get
new VMS media as the machine didn't come with any) so I have had a
look at the other avalible OSes that are avalible for the VAX.
A quick question was ULTRIX ever avalible for the uVAX 3100/80?
The two "free" operating systems that seem to be avalible for the
3100/80 are NetBSD and OpenBSD (there seems to be a version of linux
but it seems to be quite imature.)
I now have had a play with both (and If anyone ever needs a hand
setting up either of these just give me a yell.)
The NetBSD install was realy easy, I booted the vax via the network,
and then did a [ctrl] + [z] and then using ftp pulled the .tgz files
to the vax and installed the os from the local hard drive. The only
issue was that the NetBSD install was sparse to say the least, and
after compiling a couple of things (which was quite slow, but no where
as slow as my first linux pc ;) I decided to give OpenBSD a go.
Pkgsrc is your friend. Ckeck http://www.netbsd.org/Documentation/software/
for your software needs. Unlike the ``Distros'' of the Penguin the *BSD's
are just BSD, with just the standard tools you can expect to find on
most/all unix platforms
OpenBSD is great, still it doesn't have all that I want, but has a lot
more than NetBSD. The install is a little hairy in places, and it took
me a while to configure the FreeBSD i386 box I am using for a boot
server (the OpenBSD net boot process is a little differnt that NetBSD)
but the install went painlessly.
To sum up, and sorry if this is a little off topic. If anyone is
looking for something other than VMS to run on their Vaxes, I would
reccomend OpenBSD over NetBSD.
OpenBSD _is_ NetBSD for the most part. It branched a few years back, but I
don't think you can even say they went their seperate ways-- they still
share code back and forth.
If you want to run the same OS on most of you hardware I recommend NetBSD.
It suits my sun3, sun4, hp300, nvax, i386, & m68k mac just fine...
I Hope I havent bored you too much....
Benjamin
Bob
20 Apr
20 Apr
11:28 a.m.
On 19 Apr, cvisors(a)carnagevisors.net wrote:
A quick question was ULTRIX ever avalible for the uVAX
3100/80?
No.
(there seems to be a version of linux but it seems
to be quite imature.)
.... and it ever will be.
OpenBSD is great, still it doesn't have all that I
want, but has a lot
more than NetBSD.
This is not a bug, it is a feature. ;-)
NetBSD is minimalistic and this is one reason why I like it. You just
add what you need via pkgsrc and you get a system that has exactely
what you want, and nothing more. It is most bloat less.
If you wane try NetBSD again, please use the ELF snapshot of -current.
Many improvements, but it needs some more testers...
--
tschuess,
Jochen
Homepage: http://www.unixag-kl.fh-kl.de/~jkunz
21 Apr
21 Apr
4:31 p.m.
On Sat, 20 Apr 2002 jkunz(a)unixag-kl.fh-kl.de wrote:
On 19 Apr, cvisors(a)carnagevisors.net wrote:
I may have to do so (re NetBSD).
I am just playing round with *BSD on this machine at the moment, and will
probably settle on one or the other..
Though I like OpenBSD due to all of the crypto stuff, and it saves me
having to compile it all, and it still isn't bloated unlike linux can
be.
BTW quick question.
the machine came with an external scsi expansion with two drives, one of
the drives refuses to power up properly, but that is dependent on where it
is sittin in the scsi expansion, ie if I switch the drives around the
other will work and the one that was working doesnt.
any Ideas?
Benjamin
A quick question was ULTRIX ever avalible for the
uVAX 3100/80?
No.
(there seems to be a version of linux but it
seems
to be quite imature.)
.... and it ever will be.
OpenBSD is great, still it doesn't have all
that I want, but has a lot
more than NetBSD.
This is not a bug, it is a feature. ;-)
NetBSD is minimalistic and this is one reason why I like it. You just
add what you need via pkgsrc and you get a system that has exactely
what you want, and nothing more. It is most bloat less.
If you wane try NetBSD again, please use the ELF snapshot of -current.
Many improvements, but it needs some more testers...
22 Apr
22 Apr
7:13 a.m.
On Mon, Apr 22, 2002 at 11:31:19AM +1000, cvisors(a)carnagevisors.net wrote:
I am just playing round with *BSD on this machine at
the moment, and will
probably settle on one or the other..
Yes. Evaluate the choices and take the one
that suites your needs best.
the machine came with an external scsi expansion with
two drives, one of
the drives refuses to power up properly, but that is dependent on where it
is sittin in the scsi expansion, ie if I switch the drives around the
other will work and the one that was working doesnt.
Ahhh. Bad PWR connector?
Does "refuses to power up properly" mean: Does not spin up but is present
on the SCSI bus. Or: Does not spin up and is not present on the SCSI bus?
--
tsch??,
Jochen
Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
2:27 p.m.
On Mon, 22 Apr 2002, Jochen Kunz wrote:
On Mon, Apr 22, 2002 at 11:31:19AM +1000,
cvisors(a)carnagevisors.net wrote:
It doesn't spin up but is present on the SCSI bus, thats whats happening.
I didn't think it would be the power connector for the drive, as it comes
out of the power supply, loops to the drive that doesn't work and then to
the drive that does.
Benjamin
I am just playing round with *BSD on this machine
at the moment, and will
probably settle on one or the other..
Yes. Evaluate the choices and take the one
that suites your needs best.
the machine came with an external scsi expansion
with two drives, one of
the drives refuses to power up properly, but that is dependent on where it
is sittin in the scsi expansion, ie if I switch the drives around the
other will work and the one that was working doesnt.
Ahhh. Bad PWR connector?
Does "refuses to power up properly" mean: Does not spin up but is present
on the SCSI bus. Or: Does not spin up and is not present on the SCSI bus?
23 Apr
23 Apr
3:55 a.m.
On Tue, Apr 23, 2002 at 09:27:31AM +1000, cvisors(a)carnagevisors.net wrote:
It doesn't spin up but is present on the SCSI bus,
thats whats happening.
On most SCSI drives you can disable spin up via jumpers. Is
there a
cable for SCSI ID select connected to that drive? Maybe there is the
"do not spin up" jumper cnnected with that cable too...
But NetBSD schould detect the drive and spin it up uppon boot,
as should a "sh dev" from the boot prompt.
--
tsch??,
Jochen
Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
25 Apr
25 Apr
6:11 p.m.
On Tue, 23 Apr 2002, Jochen Kunz wrote:
On Tue, Apr 23, 2002 at 09:27:31AM +1000,
cvisors(a)carnagevisors.net wrote:
I think there is something wrong with the power connector for the drive,
as I don't believe its the drive that is causing the issue...
Benjamin
It doesn't spin up but is present on the SCSI
bus, thats whats happening.
On most SCSI drives you can disable spin up via
jumpers. Is there a
cable for SCSI ID select connected to that drive? Maybe there is the
"do not spin up" jumper cnnected with that cable too...
But NetBSD schould detect the drive and spin it up uppon boot,
as should a "sh dev" from the boot prompt.
8119
days inactive
8125
days old
7 comments
3 participants
participants (3)
-
cvisors＠carnagevisors.net -
jkunz＠unixag-kl.fh-kl.de -
rschaefe＠gcfn.org