LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-27-2013, 04:51 PM   #1
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,340

Rep: Reputation: Disabled
Missing "pr" utility in Slackware-current's installer?


Installing Slackware-current I tried to use an USB key as source. It didn't work so I had a look at /dev/tty4. I saw a lot of errors and also a message about pr being an unknown command in rescan-scsi-bus, line 283:
Code:
echo "$SCSISTR" | tail -n2 | pr -o4 -l1
In Slackware pr is in /bin, but not in the initrd. Maybe that should be added to the busybox or directly to /bin (not very heavy)?

I don't know if that could explain the other errors though. I'll try to pastebin them.

Last edited by Didier Spaier; 09-27-2013 at 04:53 PM.
 
Old 09-27-2013, 05:38 PM   #2
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 3,066

Rep: Reputation: 9877Reputation: 9877Reputation: 9877Reputation: 9877Reputation: 9877Reputation: 9877Reputation: 9877Reputation: 9877Reputation: 9877Reputation: 9877Reputation: 9877
Quote:
Originally Posted by Didier Spaier View Post
Installing Slackware-current I tried to use an USB key as source. It didn't work so I had a look at /dev/tty4. I saw a lot of errors and also a message about pr being an unknown command in rescan-scsi-bus, line 283:
Code:
echo "$SCSISTR" | tail -n2 | pr -o4 -l1
In Slackware pr is in /bin, but not in the initrd. Maybe that should be added to the busybox or directly to /bin (not very heavy)?

I don't know if that could explain the other errors though. I'll try to pastebin them.
It does seem like /bin/pr should be added, yes.

I'd be interested in the details of how the USB stick was structured... partitioning, filesystem, and directory structure. And, if it was made using usbimg2disk.sh, if the updated version was used. The previous one mounts the stick at boot which interfered with detection here.
 
Old 09-27-2013, 06:00 PM   #3
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,340

Original Poster
Rep: Reputation: Disabled
I couldn't grab kernel messages in /dev/tty4 (dunno how to do that?), but at least output of
Code:
/sbin/rescan-scsi-bus -l 1>$RDIR 2>$RDIR
in INSUSB (replacing RDIR=/dev/tty4 with RDIR=/tmp/scan.txt). The USB stick has only one vfat partition with one directory named /slackware64 with the same subdirectories as on the ftp site. I didn't use usbimg2disk.sh, only "cp -r" from a local mirror.

EDIT What puzzles me are these lines:
Code:
/sbin/rescan-scsi-bus: line 283: /mnt/usr/bin/pr: cannot execute binary file
as I don't understand neither why pr is looked at in /mnt nor in /usr/bin instead of /bin. It's late here, I could have a look tomorrow if need be.
Attached Files
File Type: txt scan.txt (11.6 KB, 11 views)

Last edited by Didier Spaier; 09-27-2013 at 06:07 PM. Reason: EDIT added
 
Old 09-27-2013, 06:45 PM   #4
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 3,066

Rep: Reputation: 9877Reputation: 9877Reputation: 9877Reputation: 9877Reputation: 9877Reputation: 9877Reputation: 9877Reputation: 9877Reputation: 9877Reputation: 9877Reputation: 9877
Quote:
Originally Posted by Didier Spaier View Post
I couldn't grab kernel messages in /dev/tty4 (dunno how to do that?), but at least output of
Code:
/sbin/rescan-scsi-bus -l 1>$RDIR 2>$RDIR
in INSUSB (replacing RDIR=/dev/tty4 with RDIR=/tmp/scan.txt). The USB stick has only one vfat partition with one directory named /slackware64 with the same subdirectories as on the ftp site. I didn't use usbimg2disk.sh, only "cp -r" from a local mirror.
Thanks. I'll make one that's similar and see if I can figure out what's going on.

Quote:
EDIT What puzzles me are these lines:
Code:
/sbin/rescan-scsi-bus: line 283: /mnt/usr/bin/pr: cannot execute binary file
as I don't understand neither why pr is looked at in /mnt nor in /usr/bin instead of /bin. It's late here, I could have a look tomorrow if need be.
The installer puts paths under /mnt ahead of the normal ones to try to use the better-than-busybox utilities once they are installed, and for other things like lilo that aren't actually on the installer. At the time INSUSB runs, there shouldn't be anything under there, so I'd expect "file not found" rather than any other kind of error message. Again, I'll take a look at it and see what I get here. Thanks!
 
Old 09-28-2013, 05:05 AM   #5
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,340

Original Poster
Rep: Reputation: Disabled
Failing probe of the key unrelated to missing "pr"

To make sure I commented out the line calling /sbin/rescan-scsi-bus in INSUSB: same result, the slackware directory is not found.

But I forgot to tell that I used another (not partitioned) USB key as installation media and noticed that after I run INSUSB the installation key (not the one with the packages) was mounter under /usb-stick. So, it seems that as the installation key is the first listed in $REMOVEABLE_DEVICES but contains no partition, INSUSB tries to munt it as unpartitioned:
Code:
mount /dev/$DEVICE /usb-stick 1> /dev/null 2> /dev/null
Mount succeeds, though kernel complains verbosely it can't find any fileystem on the device (which is right), but of course there is no Slackware directory on it, so it says "NO SLACKWARE DIRECTORY FOUND" (In French here :-).

PS the key with the packages is well recognized by the kernel and shows in /proc/partitions as in /sys/block (with removable=1).

PPS. Stupid me: this was caused by an architecture misfit between the installer and the USB key containing the packages, so "mv slackware64 slackware" did the trick. Maybe because in slint I overlooked differences in INSUSB for 32 and 64 bit, or I mistakenly copied one over the other, I will check and correct that then.

PPPS. Yes I had the same (internationalized) file for both archs, my mistake. Messages in both genuine files are identical so no more translation is needed (but maybe a warning could be added, like "a slackware directory was found, but not for the same architecture as the installer"?) Yes, that would complicate things a bit though.

Last edited by Didier Spaier; 09-28-2013 at 11:35 PM. Reason: minor fixes
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Ubuntu 10.04 - missing "Build" directory for current kernel | 2.6.32-38-generic | floorripper Linux - Newbie 2 02-18-2012 06:27 AM
seeking linux workstation oriented "audit" or "inventory" utility SaintDanBert Linux - Software 2 02-08-2012 05:02 AM
"Xlib: extension "XFree86-DRI" missing on display ":0.0"." zaps Linux - Games 9 05-14-2007 03:07 PM
Kernel Panic - Missing "initrd.img-2.6.8-2-686" in /boot MKSrivastava Debian 2 12-02-2005 03:09 PM
"multiboot utility" and "dell utility partition" on dell i5150 xround Linux - Laptop and Netbook 5 04-21-2005 09:19 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 02:54 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration