View Single Post

   
  #9 (permalink)  
Old 03-04-2008, 07:22 AM
Bela Lubkin
 
Posts: n/a
Default Re: Access a SCO 3.0 drive from 5.0.6?

"jerry" wrote:

> Uzytkownik <jfranks1970@gmail.com> napisal w wiadomosci
> news:7d432477-cef7-42d3-9b02-101e1f2c176b@h25g2000hsf.googlegroups.com...
> >I have an old machine with SCO 3.0 and no networking. I need the data
> > off the IDE drive. I put this drive in a 5.0.6 box that I have and
> > ran mkdev hd, but it would never show the partitions on the drive (I
> > have since put the drive back in the old box and it boots fine.).
> >
> > When the old server boots, it does show /usr mounting as S51K
> >
> > Any ideas on how to get this to work? Do I need to mkdev hd first or
> > can I just access the filesystem directly somehow?

>
> I don't know haw was it on SCO 3.0, but on 3.2v4.2 and 5.0.5 system don't
> mount partitions - only divisions. And I'm not shure, it is posiible to use
> 2 disks witch the same names of divisions.?


Division names are not stored in the division table. Names are
associated with divisions by the existence of device nodes in /dev with
the right major/minor numbers. So if you add an old root drive to an
existing system (no longer the root drive), all the minor numbers will
have changed and its divisions appear "nameless".

Recent versions of `divvy` will show you the embedded filesystem names
(as written by `fsname` and/or `labelit`), and sufficiently new systems
will even have had those stamps put in automatically. Definitely not
3.2v4.2, ODT 3.0 (which was 3.2v4.2-based), nor even OSR505. A drive
from one of those OSes will just appear to have no names, you must
assign new ones in `divvy`.

>Bela<

Reply With Quote