On a whim, I went to my Linux box and tried to mount the old workstation.
IT WORKED! (figured it was insecure since it had no root password). At
least now I have the data backed up in the event of HD failure. Other
hardwre, I'm probably screwed, but did notice several files like kconfig,
etc.
I did try to tar from the old box to the new one, but kept getting memory
overflow errors. Went the other way (mounted the old box from the new, and
it worked).
I was able to get the program to run after duplicating the environment
variables, but...got an iBCS error right away:
HEre is the screen shot (can anyone help on this?):
Copyright (c) 1991 U.S. AMADA Co., LTD. version 2.11
FMS LINE CONTROL SYSTEM(P.CELL)
Interactive UNIX
Loading the software, please wait ...
iBCS: ioctl(3, 6b00[..k], 0xbffff9a6) unsupported
SYSTEM ERROR : ioctl(): Invalid argument
At this point, software goes back to a command prompt with black on black
text (can't see what you type, just the prompt with a cursor that doesn't
move--shell not locked up).
-=>Jim Roland
"Never settle with words what you can settle with a flamethrower."
--Anonymous
On Mon, 27 Mar 2000, Michal Jaegermann wrote:
> Date: Mon, 27 Mar 2000 17:12:04 -0700 (MST)
> From: Michal Jaegermann <michal@ellpspace.math.ualberta.ca>
> To: Jim Roland <jim@roland.net>
> Subject: Re: Nostalgia: System V Release 2 filesystem
>
> Jim Roland wrote:
> >
> > I did manage to get them tarred across the network card (the technical tap
> > I gave it seemed to work), but tar would not read certain files, I presume
> > because they were in use/locked by the OS.
>
> No, probably not. An old tar which you have there, which is definitely
> not a GNU tar :-), will not read various "special" files like
> devices, sockets, etc. This is good as you do not want to end up
> with a content of the whole /dev/kmem, or equivalent, in your archive. :-)
> GNU tar is much smarter in that respect. If you have 'cpio', or
> similar, on your old machine it should deal better with such issues.
> But if this is really the case then you do not care about these anyway.
>
> Another possibility is that your disk starts to fall apart and these
> file were simply not readable. Yet another one is that these were some
> temporaries and they are listed when tar opens a directory but once you
> try to get the actual file it is already gone. But in general if this
> is a real file and you can read it as root then tar, run from a root
> account as well, should get it.
>
> Michal
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Mar 31 2000 - 21:00:21 EST