Sir,
As I understand it, if I were to type this at the shell:
ls >> /dev/hda1
Then, the output would put it at the *very beginning* of the partition,
stating with the very first area it is on. It doesn't have to be mounted.
(Ever format a disk? You CAN'T have the media mounted to format it.)
You're screwed, and you'll have to reinstall Win95 again. You've
corrupted at least the partition header, and probably the File Allocation
Tables for Windows, too.
You can try to boot with a boot disk, and "scandisk" it, but it'll
probably do you no good, it probably won't even recognize the partition
anymore.
Your partition is still accessable in this manner because you're directly
accessing the device. It's that simple (and don't do that again!). From
what I've learned thus far, UNIX (Linux) isn't any "smarter" than any
other operating system. It trusts what you tell it, and if you tell it to
chase it's tail all day, it will do just that. (Or tell you, "Define what
a tail is!") LOL...
As for your /dev/file question, I'll let someone who *knows* what they're
talking about with that answer that, 'cause as for that, I've not got a
clue.
Have a good day!
M Trausch
On 5 Jan 1999, Jayatheerthan Venkatramanan wrote:
> hi,
> i have got a system with win95(hda1) and linux(hda5). i didnt mount the win95
> partition. but i was fiddling with /dev directory as root. at one point of
> time i redirected ls to /dev/hda1. because of that the win95 partition got
> corrupted and was not getting booted.
>
> my question is:
> when i havent mounted the win95 partition, how is it that that partition
> is accessible?
> how /dev/file is related to the device when not mounted?
>
> Thanx
> Jay
>
> ____________________________________________________________________
> Get free e-mail and a permanent address at http://www.netaddress.com/?N=1
>
>
