Searching \ for '[OT]: Linux installation woes' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/index.htm?key=linux+installation
Search entire site for: 'Linux installation woes'.

Exact match. Not showing close matches.
PICList Thread
'[OT]: Linux installation woes'
2002\08\28@171620 by Pic Dude

flavicon
face
This is odd... I can't get Linux to install on my Thinkpad 600X, from
another HD.

Setup:  primary drive already partitioned.  Secondary drive has a FAT32
partition with a directory "s2", under which are the directories "a", "ap",
"d", etc.

Error:  After telling it which packages to install, it cannot find the "a"
disk set, then "ap", etc.

I've tried this using the "install from another partition" option as well
and manually mounting the partition and then telling it to install from a
directory already mounted and specifying "/slack/s2".  Yes, in the latter
case, I can manually browse the directories.  I'm also mounting it as vfat.

The closest I've got is with an older version of slackware install on a
secondary HD.  I mount the HD on /slack in which there is a dir s2 that has
the a, ap, d, x folders.  The setup program goes as far as letting me choose
the sets, then says that it couldn't find the a set, ap set, etc.  If I
choose expert mode, it will go one step further and ask me what I want from
the a set before coming back to tell me that it cannot find the a set.  Only
difference I can find with that version is a file called "diska1.txt" in the
a1 directory, etc.

Any idea why?

Cheers,
-Neil.

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email spam_OUTlistservTakeThisOuTspammitvma.mit.edu with SET PICList DIGEST in the body


2002\08\28@173702 by Peter L. Peres

picon face
I do not know for sure but I think you have to put the disks under a
directory that must be named slakware (without a c). Usually when
automatic install does not work I do it by hand from scratch using pkgtool
or a shell script that does what it does ... no qualms about that here.

Also depending on where you got the disks, you may have to uncompress them
(do you see packages under a1 etc etc ?).

Peter

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email .....listservKILLspamspam@spam@mitvma.mit.edu with SET PICList DIGEST in the body


2002\08\28@212855 by Pic Dude

flavicon
face
Okay, just tried that and it failed too.  I CD'ed into the
directory with the disk sets, ran pkgtool and hit the first
option (install from current directory).  All I got was a
command prompt again.  Did this about 50 times to read the
message that flashed across:
   //var/log/packages: no such file or directory

Apparently this is linked to an adm directory somewhere that
does not exist.  Odd.

I see the .tgz packages under the a, ap, d, etc directories.
I've never had to uncompress the tgz's.  That should be one
of the functions of pkgtool.

I'm going to wget the full installation, re-create the boot
and root disks and try again.

Thanks,
-Neil.



> {Original Message removed}

2002\08\29@011801 by Peter L. Peres

picon face
On Wed, 28 Aug 2002, Pic Dude wrote:

>Okay, just tried that and it failed too.  I CD'ed into the
>directory with the disk sets, ran pkgtool and hit the first
>option (install from current directory).  All I got was a
>command prompt again.  Did this about 50 times to read the
>message that flashed across:
>    //var/log/packages: no such file or directory
>
>Apparently this is linked to an adm directory somewhere that
>does not exist.  Odd.
>
>I see the .tgz packages under the a, ap, d, etc directories.
>I've never had to uncompress the tgz's.  That should be one
>of the functions of pkgtool.

I did not say to uncompress them. Sometimes the DISKS are compressed.
That's how you dl them. Do you see several .tgz files inside each
directory ?

>I'm going to wget the full installation, re-create the boot
>and root disks and try again.

Wait a sec. I gather that you do not have anything in the system yet. This
means that the base structure of the installation is not in place.
/var/log/packages contains a list of installed packages (one file per
package). It does not exist if you did not boot off of the right disk and
started install from there.

There are options to run pkgtool w/o this of course. I do not have it
here so I can't say.

Normally setup (slackware setup) expects to run off a boot+rootdsk floppy.
Is this how you boot ? By the time you run setup or pkgtool it is
necessary for this framework to exist. If you fudged it by hand you need
to generate it yourself. An easy way is to install aaa_base.tgz by hand.
Here are the steps:

1. cd /mounted/root_partition
2. rm -f install/doinst.sh # do not skip this step
3. tar -xzvf /somewhere/a??/aaa_base.tgz
4. if [ -x install/doinst.sh ]; then . install/doinst.sh; done

After this you should be able to run pkgtool and setup. pkgtool is
peculiar about the paths you give it (what isn't ?), trailing slashes and
other such things. Type carefully or your ass will be laminated ;-)

pkgtool does this when installing packages. pkgtool is a shell script, you
can read it or run it in debug mode to find out what it tries to do and
fix it. So is setup. Both should be run while in the directory
/mounted/root_partition, although there are ways to do it elsewhere.

Peter

--
http://www.piclist.com hint: To leave the PICList
piclist-unsubscribe-requestspamKILLspammitvma.mit.edu


More... (looser matching)
- Last day of these posts
- In 2002 , 2003 only
- Today
- New search...