Slackware 8.1.01 Install????

Slackware 8.1.01 Install????

[Hal MacArgle]

Greetings: Slackware 8.1.01 installs easily on our machines with an
IDE HD and IDE CD, booting the CD nicely and installing from the CD,
with the BIOS set properly..

However; the subject machine has an IDE 20gB HD and a __SCSI CD__,
with a BusLogic SCSI card, creating an insurmountable problem - so
far - and maybe forever. <grin> (The card and drive working
flawlessly with the other partitions.)

The drive has 4 Linux partitions; two working with Slack8.0 and one
swap of course.. Previous versions of Slackware utilized two boot
floppies; one booting the selected image and the 2nd with a "root"
file.. No problem.. Worked fine for years..

8.1 is different and the boot from CD works except as above, but
there is a file 'makedisk' that is supposed to circumvent the non CD
problem.. Invoking makedisk, as instructed, with the proper bzImage
entered, in my case scsi.s should work with both an IDE drive and a
BusLogic card, reports much on the screen but does NOT make a boot
floppy.. I tried several other images to no avail.. I tried both cat
and dd transferring the images to /dev/fd0, but apparently a standard
1.44 floppy isn't big enough. I tried formatting the floppies at both
1.68mB and 1.7X, but no joy as far as booting the floppy.. Apparently
bzImage alone is not enough to get things going.

The excellent slackware-HOWTO details perfectly an install as long as
you have an IDE HD _and_ CD.. No other README's shed any light..

As of now I've concluded the only _easy_ way out is to termporarily
fit an IDE CD for the install and then re-fit the SCSI CD.. What do
YOU think??? Appreciate!!

    Hal - in Terra Alta, WV - Slackware GNU/Linux 8.0   (2.4.18)
                Proprietary  Formats  Unacceptable
.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[pa3gcu]

On Thursday 29 May 2003 22:54, Hal MacArgle wrote:
> Greetings: Slackware 8.1.01 installs easily on our machines with an
> IDE HD and IDE CD, booting the CD nicely and installing from the CD,
> with the BIOS set properly..
>
> However; the subject machine has an IDE 20gB HD and a __SCSI CD__,
> with a BusLogic SCSI card, creating an insurmountable problem - so
> far - and maybe forever. <grin> (The card and drive working
> flawlessly with the other partitions.)
>
> The drive has 4 Linux partitions; two working with Slack8.0 and one
> swap of course.. Previous versions of Slackware utilized two boot
> floppies; one booting the selected image and the 2nd with a "root"
> file.. No problem.. Worked fine for years..
>
> 8.1 is different and the boot from CD works except as above, but
> there is a file 'makedisk' that is supposed to circumvent the non CD
> problem.. Invoking makedisk, as instructed, with the proper bzImage
> entered, in my case scsi.s should work with both an IDE drive and a
> BusLogic card, reports much on the screen but does NOT make a boot
> floppy.. I tried several other images to no avail.. I tried both cat
> and dd transferring the images to /dev/fd0, but apparently a standard
> 1.44 floppy isn't big enough. I tried formatting the floppies at both
> 1.68mB and 1.7X, but no joy as far as booting the floppy.. Apparently
> bzImage alone is not enough to get things going.
>
> The excellent slackware-HOWTO details perfectly an install as long as
> you have an IDE HD _and_ CD.. No other README's shed any light..
>
> As of now I've concluded the only _easy_ way out is to termporarily
> fit an IDE CD for the install and then re-fit the SCSI CD.. What do
> YOU think??? Appreciate!!

There could be another way;
I have installed slackware 9 on a couple of machines using old slack 8.0 boot 
floppys.
Simply try and boot with slack's 8.0 scsi.s and color.gz and then after 
booting place the slack 8.1 cdrom in the drive.
Of course this may not work for you but it has worked for me on several 
occations.

>     Hal - in Terra Alta, WV - Slackware GNU/Linux 8.0   (2.4.18)
>                 Proprietary  Formats  Unacceptable
> .
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[Chuck Gelm]

Hal MacArgle wrote:
> 
> Greetings: Slackware 8.1.01 installs easily on our machines with an
                                              ^^^^^^^^^^^^^^^
Do a 'nfs' install with the CD mounted on one of the other machines.
-or-
If you can boot any OS to the IDE/SCSI machine, copy the CD contents
(cp -R /cdrom/slakware/* /existing-partition     (syntax?))
and then use boot & root diskettes.
-or-
Move the IDE-HD into one of the other machines and copy the
CD contents to it.

dd if=/cdrom/slakware/bootdsks.144/scsi.s of=/dev/fd0 bs=8192
 (to attempt a scsi-device install,
  (but will your IDE-HD be recognized?))

dd if=/cdrom/slakware/bootdsks.144/bare.i of=/dev/fd0 bs=8192
 (to attempt a boot-from-floppy; install from IDE-HD to IDE-HD
  or 'nfs' install to IDE-HD)

dd if=/cdrom/slakware/rootdsks/color.gz of=/dev/fd0 bs=8192

 Well, this has worked with slackware <= v8.0.  I hope it
will work for => v8.1

HTH, Chuck

> IDE HD and IDE CD, booting the CD nicely and installing from the CD,
> with the BIOS set properly..
> 
> However; the subject machine has an IDE 20gB HD and a __SCSI CD__,
> with a BusLogic SCSI card, creating an insurmountable problem - so
> far - and maybe forever. <grin> (The card and drive working
> flawlessly with the other partitions.)
> 
> The drive has 4 Linux partitions; two working with Slack8.0 and one
> swap of course.. Previous versions of Slackware utilized two boot
> floppies; one booting the selected image and the 2nd with a "root"
> file.. No problem.. Worked fine for years..
> 
> 8.1 is different and the boot from CD works except as above, but
> there is a file 'makedisk' that is supposed to circumvent the non CD
> problem.. Invoking makedisk, as instructed, with the proper bzImage
> entered, in my case scsi.s should work with both an IDE drive and a
> BusLogic card, reports much on the screen but does NOT make a boot
> floppy.. I tried several other images to no avail.. I tried both cat
> and dd transferring the images to /dev/fd0, but apparently a standard
> 1.44 floppy isn't big enough. I tried formatting the floppies at both
> 1.68mB and 1.7X, but no joy as far as booting the floppy.. Apparently
> bzImage alone is not enough to get things going.
> 
> The excellent slackware-HOWTO details perfectly an install as long as
> you have an IDE HD _and_ CD.. No other README's shed any light..
> 
> As of now I've concluded the only _easy_ way out is to termporarily
> fit an IDE CD for the install and then re-fit the SCSI CD.. What do
> YOU think??? Appreciate!!
> 
>     Hal - in Terra Alta, WV - Slackware GNU/Linux 8.0   (2.4.18)
>                 Proprietary  Formats  Unacceptable
> .
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[James Miller]

On Thu, 29 May 2003, pa3gcu wrote:
> >
> > As of now I've concluded the only _easy_ way out is to termporarily
> > fit an IDE CD for the install and then re-fit the SCSI CD.. What do
> > YOU think??? Appreciate!!
>
> There could be another way;
> I have installed slackware 9 on a couple of machines using old slack 8.0 boot
> floppys.
> Simply try and boot with slack's 8.0 scsi.s and color.gz and then after
> booting place the slack 8.1 cdrom in the drive.
> Of course this may not work for you but it has worked for me on several
> occations.
>
Seems like this should work.  Isn't Slack the distro that asks you which
kernel image you want to install at the very end of the install process?

James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[Chuck Gelm]

James Miller wrote:
<snip>
> Seems like this should work.  Isn't Slack the distro that asks you which
> kernel image you want to install at the very end of the install process?

 Uh, huh.  But I have always simply used the boot floppy and then 
compiled my own kernel later.  :-|

Chuck

> 
> James
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[Hal MacArgle]

On 05-29, James Miller wrote:
> On Thu, 29 May 2003, pa3gcu wrote:
> > >
> > > As of now I've concluded the only _easy_ way out is to termporarily
> > > fit an IDE CD for the install and then re-fit the SCSI CD.. What do
> > > YOU think??? Appreciate!!
> >
> > There could be another way;
> > I have installed slackware 9 on a couple of machines using old slack 8.0 boot
> > floppys.
> > Simply try and boot with slack's 8.0 scsi.s and color.gz and then after
> > booting place the slack 8.1 cdrom in the drive.
> > Of course this may not work for you but it has worked for me on several
> > occations.
> >
> Seems like this should work.  Isn't Slack the distro that asks you which
> kernel image you want to install at the very end of the install process?
> 
> James

		Greetings: Negative - the kernel image you select is
on the boot floppy, Slack =<8.0, plus a "root" floppy to get into the
install screens.. It was all changed with 8.1 in that the image is
loaded via 'syslinux' from the bootable CD.. I'm still bogged down
with this - more later for Richard and Chuck..

    Hal - in Terra Alta, WV - Slackware GNU/Linux 8.0   (2.4.18)
                Proprietary  Formats  Unacceptable
.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[Chuck Gelm]

ftp://ftp.slackware.com/pub/slackware/slackware-8.1/

 Hi, Hal:

 I downloaded slackware-9.0-install.iso and burned a CD.
The resultant CD boots on two of three computers that I
tried it on.  I suggest going to the above URL and downloading
the iso image.  Here is a mirror that seems close to me:

ftp://ftp.cerias.purdue.edu/pub/os/slackware/slackware-8.1-iso/

 Sometimes I get all the domain names from:
http://www.slackware.com/getslack/
 then ping them to see which is fastest.  Then I
get the file(s) from the fastest one.  ;-)

To date, I have purchased one CD set from Slackware and
one from CheapBytes. I currently use Slackware v8.0 with
kernels 2.2.19, 2.2.25, 2.4.19, 2.4.20 on various computers.

 Can you mount and read the bootable CD with your current
slackware v8.0 computer?  I still think you can copy a boot
image to one of your existing partitions and boot it
with one floppy or even your existing boot loader.

 If you can mount your 'bootable' install CD under 8.0,
copy the base directory and the /slakware directory to
an existing partition.  Then when you select your install
media, use this hard drive partition.

HTH, Chuck
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[pa3gcu]

On Tuesday 03 June 2003 22:44, Hal MacArgle wrote:
> Greetings again Richard and I've found something that I'm hoping is
> --IT--....

Firstly, i cant remember if we started this as a personal matter, however i 
have CC'ed this to the linux-newbie list, i saw some other mails with the 
same header so i am sure i am doing the correct thing.

>
> My mind is like Jello after an afternoon with this so forgive me if I
> say something really stupid:
>
> I bought another IDE drive and fitted it to yet another machine..
> Using Slack 8.0, 2.4.5 bare.i bootdisk and color.gz all seemed well
> as the CD was found; partitions setup, etc.. Selected "a" only, menu
> mode and then got the dreaded screen again "Your source device cannot
> be accessed properly."
>
> This time however I RTFM the rest of what it said. Dumbo me, before.
> It said to be sure the Slackware distribution  is mounted on
> /var/log/mount/slakware... Of course the drive was mounted properly
> BUT the CD I have has the packages in the directory slackware. After

Something wrong here, my slackware-8.1 cdrom obtained from a mirror site of 
slackware.com so its a slackware disk period.

I booted my machine a 650Mhz PIII machine with slack 8.0 bare.i and color.gz 
disks, please NOTE, slack 8.0 boot disks.
After doing the normal thing, fdisk(ing) typing 'setup' i get the dialog 
install program just like one expects.

I can then add swap, choose a partition to install on and let setup 
'automaticly' mount my cdrom located on /dev/hdc.
It gets mounted in /var/log/mount "thats it" no slackware directory to be 
seen, AFAIK its always been that way.

> all these years Patrick has decided to change the "normal" directory?
> /Or/ perhaps when the distribution was made this happened somewhere
> along the line. Dunno..

Not as far as i know he has'nt. At least not as far as 8.1, however i cant 
comment on slack 9 as i did not install from an iso image i installed from 
HD, i simply ftp'ed the directory's a thro' y .

>
> I, actually, noted this all along but never gave it a 2nd thought..
>
> The problem now is: How in the hell can I go round this??

What i ask is the following, if you mount the CD on another running linux 
machine, what is the dir structrue after the mount point, you should see;
"slackware" period, in otherwords if you mount the cdrom under /mnt you should 
see;
/mnt/(a lot of files and directorys) and one called slackware contianing dir's
a, ap, d, e, so on and so forth.

Another quiestion is what happens if you give a path to "setup" and mount the 
cdrom manually. ??

>
> Not having the actual CD I have in my possession no one could have
> possibly known about this except ME...
>
> Do I have to copy all the files from that CD directory to the HD in
> the 'slakware' directory and then install from there?? Maybe this is
> what you were talking about before.. I'm getting too old methinks.
> At least I'm sure learning more and more.
 You certainly can do that yes, there is only the need for the contens of the 
slackware directory to be copied to the HD no need for all the help readm's 
and so on in the topdir of the cdrom.

If all esle fails i could even send you a copy of my cdrom per POST, but i 
dont really think that is nessasary at all, i have a small inclination you 
are doing something fundementally wrong.

> Tomorrows another day, eh? Vy 73,
>
>     Hal - in Terra Alta, WV - Slackware GNU/Linux 8.0   (2.4.18)
>                 Proprietary  Formats  Unacceptable
> .

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[Hal MacArgle]

On 06-04, pa3gcu wrote:
> 
> Something wrong here, my slackware-8.1 cdrom obtained from a mirror site of 
> slackware.com so its a slackware disk period.
> 
> I booted my machine a 650Mhz PIII machine with slack 8.0 bare.i and color.gz 
> disks, please NOTE, slack 8.0 boot disks.
> After doing the normal thing, fdisk(ing) typing 'setup' i get the dialog 
> install program just like one expects.
> 
> I can then add swap, choose a partition to install on and let setup 
> 'automaticly' mount my cdrom located on /dev/hdc.
> It gets mounted in /var/log/mount "thats it" no slackware directory to be 
> seen, AFAIK its always been that way.

	OK - that's _exactly_ what I've been doing on two machines,
one with an IDE CD the other with a SCSI CD.. Both report it can't
read the CD.. Mounting the same CD on either machine I can read it
perfectly.. I'm presuming the bare.i you used is from the 2.4.5
directory, although I've tried both that one plus the one in the
2.2.19 directory, same problem.. The problem follows the physical CD
even though it does install from a machine with an IDE CD drive,
booting from the same CD..



> What i ask is the following, if you mount the CD on another running linux 
> machine, what is the dir structrue after the mount point, you should see;
> "slackware" period, in otherwords if you mount the cdrom under /mnt you should 
> see;
> /mnt/(a lot of files and directorys) and one called slackware contianing dir's
> a, ap, d, e, so on and so forth.

	I can mount the CD on _any_ of my machines - cd to the
slackware directory and view, copy, do anything I want with all the
'letter' directories.. Everything 'normal' there..
 


> Another quiestion is what happens if you give a path to "setup" and mount the 
> cdrom manually. ??

	I've tried that but, previously, during the setup routine
I've checked each time and the cd drive is mounted properly on
/var/log/mount, as it should be - but down the line it still can't
see the slackware directory. Moving all those files to the HD in a
/slakware directory - same thing..



> If all esle fails i could even send you a copy of my cdrom per POST, but i 
> dont really think that is nessasary at all, i have a small inclination you 
> are doing something fundementally wrong.

	That's for sure, but I've pestered you and Chuck entirely too
much with this and I'm sure the List is bored to tears.. As of now I
_can_ install Slack8.1 with an IDE CD, bootable, machine, and that's
IT.. Since I read the big box vendors are starting to eliminate the
floppies from their boxes - maybe that's the only way to go in the
future, eh? HI.. I'm a stubborn tenacious Scot but there has to be
closure somewhere along the line.. Life's too short... <grin>

	APPRECIATE!!!

    Hal - in Terra Alta, WV - Slackware GNU/Linux 8.0   (2.4.18)
                Proprietary  Formats  Unacceptable
.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[pa3gcu]

On Thursday 05 June 2003 15:30, Hal MacArgle wrote:
> On 06-04, pa3gcu wrote:
> > Something wrong here, my slackware-8.1 cdrom obtained from a mirror site
> > of slackware.com so its a slackware disk period.
> >
> > I booted my machine a 650Mhz PIII machine with slack 8.0 bare.i and
> > color.gz disks, please NOTE, slack 8.0 boot disks.
> > After doing the normal thing, fdisk(ing) typing 'setup' i get the dialog
> > install program just like one expects.
> >
> > I can then add swap, choose a partition to install on and let setup
> > 'automaticly' mount my cdrom located on /dev/hdc.
> > It gets mounted in /var/log/mount "thats it" no slackware directory to be
> > seen, AFAIK its always been that way.
>
> 	OK - that's _exactly_ what I've been doing on two machines,
> one with an IDE CD the other with a SCSI CD.. Both report it can't
> read the CD.. Mounting the same CD on either machine I can read it
> perfectly.. I'm presuming the bare.i you used is from the 2.4.5
> directory, although I've tried both that one plus the one in the
> 2.2.19 directory, same problem.. The problem follows the physical CD
> even though it does install from a machine with an IDE CD drive,
> booting from the same CD..

I used 2.2.19 and i have used 2.4.5 as well.
I found no difference with my hardware in dectection or install.

> > What i ask is the following, if you mount the CD on another running linux
> > machine, what is the dir structrue after the mount point, you should see;
> > "slackware" period, in otherwords if you mount the cdrom under /mnt you
> > should see;
> > /mnt/(a lot of files and directorys) and one called slackware contianing
> > dir's a, ap, d, e, so on and so forth.
>
> 	I can mount the CD on _any_ of my machines - cd to the
> slackware directory and view, copy, do anything I want with all the
> 'letter' directories.. Everything 'normal' there..
>
> > Another quiestion is what happens if you give a path to "setup" and mount
> > the cdrom manually. ??
>
> 	I've tried that but, previously, during the setup routine
> I've checked each time and the cd drive is mounted properly on
> /var/log/mount, as it should be - but down the line it still can't
> see the slackware directory. Moving all those files to the HD in a
> /slakware directory - same thing..

So it sounds like you can mount the CD manually during install, is that 
correct,?? If so then you MUST be able to use it to install period, what you 
may be doing is FORGETTING to ""UNMOUNT"" it before proceeding with the 
install, i say that be cause i can get the same error message you mention if 
i mount the cdrom by hand in a console and then proceed with "setup" to 
install slackware, it does not then work, one needs to UNMOUNT the cdrom 
first....

Is that your problem.?????

>
> > If all esle fails i could even send you a copy of my cdrom per POST, but
> > i dont really think that is nessasary at all, i have a small inclination
> > you are doing something fundementally wrong.
>
> 	That's for sure, but I've pestered you and Chuck entirely too
> much with this and I'm sure the List is bored to tears.. As of now I
> _can_ install Slack8.1 with an IDE CD, bootable, machine, and that's
> IT.. Since I read the big box vendors are starting to eliminate the
> floppies from their boxes - maybe that's the only way to go in the
> future, eh? HI.. I'm a stubborn tenacious Scot but there has to be
> closure somewhere along the line.. Life's too short... <grin>

Get on a plane, travel to EU is much easier than Europeens traveling to the 
USA theresdays, our rules and regulations on travel seem to vary a lot, i 
will install it for you.

>
> 	APPRECIATE!!!

No problem, been there done that and am willing to keep on doing that.

>
>     Hal - in Terra Alta, WV - Slackware GNU/Linux 8.0   (2.4.18)
>                 Proprietary  Formats  Unacceptable

O i am thinking of making the following my sig...

"If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime."

Comments.??

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[Hal MacArgle]

On 06-05, pa3gcu wrote:
> 
> So it sounds like you can mount the CD manually during install, is that 
> correct,?? If so then you MUST be able to use it to install period, what you 
> may be doing is FORGETTING to ""UNMOUNT"" it before proceeding with the 
> install, i say that be cause i can get the same error message you mention if 
> i mount the cdrom by hand in a console and then proceed with "setup" to 
> install slackware, it does not then work, one needs to UNMOUNT the cdrom 
> first....
> 
> Is that your problem.?????

	Not sure I understand the above completely.. Slackware has a
source selection including sth like "Install from a mounted
directory." I tried that by creating an empty directory, /slack, and
then mounting the CD drive.. So that means, to me, that setup should
find the files at /slack/slackware.. I tried all combinations to no
avail, including trailing "/"s...



> Get on a plane, travel to EU is much easier than Europeens traveling to the 
> USA theresdays, our rules and regulations on travel seem to vary a lot, i 
> will install it for you.

	Boy wouldn't that be overkill?? I guess Americans are good at
that so maybe it's not too far fetched.. I don't do aeroplanes
anymore.. <grin>



> O i am thinking of making the following my sig...
> 
> "If the Linux community is a bunch of theives because they
> try to imitate windows programs, then the Windows community
> is built on organized crime."
> 
> Comments.??

	Well - sounds good to me except I would say MSWindows because
we have our XWindows. With M$ and AOL now joining up together we had
better hunker down for the long run.. At least it's interesting, eh?
Vy 73,

    Hal - in Terra Alta, WV - Slackware GNU/Linux 8.0   (2.4.18)
                Proprietary  Formats  Unacceptable
.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[Amin]

On Sat, 7 Jun 2003 10:47:27 -0400, Hal MacArgle wrote:
> we have our XWindows. With M$ and AOL now joining up together we had

Tut tut.  People are touchy about the whole ``X-Windows'' thing, you
know.  The proper naming scheme's one of the first things you get to
read on the X(7x) man page.  Of course, it wouldn't be very accurate to 
say that X is only for Unix variants --- after all, people do run it in 
MS Windows, through Cygwin.

MS and AOL merging?  Sounds a little far-fetched ... .

My $0.02,
Yawar Amin
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: AOL and MS.

[Hal MacArgle]

On 06-07, Amin wrote:
> 
> MS and AOL merging?  Sounds a little far-fetched ... .
> 
> My $0.02,
> Yawar Amin

	Your comments noted but it's not "merging" just "joining" for
some mutual shenanigans methinks..

	Check out Newsweek,  09 June 2003 issue, page 38 by Steven
Levy - "Two Gorillas Make Nice." My comment about them, possibly,
going after Linux was gleaned from an eMail message I happened to
view. 

	I found part of the message but this is OT, so nuff said,
although it does and will affect Linux users in the future..

    Hal - in Terra Alta, WV - Slackware GNU/Linux 8.0   (2.4.18)
                Proprietary  Formats  Unacceptable
.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

crontab syntax ?

[Chuck Gelm]

Howdy, y'all:

 I want to run a script monthly.
(update my dynamic DNS account)
I (as 'root') ran 'crontab -e' and added this line:

5 6 7 * date /usr/local/src/ez/dyndns.conf >> /share/dyndnsup.txt 2>>
/share/dyndnsup.txt

This seems to be the syntax indicated by 'man crontab'.
If I understand the syntax of crontab, the above line will 
every 7th of the month, at 06:05, execute my dyndns.conf file
and send standard and error messages to file /share/dyndnsup.txt.

 Is this correct syntax?
 Is there a syntax checker for crontab like testparm for samba?

Regards, Chuck
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: crontab syntax ?

[Ray Olszewski]

At 03:50 PM 6/7/2003 -0400, Chuck Gelm wrote:
>Howdy, y'all:
>
>  I want to run a script monthly.
>(update my dynamic DNS account)
>I (as 'root') ran 'crontab -e' and added this line:
>
>5 6 7 * date /usr/local/src/ez/dyndns.conf >> /share/dyndnsup.txt 2>>
>/share/dyndnsup.txt
>
>This seems to be the syntax indicated by 'man crontab'.
>If I understand the syntax of crontab, the above line will
>every 7th of the month, at 06:05, execute my dyndns.conf file
>and send standard and error messages to file /share/dyndnsup.txt.
>
>  Is this correct syntax?

Probably. I'm not familiar with the use of "date" as the fifth field (for 
day of the week), and I can't find it listed as an option in my man page, 
so I am not sure about that piece. I would write this entry ...

5 6 7 *  *      /usr/local/src/ez/dyndns.conf >> /share/dyndnsup.txt 2>> 
/share/dyndnsup.txt.

... with the last * indicating any day of the week.

>  Is there a syntax checker for crontab like testparm for samba?

crontab itself will inform you if any of the 5 time fields has an invalid 
entry, whenever you exit your editor (and it displays the "installing new 
crontab" message). crontab has no way fo knowing if the entry for what to 
run is valid or not.



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: crontab syntax ?

[Chuck Gelm]

Thanks, Ray:

Odd, here is a segment of (*my*) 'man crontab' showing
the example lines. Every example has 'date' as the 6th field. :-|
(*my* = slackware-8.0, kernel-2.2.19, firewall, ip-masq)
Maybe the examples show how to run the 'date' program?

# MIN HOUR DAY MONTH DAYOFWEEK   COMMAND
# at 6:10 a.m. every day
10 6 * * * date

# every two hours at the top of the hour
0 */2 * * * date

# every two hours from 11p.m. to 7a.m., and at 8a.m.
0 23-7/2,8 * * * date

# at 11:00 a.m. on the 4th and on every mon, tue, wed
0 11 4 * mon-wed date

# 4:00 a.m. on january 1st
0 4 1 jan * date

# once an hour, all output appended to log file
0 4 1 jan * date >>/var/log/messages 2>&1

Ray Olszewski wrote:
> 
> At 03:50 PM 6/7/2003 -0400, Chuck Gelm wrote:
> >Howdy, y'all:
> >
> >  I want to run a script monthly.
> >(update my dynamic DNS account)
> >I (as 'root') ran 'crontab -e' and added this line:
> >
> >5 6 7 * date /usr/local/src/ez/dyndns.conf >> /share/dyndnsup.txt 2>>
> >/share/dyndnsup.txt
> >
> >This seems to be the syntax indicated by 'man crontab'.
> >If I understand the syntax of crontab, the above line will
> >every 7th of the month, at 06:05, execute my dyndns.conf file
> >and send standard and error messages to file /share/dyndnsup.txt.
> >
> >  Is this correct syntax?
> 
> Probably. I'm not familiar with the use of "date" as the fifth field (for
> day of the week), and I can't find it listed as an option in my man page,
> so I am not sure about that piece. I would write this entry ...
> 
> 5 6 7 *  *      /usr/local/src/ez/dyndns.conf >> /share/dyndnsup.txt 2>>
> /share/dyndnsup.txt.
> 
> ... with the last * indicating any day of the week.
> 
> >  Is there a syntax checker for crontab like testparm for samba?
> 
> crontab itself will inform you if any of the 5 time fields has an invalid
> entry, whenever you exit your editor (and it displays the "installing new
> crontab" message). crontab has no way fo knowing if the entry for what to
> run is valid or not.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: crontab syntax ?

[Ray Olszewski]

At 06:23 PM 6/7/2003 -0400, Chuck Gelm wrote:
>Thanks, Ray:
>
>Odd, here is a segment of (*my*) 'man crontab' showing
>the example lines. Every example has 'date' as the 6th field. :-|

Yes. But the proposed entry you asked us about originally --

         5 6 7 * date /usr/local/src/ez/dyndns.conf

-- had "date" as the fifth field, NOT the sixth field. That is wrong. You 
can't just skip a field; you need (in this case) the * entry for it.

"date" is a standard Unix/Linux command, and the samples you referred to, 
which have it in the sixth field, simply use it as the name of the program 
to run ... just as you suspected.

>(*my* = slackware-8.0, kernel-2.2.19, firewall, ip-masq)
>Maybe the examples show how to run the 'date' program?
>
># MIN HOUR DAY MONTH DAYOFWEEK   COMMAND
># at 6:10 a.m. every day
>10 6 * * * date
[rest deleted]




-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: crontab syntax ?

[jdr]

On 7 Jun 2003 at 18:23, Chuck Gelm wrote:

> Thanks, Ray:
> 
> Odd, here is a segment of (*my*) 'man crontab' showing
> the example lines. Every example has 'date' as the 6th field. :-|
> (*my* = slackware-8.0, kernel-2.2.19, firewall, ip-masq)
> Maybe the examples show how to run the 'date' program?
> 
> # MIN HOUR DAY MONTH DAYOFWEEK   COMMAND
> # at 6:10 a.m. every day
> 10 6 * * * date
> 

<snip>

Yeah, it's showing you how to run 'date' at various times and
intervals.

Here's a bit of what Red Hat's "man 5 crontab" says (for what it's worth):

The time and date fields are:

       field          allowed values
       -----          --------------
       minute         0-59
       hour           0-23
       day of month   1-31
       month          1-12 (or names, see below)
       day of week    0-7 (0 or 7 is Sun, or use names)


-jdr-
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[pa3gcu]

On Saturday 07 June 2003 16:47, Hal MacArgle wrote:
> On 06-05, pa3gcu wrote:
> > So it sounds like you can mount the CD manually during install, is that
> > correct,?? If so then you MUST be able to use it to install period, what
> > you may be doing is FORGETTING to ""UNMOUNT"" it before proceeding with
> > the install, i say that be cause i can get the same error message you
> > mention if i mount the cdrom by hand in a console and then proceed with
> > "setup" to install slackware, it does not then work, one needs to UNMOUNT
> > the cdrom first....
> >
> > Is that your problem.?????
>
> 	Not sure I understand the above completely.. Slackware has a
> source selection including sth like "Install from a mounted
> directory." I tried that by creating an empty directory, /slack, and
> then mounting the CD drive.. So that means, to me, that setup should
> find the files at /slack/slackware.. I tried all combinations to no
> avail, including trailing "/"s...

Yes it does allow what you say however it will NOT work as you think or want 
it to for the following reason.

You mount your cdrom in /slack which you created, your cdrom has a directory 
called slackware containing the install sets, a, ap, etc etc etc.
However the setup program does NOT look in slackware, it looks in slack and 
will not find the install sets. I burnt a cdrom with the contents of the 
slackware directory in the root of the cdrom, however this did not work 
either.

One possable reason for it not working is that you are not mounting a 
predefined "directory" you mount another "device" in that directory, my cdrom 
led does not even flikker at all when setup looks for the "a" series 
indicating that it does not find the cdrom mounted in the given directory at 
all.

So as far as i see it, simply let slack detect the cdrom from the setup 
process, do not mount the cdrom beforehand. If it does not find it you may 
need to define where setup must look for it.

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[Chuck Gelm]

Hal:

 I've created slackware-8.1-iso & slackware-9.0-iso CDROMs.
I have exhausted attempts to use them as install media
while booting from a single floppy.

 There ought to be a way to copy files from the CDROM to
an existing hard drive partition (root file system). Then
using a single boot floppy (selecting one that matches
your scsi devices) to start an install.  However, it is
beyond my knowledge.

I am baffled.

Regards, Chuck
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[pa3gcu]

On Monday 09 June 2003 11:59, Chuck Gelm wrote:
> Hal:
>
>  I've created slackware-8.1-iso & slackware-9.0-iso CDROMs.
> I have exhausted attempts to use them as install media
> while booting from a single floppy.

The idea that has been adopted by Slack for booting from a cdrom is very easy 
and AFAIK is going to be keep that way.
Are you saying that your cdrom does not boot the system and/or not find your 
hardware properly.??

The idea is that you place the slack-9.0 disk in the cdrom drive and start the 
system, at the "boot": prompt you type the kernel name of your choise.

Example;

boot: scsi.s

Read the file Slackware-HOWTO in the root of the cdrom paragraph 3.2 to see 
which kernel you need.

I have never tryed to use just one bootdisk, 2 is then minimum i have ever 
used. I have explained howto boot and install 9.0 with slackware-8.0 
floppy's, that how i started my install for slack 9.

>  There ought to be a way to copy files from the CDROM to
> an existing hard drive partition (root file system). Then
> using a single boot floppy (selecting one that matches
> your scsi devices) to start an install.  However, it is
> beyond my knowledge.

One floppy no, 2 maybe.

You can always download the packages needed and place them on your HD.

> I am baffled.

Its all quite easy really.

>
> Regards, Chuck

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[Chuck Gelm]

Hi, Richard:

 I have two computers that (can not|will not) boot from CDROM drive.
Hal had a similar setup wherein one of his computers would not boot
from its SCSI CDROM (or would not boot some odd release of
Slackware-8.1.1 from its SCSI CDROM drive).  So I was trying to find
a way to copy files from an install .iso CDROM disk to hard disk
partition where I could boot from 'scsi.s' boot disk and then
tell the prompt
 boot: mount root=/dev/hdb1
where /dev/hdb1 would be a partition where the install CDROM 
files were.  Then after logging in as 'root', 'setup' could
be run to start a new installation.

 On the CDROM is /isolinux/initrd.img which I was thinking was a
'root' filesystem. ?  Couldn't this file (and others?) be copied
to an existing hard disk partition and then booted?

 Could the entire CDROM be copied to /dev/hdb1 and then use
fdisk to set /dev/hdb1 as the active partition and then reboot?

 There ought to be a way to 'upgrade' to Slackware-8.1 or -9.0
on a system with no bootable CDROM device.  There is a
/slackware/
directory that can be copied, but where is the 'setup' application?

:-| Chuck

pa3gcu wrote:
> 
> On Monday 09 June 2003 11:59, Chuck Gelm wrote:
> > Hal:
> >
> >  I've created slackware-8.1-iso & slackware-9.0-iso CDROMs.
> > I have exhausted attempts to use them as install media
> > while booting from a single floppy.
> 
> The idea that has been adopted by Slack for booting from a cdrom is very easy
> and AFAIK is going to be keep that way.
> Are you saying that your cdrom does not boot the system and/or not find your
> hardware properly.??

 Yes.

 I have used the bootdisk & rootdisk method many times and
have done a 'nfs' install a few times too.  The -8.1 & -9.0
releases require a bootdisk & 5 rootdisks if the computer
cannot boot from CDROM.

-- more later --
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[Chuck Gelm]

I just booted the slackware-9.0-iso on a rather old
Compaq Deskpro 2000 (pentium 120 MHz with f00f bug),
did a 'dmesg|head' and found this:

Kernel command line:
BOOT_IMAGE=/kernels/bare.i/bzImage initrd=initrd.img load_ramdisk=1 \
prompt_ramdisk=0 ramdisk_size=6464 rw root=/dev/ram SLACK_KERNEL=bare.i

 So, somehow, when the system boots from CDROM, its pwd=/isolinux/
because there is no path in 'initrd=initrd.img', but there is a path
in 'BOOT_IMAGE=/kernels/bare.i/bzImage'.

 Is there a way to copy the CDROM's root filesystem to /dev/hdb1
and alter the default 'scsi.s' bootdisk so that it loads the root
image from /dev/hdb1?    rdev?

 Can the boot files be copied to /dev/hdb1 and the 'scsi.s'
bootdisk be altered to boot /dev/hdb1/kernels/scsi.s/bzImage
and the root /dev/hdb1/isolinux/initrd.img?

 Then the CDROM and be mounted on the SCSI CDROM drive and
the install begun. 

 Heck, why not copy /isolinux/*, /kernels/scsi.s/*, & /slackware/*
to /dev/hdb1?

Wondering... Chuck


pa3gcu wrote:
> 
> On Monday 09 June 2003 11:59, Chuck Gelm wrote:
> > Hal:
> >
> >  I've created slackware-8.1-iso & slackware-9.0-iso CDROMs.
> > I have exhausted attempts to use them as install media
> > while booting from a single floppy.
> 
> The idea that has been adopted by Slack for booting from a cdrom is very easy
> and AFAIK is going to be keep that way.
> Are you saying that your cdrom does not boot the system and/or not find your
> hardware properly.??
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[Chuck Gelm]

Hi, Steven

qwms-avib@dea.spamcon.org wrote:
> 
> Chuck Gelm wrote:
> >
> > I've created slackware-8.1-iso & slackware-9.0-iso CDROMs.
> > I have exhausted attempts to use them as install media
> > while booting from a single floppy.
<snip>
> Now you are getting close to a solution.  You take the kernel
> from the CDrom (bzImage) and the image of the installation
> filesystem (initrd.img) and boot them (from DOS) using loadlin.exe:
> ---------------------------------------------------------------
> loadlin d:\kernels\scsi.s\bzImage initrd=d:\isolinux\initrd.img
> ---------------------------------------------------------------
 
 Provided that your boot floppy's o/s can recognize the CDROM drive.
;-)

 Thanks, Steven, this should work for me.

 Hal:  Does your reluctant system, if booted from a DOS diskette,
have its SCSI CDROM drive recognized?

Regards, Chuck

> I've just executed that line (on a nearby system) and it is now
> running the installation routine.  Note:  you may need to change
> the d: to a different letter (depending on what letter was assigned
> by DOS to your CDrom).
> 
> > Is there a way to copy the CDROM's root filesystem to /dev/hdb1
> > and alter the default 'scsi.s' bootdisk so that it loads the root
> > image from /dev/hdb1?    rdev?
> 
> Yes, but it should not be necessary.  Just try loadlin.exe
> (get it from the loadlin zip file in the /kernels directory
> of the CDrom).

 The installation runs much faster from hard drive.  ;-)

> Cheers,
> Steven
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[Hal MacArgle]

Greetings: Delay taking time out to visit the hospital taking me away
from this more interesting stuff. <grin> Comments below at request:
Hal

On 06-10, Chuck Gelm wrote:
> Hi, Steven
> 
> qwms-avib@dea.spamcon.org wrote:
> > 
> > Chuck Gelm wrote:
> > >
> > > I've created slackware-8.1-iso & slackware-9.0-iso CDROMs.
> > > I have exhausted attempts to use them as install media
> > > while booting from a single floppy.
> <snip>
> > Now you are getting close to a solution.  You take the kernel
> > from the CDrom (bzImage) and the image of the installation
> > filesystem (initrd.img) and boot them (from DOS) using loadlin.exe:
> > ---------------------------------------------------------------
> > loadlin d:\kernels\scsi.s\bzImage initrd=d:\isolinux\initrd.img
> > ---------------------------------------------------------------
>  
>  Provided that your boot floppy's o/s can recognize the CDROM drive.
> ;-)
> 
>  Thanks, Steven, this should work for me.
> 
>  Hal:  Does your reluctant system, if booted from a DOS diskette,
> have its SCSI CDROM drive recognized?
> 
> Regards, Chuck

	First off, to make matters worse, I note that my distribution
disk does NOT have the /rootdisks directory so that's _one_ reason
I've been in the dark so much.. The other, seemingly, big problem is
that the "reluctant" system has an IDE HD but both CD's are SCSI,
driven by a BusLogic controller.. There is, also, a SCSI scanner, but
I've disconnected it during this mess, and a ZIP250..

	Re above; booting from a DRDos702 floppy the BIOS sees the
BusLogic controller OK but doesn't, automatically, assign a drive
letter to either CD.. The IDE HD on this machine does NOT have a Dos
partition, only 3 Linux native and 1 swap, so I'm shot down with
Stevens' instructions as the two images wont fit on a floppy.. Maybe
I'm missing something here - my mind has turned to Jello. :^)... I
have the Dos drivers for Atapi drives and the required mscdex, or
equivalent, but that's no use with a SCSI drive.. I've got to
research this somemore..

	Trying to boot from the SlackCD with the disk in either of
the SCSI drives and the BIOS set to Boot: SCSI, A, C, it doesn't see
either and goes right into the normal LILO boot of /hda3.. I'm
guessing that the autoboot routine on the CD only works when you set
the BIOS to: CDROM,,,, and the drive is ATAPI-IDE.. So, bottom line,
is that the CD distribution I have installs OK on a pure ATAPI-IDE
machine - which I have already done on another machine.

	Richard has installed using the boot/root combination from
Slack8.0, but I can't seem to get it working so far.. He's, kindly,
trying to solve that problem..

	It's rather obvious, that the ./makedisk <filename>
<kernel.img> routine in the distribution doesn't work, even tho I've
tried formatting a floppy to 1720K and 1680K, which the routine is
supposed to do automatically.. Searching google/linux; "makedisk
slackware 8.1" brought several horror stories.. ./makedisk creates a
file in /tmp/xxxx.img - but what to do with that?? Load it with
loadlin? I still have so much to learn..

	To me the most unfortunate thing about this is: How can I,
with a straight face, recommend the neighbours switch to Linux??

	Sorry this is so long..

Hal

> 
> > I've just executed that line (on a nearby system) and it is now
> > running the installation routine.  Note:  you may need to change
> > the d: to a different letter (depending on what letter was assigned
> > by DOS to your CDrom).
> > 
> > > Is there a way to copy the CDROM's root filesystem to /dev/hdb1
> > > and alter the default 'scsi.s' bootdisk so that it loads the root
> > > image from /dev/hdb1?    rdev?
> > 
> > Yes, but it should not be necessary.  Just try loadlin.exe
> > (get it from the loadlin zip file in the /kernels directory
> > of the CDrom).
> 
>  The installation runs much faster from hard drive.  ;-)
> 
> > Cheers,
> > Steven
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[Hal MacArgle]

On 06-08, pa3gcu wrote:
> On Saturday 07 June 2003 16:47, Hal MacArgle wrote:
> > On 06-05, pa3gcu wrote:
> > > So it sounds like you can mount the CD manually during install, is that
> > > correct,?? If so then you MUST be able to use it to install period, what
> > > you may be doing is FORGETTING to ""UNMOUNT"" it before proceeding with
> > > the install, i say that be cause i can get the same error message you
> > > mention if i mount the cdrom by hand in a console and then proceed with
> > > "setup" to install slackware, it does not then work, one needs to UNMOUNT
> > > the cdrom first....
> > >
> > > Is that your problem.?????
> >
> > 	Not sure I understand the above completely.. Slackware has a
> > source selection including sth like "Install from a mounted
> > directory." I tried that by creating an empty directory, /slack, and
> > then mounting the CD drive.. So that means, to me, that setup should
> > find the files at /slack/slackware.. I tried all combinations to no
> > avail, including trailing "/"s...
> 
> Yes it does allow what you say however it will NOT work as you think or want 
> it to for the following reason.
> 
> You mount your cdrom in /slack which you created, your cdrom has a directory 
> called slackware containing the install sets, a, ap, etc etc etc.
> However the setup program does NOT look in slackware, it looks in slack and 
> will not find the install sets. I burnt a cdrom with the contents of the 
> slackware directory in the root of the cdrom, however this did not work 
> either.
> 
> One possable reason for it not working is that you are not mounting a 
> predefined "directory" you mount another "device" in that directory, my cdrom 
> led does not even flikker at all when setup looks for the "a" series 
> indicating that it does not find the cdrom mounted in the given directory at 
> all.
> 
> So as far as i see it, simply let slack detect the cdrom from the setup 
> process, do not mount the cdrom beforehand. If it does not find it you may 
> need to define where setup must look for it.

	OK - I went back to a completly new try using the 8.0
buslogic.s/colour.gz combination:/hda4 as swap and a clean /hda1 as
target. Swap on; quick format; Source Slackware CD-ROM - autoscan
found 2nd scsi cd ok; select 'a' only - report "Installing series
a".. Then the dreaded panel, seen so many times: "MOUNT ERROR -
Please be sure that it is mounted on /var/log/mount/slakware and that
the Slackware disks are found in sub dirs /var/log/mount/slakware
like specified." (Of course on the CD they are in slackware, not
slakware.. With OK I got the # command line again but with several
reports: "/usr/lib/setup/setup: cannot create /mnt/etc fstab:
directory non-existent."

	I checked and /mnt exists but not etc, so I did a mkdir etc
there and went back to setup again.. This time I got the MOUNT ERROR
report again, but not the previous non-existent, and, actually got as
far as making a boot disk, selecting 'make lilo boot disk' but,
noting that the a files were really never installed.. Trying to make
the boot disk fd0 went into netherland and didn't stop running until
I ejected the disk (a no-no to me, normally) Tried whole routine
again making a 'simple' boot disk and it worked but, of course,
reported a Kernel Panic: because there were no files on the drive..

	In summation Richard, notwithstanding all the work you and
others have done with this - Who needs it??? Life is too short..
Apparently 8.1 has more than one messed up directory label, compared
to the previous versions..This version installs OK with an ATAPI-IDE
CD and HD with a BIOS that boots CD's, period.. IMHO. <grin> Since
some vendors are eliminating floppies from their boxes now - I guess
that's the way to go, eh?

APPRECIATE!!

    Hal - in Terra Alta, WV - Slackware GNU/Linux 8.0   (2.4.18)
                Proprietary  Formats  Unacceptable
.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[pa3gcu]

On Tuesday 10 June 2003 02:58, Chuck Gelm wrote:
> Hi, Richard:
>
>  I have two computers that (can not|will not) boot from CDROM drive.
> Hal had a similar setup wherein one of his computers would not boot
> from its SCSI CDROM (or would not boot some odd release of
> Slackware-8.1.1 from its SCSI CDROM drive).  So I was trying to find
> a way to copy files from an install .iso CDROM disk to hard disk
> partition where I could boot from 'scsi.s' boot disk and then
> tell the prompt
>  boot: mount root=/dev/hdb1
> where /dev/hdb1 would be a partition where the install CDROM
> files were.  Then after logging in as 'root', 'setup' could
> be run to start a new installation.

No it does not work like that, to use your boot option you must have "already" 
install the packages.
If you try the above no way will you boot your system.

What you need to do is copy the "slackware" directory to a HD partition, not 
the partition where you intend to install. so you may need two empty 
partitions one for the source and one to install on. The source HD partition 
could be a running older slackware version "providing" you have enough disk 
space, at least 620MB i belive it was when i copied the slack-9.0 slackware 
directory to my HD. This is all exaplained in the "UPGRADE.TXT" file, more 
comments below.

It could also be that you need to pass kernel parms via lilo at the boot 
prompt to get the kernel to recocnise your SCSI cdrom, read section 2 of the 
BOOTING.TXT file both mentioned files should be in the root of the cdrom.

>  On the CDROM is /isolinux/initrd.img which I was thinking was a
> 'root' filesystem. ?  Couldn't this file (and others?) be copied
> to an existing hard disk partition and then booted?
>
>  Could the entire CDROM be copied to /dev/hdb1 and then use
> fdisk to set /dev/hdb1 as the active partition and then reboot?

No need only the slackware dir needs to be copied, more comments below.

>
>  There ought to be a way to 'upgrade' to Slackware-8.1 or -9.0
> on a system with no bootable CDROM device.  There is a
> /slackware/
> directory that can be copied, but where is the 'setup' application?

O but there is, read the file called UPGRADE.TXT, again it should be in the 
root of the cdrom. It also explains what you need to copy from the cdrom to 
your HD and most important, HOWTO do it.

If i may make a comment without seeming pompous, i am quite sure you have not 
read the nessacary documents, documents which are mentioned here in this mail 
are "unmissable" for your problem.

>
> :-| Chuck

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[pa3gcu]

On Tuesday 10 June 2003 03:32, Chuck Gelm wrote:
> I just booted the slackware-9.0-iso on a rather old
> Compaq Deskpro 2000 (pentium 120 MHz with f00f bug),
> did a 'dmesg|head' and found this:
>
> Kernel command line:
> BOOT_IMAGE=/kernels/bare.i/bzImage initrd=initrd.img load_ramdisk=1 \
> prompt_ramdisk=0 ramdisk_size=6464 rw root=/dev/ram SLACK_KERNEL=bare.i
>
>  So, somehow, when the system boots from CDROM, its pwd=/isolinux/
> because there is no path in 'initrd=initrd.img', but there is a path
> in 'BOOT_IMAGE=/kernels/bare.i/bzImage'.
>
>  Is there a way to copy the CDROM's root filesystem to /dev/hdb1
> and alter the default 'scsi.s' bootdisk so that it loads the root
> image from /dev/hdb1?    rdev?
>
>  Can the boot files be copied to /dev/hdb1 and the 'scsi.s'
> bootdisk be altered to boot /dev/hdb1/kernels/scsi.s/bzImage
> and the root /dev/hdb1/isolinux/initrd.img?
>
>  Then the CDROM and be mounted on the SCSI CDROM drive and
> the install begun.
>
>  Heck, why not copy /isolinux/*, /kernels/scsi.s/*, & /slackware/*
> to /dev/hdb1?

As i explained in my last mail, it dont work like that.

> Wondering... Chuck

--
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[pa3gcu]

On Tuesday 10 June 2003 15:54, Hal MacArgle wrote:
> Greetings: Delay taking time out to visit the hospital taking me away
> from this more interesting stuff. <grin> Comments below at request:

Hope all is now well then..

> Hal
>
> 	First off, to make matters worse, I note that my distribution
> disk does NOT have the /rootdisks directory so that's _one_ reason
> I've been in the dark so much.. The other, seemingly, big problem is
> that the "reluctant" system has an IDE HD but both CD's are SCSI,
> driven by a BusLogic controller.. There is, also, a SCSI scanner, but
> I've disconnected it during this mess, and a ZIP250..

Just what is the model number of the Bislogic controller and what is the make 
and type/model Nr, of the cdrom's. ???

>
> 	Re above; booting from a DRDos702 floppy the BIOS sees the
> BusLogic controller OK but doesn't, automatically, assign a drive
> letter to either CD.. The IDE HD on this machine does NOT have a Dos
> partition, only 3 Linux native and 1 swap, so I'm shot down with
> Stevens' instructions as the two images wont fit on a floppy.. Maybe
> I'm missing something here - my mind has turned to Jello. :^)... I
> have the Dos drivers for Atapi drives and the required mscdex, or
> equivalent, but that's no use with a SCSI drive.. I've got to
> research this somemore..
>
> 	Trying to boot from the SlackCD with the disk in either of
> the SCSI drives and the BIOS set to Boot: SCSI, A, C, it doesn't see
> either and goes right into the normal LILO boot of /hda3.. I'm
> guessing that the autoboot routine on the CD only works when you set
> the BIOS to: CDROM,,,, and the drive is ATAPI-IDE.. So, bottom line,
> is that the CD distribution I have installs OK on a pure ATAPI-IDE
> machine - which I have already done on another machine.

That sounds more like a bios limitation than a slackware problem.
Well you could swap disk's around then and install on the machine where it 
does work, after installing you change the disk back.

>
> 	Richard has installed using the boot/root combination from
> Slack8.0, but I can't seem to get it working so far.. He's, kindly,
> trying to solve that problem..

What happens when you try and which disk do you use as the initial boot disk,?
You should be using scsi.s from what i can gather.

>
> 	It's rather obvious, that the ./makedisk <filename>
> <kernel.img> routine in the distribution doesn't work, even tho I've
> tried formatting a floppy to 1720K and 1680K, which the routine is
> supposed to do automatically.. Searching google/linux; "makedisk
> slackware 8.1" brought several horror stories.. ./makedisk creates a
> file in /tmp/xxxx.img - but what to do with that?? Load it with
> loadlin? I still have so much to learn..

As i said before, i cant get that to work either, i also said things like that 
i drop by the wayside thinking i'm just dumb, but it seems not to be the 
case.

>
> 	To me the most unfortunate thing about this is: How can I,
> with a straight face, recommend the neighbours switch to Linux??

Have you reasd the Slackware-HOWTO and BOOTING.TXT files, there are quite a 
few scsi FAQ's there and my just help.

>
> 	Sorry this is so long..
>
> Hal
>
> > > I've just executed that line (on a nearby system) and it is now
> > > running the installation routine.  Note:  you may need to change
> > > the d: to a different letter (depending on what letter was assigned
> > > by DOS to your CDrom).
> > >
> > > > Is there a way to copy the CDROM's root filesystem to /dev/hdb1
> > > > and alter the default 'scsi.s' bootdisk so that it loads the root
> > > > image from /dev/hdb1?    rdev?
> > >
> > > Yes, but it should not be necessary.  Just try loadlin.exe
> > > (get it from the loadlin zip file in the /kernels directory
> > > of the CDrom).

Maybe Steven could explain how he would copy the cdrom's root file system to a 
blank partiton and get it to boot and allow one to install the complete 
slackware disk series on the same HD.?
AFAIK you cant but i could be missing something.!. Or should i say i have 
never done such a uncommon thing and do say it should NOT be nessasay at all 
to even think of doing it

> >
> >  The installation runs much faster from hard drive.  ;-)
> >
> > > Cheers,
> > > Steven
>

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[pa3gcu]

On Tuesday 10 June 2003 17:34, Hal MacArgle wrote:

> 	OK - I went back to a completly new try using the 8.0
> buslogic.s/colour.gz combination:/hda4 as swap and a clean /hda1 as
> target. Swap on; quick format; Source Slackware CD-ROM - autoscan
> found 2nd scsi cd ok; select 'a' only - report "Installing series
> a".. Then the dreaded panel, seen so many times: "MOUNT ERROR -
> Please be sure that it is mounted on /var/log/mount/slakware and that
> the Slackware disks are found in sub dirs /var/log/mount/slakware
> like specified." (Of course on the CD they are in slackware, not
> slakware.. With OK I got the # command line again but with several
> reports: "/usr/lib/setup/setup: cannot create /mnt/etc fstab:
> directory non-existent."

Have you tryed thr "scsi.s" disk, buslogic.s is only for the MultiMaster or so 
stated in the doc's from slack-8.0.

As of 8.1 there is no buslogic.s disk its now scsi.s because of known problems 
with buslogic controllers.

>
> 	I checked and /mnt exists but not etc, so I did a mkdir etc
> there and went back to setup again.. This time I got the MOUNT ERROR
> report again, but not the previous non-existent, and, actually got as
> far as making a boot disk, selecting 'make lilo boot disk' but,
> noting that the a files were really never installed.. Trying to make
> the boot disk fd0 went into netherland and didn't stop running until
> I ejected the disk (a no-no to me, normally) Tried whole routine
> again making a 'simple' boot disk and it worked but, of course,
> reported a Kernel Panic: because there were no files on the drive..
>
> 	In summation Richard, notwithstanding all the work you and
> others have done with this - Who needs it??? Life is too short..
> Apparently 8.1 has more than one messed up directory label, compared
> to the previous versions..This version installs OK with an ATAPI-IDE
> CD and HD with a BIOS that boots CD's, period.. IMHO. <grin> Since
> some vendors are eliminating floppies from their boxes now - I guess
> that's the way to go, eh?

I dont quite know what you mean abot messed up directory labels.
I have never noticed anything funny about 8.1..

>
> APPRECIATE!!
>
>     Hal - in Terra Alta, WV - Slackware GNU/Linux 8.0   (2.4.18)
>                 Proprietary  Formats  Unacceptable

-- 
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[Hal MacArgle]

On 06-11, qwms-avib@dea.spamcon.org wrote:
> Hal MacArgle wrote:
> > 
> > booting from a DRDos702 floppy the BIOS sees the
> > BusLogic controller OK but doesn't, automatically, 
> > assign a drive letter to either CD.
> 
> A DOS bootdisk can be downloaded from www.bootdisk.com
> that handles the following CDrom drives:
> ---------------------------
> Adaptec UW (SCSI) CD or DVD
> Adaptec U2 (LVD) CD or DVD
> IDE/Atapi CD or DVD 
> ---------------------------
> It automatically assigns a drive letter (R:) to the CDrom.
> 
	AOK!, except they may not have a BusLogic version, but that's
very good to know for the future, and I'll make sure I use an ATAPI
drive next time..


> > The IDE HD on this machine does NOT have a Dos partition, 
> 
> No DOS partition is needed.  The system is booted from the
> DOS bootdisk, which launches the installation routine from
> the CDrom.

	In my case I had to fetch the _genuine_ BusLogic drivers on
the INet that assigned E: and F: to the two CD's, so I was able to
use the routine you sent Chuck loading scsi.s and initrd.img.. I'm
home free now and have installed 8.1.01, from a combination of made
up floppy and the ZIP drive, which I didn't really need.. 


> > so I'm shot down with Stevens' instructions as the two 
> > images wont fit on a floppy.
> 
> The two images do not go on the the floppy.  They are read
> (by loadlin.exe) directly from the CDrom.  

	Another mystery occurred here when the /slackware directory
on the CD became "slack000", when I looked at it, but setup found it
anyway??? I'm going bonkers but it's done bottom line...

	At least I'm learning much more than if it worked the first
time out..

    Hal - in Terra Alta, WV - Slackware GNU/Linux 8.0   (2.4.18)
                Proprietary  Formats  Unacceptable
.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[Hal MacArgle]

On 06-10, pa3gcu wrote:
> 
> Have you tryed thr "scsi.s" disk, buslogic.s is only for the MultiMaster or so 
> stated in the doc's from slack-8.0.
> 
> As of 8.1 there is no buslogic.s disk its now scsi.s because of known problems 
> with buslogic controllers.

	No I didn't try that one because the screen report indicated
that the card and drive were "successfully installed," so I felt all
was OK.. SCSI controllers are notoriously problem prone it seems as
I've had more trouble with Adaptec ones.. To each his own I guess..

	Anyway I have installed 8.1.01 using a made up boot floppy
and the ZIP drive, which I really didn't need - plus the Dos BusLogic
drivers.. I learned a lot about ZIP this time around too.. :^)..

	I hope I don't have to go through this again.. <grin>

    Hal - in Terra Alta, WV - Slackware GNU/Linux 8.0   (2.4.18)
                Proprietary  Formats  Unacceptable
.




-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Slackware 8.1.01 Install????

[qwms-avib]

Hal MacArgle wrote:
> 
> booting from a DRDos702 floppy the BIOS sees the
> BusLogic controller OK but doesn't, automatically, 
> assign a drive letter to either CD.

A DOS bootdisk can be downloaded from www.bootdisk.com
that handles the following CDrom drives:
---------------------------
Adaptec UW (SCSI) CD or DVD
Adaptec U2 (LVD) CD or DVD
IDE/Atapi CD or DVD 
---------------------------
It automatically assigns a drive letter (R:) to the CDrom.


> The IDE HD on this machine does NOT have a Dos partition, 

No DOS partition is needed.  The system is booted from the
DOS bootdisk, which launches the installation routine from
the CDrom.

> so I'm shot down with Stevens' instructions as the two 
> images wont fit on a floppy.

The two images do not go on the the floppy.  They are read
(by loadlin.exe) directly from the CDrom.  

Cheers,
Steven

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs