LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
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 03-16-2015, 10:42 AM   #16
rudsonalves
LQ Newbie
 
Registered: Jul 2009
Posts: 6

Rep: Reputation: 0

I saw the parameter changed Alien Bob:

Quote:
On Slackware 13.37:
Code:
        -A number
              Make the indicated partition(s) active, and all others inactive.
On Slackware 14.1:

Code:
       -a, --activate device [partition-number...]
              Switch  on  the bootable flag.  If no partition-number is speci-
              fied, then all partitions with an enabled flag are listed.

OPTIONS
       -A, --append
              Don't  create  a new partition table, but only append the speci-
              fied partitions.
But in Slackware64 14.1, where "-a, --activate device [partition-number...]" in sfdisk command, the script usbimg2disk.sh is "-A" and not "-a".

Check you self

http://mirrors.slackware.com/slackwa...usbimg2disk.sh

The same in Slackware-current.

http://mirrors.slackware.com/slackwa...usbimg2disk.sh


See the code
Code:
...
makebootable() {
  # Only parameter: the name of the USB device to be set bootable:
  USBDRV="$1"

  # Sanity checks:
  if [ ! -b $USBDRV ]; then
    echo "*** Not a block device: '$USBDRV' !"
    exit 1
  fi

  # Set the bootable flag for the first partition:
  /sbin/sfdisk -A $USBDRV 1
}
...
Thank you for your kindness.
 
Old 03-16-2015, 01:14 PM   #17
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106
That's what I meant. The script stayed the same, expecting that a sensible develoer does not suddenly mess up the meaning of the parameters of his program.
As a result of that, the script in Slackware-current does not work anymore.
That's not the fault of the script which has existed since before Slackware 13.37.
 
  


Reply

Tags
usbimg2disk.sh



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
usbimg2disk.sh - 'This is not a directory' gcamp689 Slackware - Installation 6 08-21-2013 04:26 PM
usbimg2disk.sh fails in current piratesmack Slackware 6 11-26-2010 02:27 PM
[SOLVED] USB bootstick, usbimg2disk.sh and OEM recovery partition catkin Slackware 15 07-01-2010 02:54 AM
usbimg2disk.sh fails on dependencies check zavko Slackware 1 02-11-2010 10:11 AM
Squid failed: line 162 su_jump Linux - Newbie 0 10-17-2002 08:49 PM

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

All times are GMT -5. The time now is 05:44 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