'unsubscribe'

[Jesse <jesse brunet bn>]

Peter Dulimov wrote:
> 
> Joshua,
> 
> Thanks for your reply. I guess the problem is that I really don't understand
> what is going on. After all, I have the disk partitioned now (using the
> cfdisk utility that comes with RH3.0.3), so why don't I just install over
> the top of the current partitions? Well, the answer is that something that
> used to work just fine and dandy no longer does, and I'd like to understand
> what is going on so that if the problem produces further difficulties down
> the track I know what to do about it.
> 
> With respect to what you told me, I don't believe that I even get the
> opportunity to use fdisk (although thank you very much for your detailed
> instructions). When I hit the button that says "install" during the setup
> install procedure on the RH4.2 PowerTools CD, that is when the "error"
> message pops up. I don't get an opportunity to put anything on any command
> line. (I don't get the opportunity to use cfdisk either.) The point I was
> trying to make in the old posting was that in previous versions of the setup
> routine, I had the chance to pick between fdisk and cfdisk, and I always
> chose cfdisk. I was just wondering out aloud whether fdisk was broken in
> previous versions and I just didn't know it because I never used it. I have
> checked however since that posting, and I know that the current version of
> fdisk is the same as the old (3.0.3) version, and that it works when invoked
> from the command line.
> 
> These days I am tending toward the hypothesis that something broke during
> Redhat's efforts to get the install procedure down to a "one floppy
> operation". This theory comes from the fact that I am slowly eliminating all
> of the other alternatives (nothing left to speculate about!). I am sure that
> you noticed that the SCSI card is not reported correctly during the second
> stage install, as evidenced by the [ALT - F3] screen. This is the only
> "smoking gun" in the whole exercise - the version of fdisk on the CD seems
> ok, I had the 2.30 kernel working in the past (it was compiled from the 4.0
> install), the hardware is unchanged. I note that the AHA2940 is not a good
> SCSI adapter card to be using, but it was working without a problem until
> this current episode. I also note that the RH H/W compatibility list gives a
> black mark against my m'board, but that is with respect to its handling of
> the keyboard, which has nothing to do with my current problem.
> 
> So what will I do? My current thinking is that I will just ignore the
> partion step, and stick the new install over the old setup, and then see
> what happens. Next Monday is a public holiday in my State, so I will get an
> opportunity to spend some time dicking around.
> 
> On the other hand, some genius at Redhat may realise that product sold
> outside of the US doesn't have product registration numbers - and so we are
> stuck "supportless" although for example I have now paid for RH3.0.3
> "Official Version", RH Motif, and RH4.2 PowerTools (the 4.0 disks were
> borrowed from a friend). If RH recognised the "rest-of-the-world", (as in
> where Linus Torvalds comes from - or is Helsinki in Michigan nowadays?),
> then maybe I would have a hope of getting a serious solution to this.  And
> then maybe not.
> 
> Sorry to rant like that but I'm tired and pissed off.
> 
> Regards,
> 
> Peter Dulimov.
> dulimov rill me su oz au
> 
> At 09:17 29/09/97 -0600, you wrote:
> >Wait, you said that Linux was installed just fine?  Does that mean you
> >have a 'swap' partition, and a 'native' ext2fs partition setup already?
> >Why don't you just run an Upgrade install?  It is a piece of cake, and I
> >think it would be the best.   Just install Redhat 4.0, then Install
> >Redhat 4.2  If you don't have that luxury, and you DON'T have your
> >partitions setup on the disk here is what I say:
> >
> >       First, use the 'tab' button to move between disks. (Assuming you have
> >more than one).
> >       Fear not the command line utilites.  For they are simple, and easily
> >mastered!  When using fdisk, just hit '?' that will give you a list of
> >options. I.E. 'p' to list your current partition setup.  If you have a
> >CLEAN disk, (I.E. no partitions, or ONES YOU WANT TO GET RID OF).   To
> >create a normal partition, just use 'n' then select 'p' for primary,
> >then 1 - 4 depending on whats free.  The beginning block, just use the
> >first availible, then select your size in megabyte like this: '+160M'
> >for 160 megs, or '+1024M' for 1 gig.   Peice of Cake.  If you have a
> >CLEAN unused disk, I would recommend using for first chuck of it for
> >Swap,  in that case you would make your partition about 2 megs bigger
> >than ram. (I have never actually seen my Linux box seriously use swap
> >space, but in the event that it does I want it to be FAST, and that is
> >the recommended formula.  If you are going to be upgrading ram soon, I
> >would set it to the size that you intend to upgrade to. I.E.: if you
> >intend to use 32 megs, set it to 34.) You just create the partition:
> >'n', then 'p', then '1', then '1'(beginning block), then '+34M'.   Then
> >you use 'l' to show you all the types of partitions there are. (Note:
> >82=Linux Swap, 83=Ext2fs (Linux Native)), then hit 't', then '1', then
> >for the type: '82'.  It will automatically set all new partitions to
> >Ext2Fs.  Also if you screw up, or don't like how it's going, use 'q' to
> >quit W/O saving.  When you like your setup, push 'p' to look one more
> >time, if you like it, then push 'w' for write, then quit.   Peice of
> >cake man, it really is.  Not very friendly at first, but it is quite
> >simple.  Of you need an help feel free to write.
> >
> >joshua - menion mindless com
> >
> >
> >
> >Peter Dulimov wrote:
> >>
> >> Hello,
> >>
> >> Firstly, apologies for cross-posting. However, my last post was a reasonable
> >> period of time ago. I didn't get an answer, so I am trying on this list
> now...
> >>
> >> ---------
> >>
> >> Greetings,
> >>
> >> A little while ago I had a problem with a corrupt init, so I decided
> >> to erase my hard-drive and re-install RedHat Linux.  Since I was doing
> >> an install, I went and bought the new Redhat 4.2 Powertools CD so that
> >> I can be moderately current with all the new stuff floating around.
> >>
> >> Anyway, I didn't get very far though the install process when this
> >> problem popped up.  The setup script asks if I want to install or
> >> upgrade, and since I low-level formatted my hard disk already I say
> >> "install" and then the script tells me that I have a problem
> >> formatting my disk. The options are "previous", "re-try" or "menu",
> >> but nothing that I do gets past this problem.
> >>
> >> The salient point is that Redhat 3.0.3 (Picasso) and 4.0 (Colgate)
> >> both installed totally painlessly on EXACTLY the same hardware, and
> >> more importantly, I was able to install RH 3.0.3 immediately after the
> >> 4.2 Install failed on exactly the disk that I was attempting to
> >> install on.
> >>
> >> The [alt - F3] screen says the following:
> >>
> >> * Second stage install running (version 1.1 built Apr 22 1997
> >> 16:03:02)
> >> * /proc/scsi/scsi: Attached devices:
> >>   Host: scsi0 Channel: 00 ld: 00 Lun: 00
> >>      Vendor:          Mo        <-----  This looks wrong??!?!
> >> * scsi devices are available
> >> * successfully opened: /tmp/sda
> >> * successfully opened: /tmp/sdb
> >> * /proc/scsi/scsi: Attached devices:
> >>   Host: scsi0 Channel: 00 ld: 00 Lun: 00
> >>      Vendor:          Mo
> >> * scsi devices are available
> >> * Rev missing in /proc/scsi/scsi
> >>
> >> My Hardware configuration is as follows:
> >>
> >> Intel Pentium (Triton) 133 MHz
> >> M'board Super Micro P55T2S
> >> Adaptec AHA 2940 scsi card scsi ID #7, BIOS version 1.16
> >> Quantum Atlas XP32150W 2 gb hard-drive on scsi ID #0
> >> IBM DCAS32160w on scsi ID #1  (THIS IS THE LINUX DISK)
> >>
> >> Both the hard drives are "wide" units that have those little plastic
> >> 68->50 converters.
> >>
> >> Sony scsi CDROM on scsi ID #3
> >> Matrox millenium video card, 2MB.
> >> creative SB32 PnP card (that has never worked under Linux - and I
> >> don't care.)
> >>
> >> Historically, what I have done is had Lilo on the superblock of the
> >> root partition of the Linux disk, and used that little boot disk
> >> utility from Gilles Vollant to get there.
> >>
> >> What I think is going on:
> >> In the past, the install script used to ask if I wanted to use cfdisk,
> >> fdisk, or skip the partition stage. I choose cfdisk, because I'm too
> >> stupid to use command lines, and it worked.
> >> Now in the current install, there is no option to use cfdisk. So I
> >> wonder if there is some default option being passed to fdisk without
> >> my knowing that is getting it wrong. Or maybe just the software for
> >> (c)fdisk was "upgraded", and in the process it got broke for those of
> >> us with older hardware?
> >>
> >> The question is: is there anything that I can do that can get around
> >> this seemingly insurmountable hurdle?
> >>
> >> All suggestions welcomed.
> >>
> >> Thanks,
> >>
> >> Peter Dulimov.
> >> dulimov rill me su oz au
> 
> --
>   PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
>          To unsubscribe: mail redhat-install-list-request redhat com
>                      with "unsubscribe" as the Subject.