[SOLVED] pkgtool hangs

offplanet · 08-21-2014, 08:47 PM

script -c 'pkgtool --sets a#ap#d#f#k#kde#l#n#t#tcl#x#xap#xce#y# --source_dir /media/TOSHIBAEXT/slackware/slackware64-curent/slackware64/ --target-dir /ubuntu --tagfile tagfile' install-slackware-2014-08-21.18:27.log the above command hangs my cpu at 50% and does nothing. It does not populate mounted partition /upuntu. It produces no output in the install log. tagfile is a tree that contains a directory for each disk set that contains a copy of the default tagfile. suggestions please.

Drakeo · 08-21-2014, 10:10 PM

you try reinstalling pkgtool because pkgtool is a noarch program it is just scripts. So what was your goal is here ?

offplanet · 08-21-2014, 10:29 PM

Drakeo, my goal is to automate a clean slackware installation in an empty partition. I was able to reduce the cpu time to less than 10% by putting a # in front of the first --sets argument. It still hangs tho. checking the remaining arguments.

Drakeo · 08-21-2014, 11:07 PM

you know that pretty simple actually. I set up some scripts for my friend to actually install slackware while running puppy linux ok want a script how i do it.
i do a

Code:

    #!/bin/sh
    cd /mnt/sdb2/Slackware/slackware64-14.1/slackware64 # set to your partition 
    for dir in a ap d e f k kde l n t tcl x xap xfce y ; do
      ( cd $dir ; installpkg -root /mnt/sdb2 *.t?z )
    done

if you do not want a full install pick out some
here this says you have sdb2 set up to be installed on my first script actually mirrored the repo to sdb2.
you need to set up a boot loader. before and then go to telinit 1 run pktools and create a password etc.

offplanet · 08-21-2014, 11:27 PM

Watch your hyphens and underbars in the arguments. The first # symbol in front of the disk sets must be there and quotes. Also the source-dir path was missing an extra r. Below is the command that runs:

Code:

script -c 'pkgtool --sets "#a#ap#d#f#k#kde#l#n#t#tcl#x#xap#xfce#y#" --source-mounted --source_dir /media/TOSHIBAEXT/slackware/slackware64-current/slackware64/ --target_dir /ubuntu --tagfile tagfile' install-slackware-$(date +%F.%H-%M).log

Now I am working to see why it is ignoring the tag files.

offplanet · 08-21-2014, 11:32 PM

I copied your script Drakeo. Thanks. Where can I go to learn how to make my posts readable?

Drakeo · 08-22-2014, 06:30 AM

Quote:

Originally Posted by offplanet

I copied your script Drakeo. Thanks. Where can I go to learn how to make my posts readable?

I really do not understand the question. that script is just a little bit of a modification of the upgrade text from slackware.

Quote:

Where can I go to learn how to make my posts readable?

please elaborate a little more.

offplanet · 08-22-2014, 08:40 AM

Quote:

Originally Posted by offplanet

I copied your script Drakeo. Thanks. Where can I go to learn how to make my posts readable?

The LQ reply tool was removing my double quotes and substituting text.
And I did not understand why.

Text formatting LQ reply and figuring out PKGTOOL are 2 different problems. The BB CODE TAGS helped but I need to learn more about LQ reply formatting.

TracyTiger · 08-22-2014, 10:07 AM

Quote:

Originally Posted by offplanet

The BB CODE TAGS helped but I need to learn more about LQ reply formatting.

@offplanet You mention BB Codes. Have you seen these pages?

General

BBCodes

Smilies

I've not had trouble with double quotes. Perhaps if you elaborate someone can offer a suggestion.

EDIT: You can select the version of the editor (simple, WYSIWYG) you use by configuring you LQ account options.

offplanet · 08-23-2014, 06:20 PM

In my code section I used double quotes after the --sets text. The editor removed the quotes and put amp;stuffhere;amp; in its place. This was during the preview process. I went back and edited it to put the double quotes back before I submitted. This time it stayed there. I don't know why. The sections on bbcodes smiles and general did not talk about the tag I saw in Drakeo's post to force a new line. I even used it. But now the tag does not show up and I don't remember the exact syntax. It had angle brackets, a slash and a b. All of this is a side issue. I need to get back to figuring out why my tag files are not being used. Today hopefully. Thanks to all who offered help.

Drakeo · 08-24-2014, 07:01 AM

durring your post you will see the go advance at the bottom this will allow you to use the code # insert. and many other things.