Message-ID: <37DA1DD6.A9739897@smtp.uninet.ee>
Date: Sat, 11 Sep 1999 12:16:06 +0300
From: Pisi <pisi@smtp.uninet.ee>
Reply-To: pisi@uninet.ee
Organization: Pisi Cahtlased Tehingud, Inc.
X-Mailer: Mozilla 4.5 [en]C-CCK-MCD Uninet  (Win95; I)
X-Accept-Language: et,en
MIME-Version: 1.0
Newsgroups: comp.os.minix
Subject: Re: "at-hd0: can't read partition table"
References: <rt7djjot8os37@news.supernews.com> <37d73fef.3244298@news.bigpond.com> <jit7r7.cs3.ln@mega.am.cs.vu.nl>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 94
NNTP-Posting-Host: 194.204.25.101
X-Trace: 937041309 191 (none) 194.204.25.101
Path: news.adfa.oz.au!clarion.carno.net.au!news0.optus.net.au!news1.optus.net.au!optus!intgwpad.nntp.telstra.net!newsfeed.berkeley.edu!newsfeed.enteract.com!news.maxwell.syr.edu!skynet.be!newsfeed1.funet.fi!newsfeed.uninet.ee!diablo.uninet.ee!not-for-mail

Well.. 

I get this error message always if I try to do something with my hard
disk(quantum fireball EX 6.4 GB) under minix 2.0.2 or 2.0.0. Minix
vmd(what I actually need more than standard minix:) ) recognizes
everything and everything works. 
I don't know exactly how big variables standard minix uses for disks,
but I have a strange feeling that it showd maximum  2147483648 bytes.


pisi
pisi@uninet.ee


Kees J Bot wrote:
> 
> In article <37d73fef.3244298@news.bigpond.com>,
> David Lions <davidlions@hotmail.com> wrote:
> >
> >The other day I was looking for the password encryption code so I
> >looked for "login" in all .c files.  (I found it .. needless to say it
> >was really boring after about 5 minutes).  Here's how I did it :
> >
> >find / -name '*.c' >cfiles
> >
> >This locates all .c files, prints their names and directory to the
> >console, but I redirected stdio to file "cfiles" (did this as root
> >from /).  Then I did this :
> >
> >grep login <cfiles
> 
> You can cut this short with:
> 
>         find / -name '*login*.c'
> 
> >...and it printed out about 3 files, which at least called functions
> >from the file that I wanted.
> >
> >Check the syntax required for the -name option in 'find'.  You can't
> >just put a *.c in there, it had to be surrounded with something (can't
> >remember what).
> 
> You have to put quotes around the -name argument to keep the shell from
> expanding the '*'.  The shell has no idea that you want grep to do
> this, it will happily try to expand any '*', '?' or '[a-z]' like stuff
> anywhere on the command line.  (Under DOS it's the command that expands
> wildcards, under UNIX it's the shell doing it for the command.  Many a
> religious war has been fought on this subject in comp.unix.shell and
> other groups.)
> 
> >Happy searching!
> 
> For more happy searching:
> 
>         find /usr/src/kernel -type f | xargs grep 'read partition table'
> 
> I use the 'find | xargs grep' combo a lot to search for random strings
> *in* files.  (Reminds me that the new xargs for 2.0.2 doesn't work well
> in 16-bit mode, something I still haven't repaired.)
> 
> Xargs reads filenames from standard input (usually from 'find') and
> hands those names over to the command it's called with (in this case
> 'grep').  (Those who know the lisp language should note the similarity
> to the 'map' like functions.)  Alas xargs will trip over spaces in
> names.  Whoever decided that xargs should split names on any whitespace
> instead of just newlines was smoking some good stuff.
> 
> >Disclaimer : I am not a UNIX nerd.
> 
> You are already down the slippery slope to UNIX nerd-dom by knowing that
> 'find' exists.  And you're using Minix, so you're doomed.
> 
> >As such, I humbly confer greatness
> >on anyone who knows a better way, and bow before those who present
> >better suggestions.  I willfully acknowledge my lesser and less
> >refined existance.
> 
> A nice bit of groveling.  I'm impressed.
> 
> >P.S.  Sounds like your partition table is f*cked.  Well, doesn't take
> >long to reinstall Minix does it?  At least you didn't lose 150Mb of
> >MP3s when you installed yours.  (I overwrote my Fat32 D: drive,
> >because it said "unknown format", and I thought "ah, theres that empty
> >space I saved for Minix!".  Thus ended drive d:)
> 
> The "can't read partition table" message can result from an actual disk
> error, or a bad MINIX or extended partition entry in the partition
> table that makes the driver look for a subpartition table beyond the end
> of the disk.  (Or whatever Minix thinks is the end, the BIOS may be
> lying.)
> --
> Kees J. Bot, Systems Programmer, Sciences dept., Vrije Universiteit Amsterdam
> Minix:       http://www.cs.vu.nl/pub/minix/   ftp://ftp.cs.vu.nl/pub/minix/
> Minix-vmd:   http://www.Minix-vmd.org/        ftp://ftp.Minix-vmd.org/
