LinuxQuestions.org
Review your favorite Linux distribution.
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
 
LinkBack Search this Thread
Old 03-20-2013, 04:31 AM   #1
coner
LQ Newbie
 
Registered: Mar 2013
Posts: 21

Rep: Reputation: Disabled
Valid Setup Targets


Re: slackware-14.0-install-dvd.iso

hi,

what are valid targets for setup? docs indicate hard drive is the only option!

can a flash stick mimic a hard drive, so the usb stick can also be a bootable target?

the plan is to have the hard drive exempt from setup's installation process.

coner
 
Old 03-20-2013, 06:02 AM   #2
michaelslack
Member
 
Registered: Feb 2013
Location: Sydney
Distribution: slackware
Posts: 78

Rep: Reputation: 25
You can certainly install slackware on a usb stick, in fact there are recent threads that go into the details, most recently this one which in turn links back to this one.

In brief, you need to use fdisk or cfdisk to set up partitions before you run setup, and then inside the setup program you just choose which device you want to install to -- this can be a usb stick or an external usb hard drive (the latter is perhaps more sensible since usb sticks are supposed to have limited write cycles and so it is sometimes said that installing a regular linux distribution on one of them can burn it out quite quickly).

If your usb stick/drive shows up as /dev/sdb (while your main drive shows up as /dev/sda, say) then you go e.g. fdisk /dev/sdb and away you go...

I hope this helps,

Michael
 
Old 03-20-2013, 08:37 AM   #3
coner
LQ Newbie
 
Registered: Mar 2013
Posts: 21

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by michaelslack View Post
You can certainly install slackware on a usb stick,

If your usb stick/drive shows up as /dev/sdb (while your main drive shows up as /dev/sda, say) then you go e.g. fdisk /dev/sdb and away you go...

I hope this helps,

Michael
Hi Michael,

I followed this guide:
INSTALL

It said LILO is very close knit to Slackware system, but did not go into any details. It did mention to manually install LILO and its config file is located:
/etc/lilo.conf

If Slackware does not boot, there is no way to access 'lilo.conf'.

Also, installation did mention 'os/2 boot manager' was an option, that's new to me.

Regards,
coner
 
Old 03-20-2013, 03:16 PM   #4
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware-14.0 on a Lenovo T61 6457-4XG
Posts: 3,643

Rep: Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828
The 'setup' main program of the installer early runs the 'probe' wrapper to fdisk to make a list of all partitions with their types.

Then when you select the TARGET entry it allows you to choose as target any partition of type 'Linux', regardless of the media where it lies.

Oh, and about "os/2 boot manager", you *could* find a machine with OS/2 installed (look for that in the nearest computer museum). But the "liloconfig" program does not allow you to deal with OS/2 partitions any more (the code is still there just in case OS/2 makes a comeback but is commented out).
 
Old 03-20-2013, 07:15 PM   #5
michaelslack
Member
 
Registered: Feb 2013
Location: Sydney
Distribution: slackware
Posts: 78

Rep: Reputation: 25
I think I see your problem.

First, before you run setup, you need to create a linux partition and a swap partition on your usb device (flashstick/external hard drive). You can use fdisk, use `n' to create new partitions and `t' to make sure they are the correct type (when you use `p' in fdisk the linux partition should have Id 83, the swap should have Id 82).

Then run setup. Suppose your usb device comes up as /dev/sdb. Then when it comes to installing lilo you can try to do it within setup but it might be better to skip that step and install it manually after you exit setup but before you reboot. If you choose this path, one way is to edit /etc/lilo.conf so it has something like the following:

near the top of the file it should say

boot=/dev/sdb

(this means lilo gets installed to the MBR of your usb device). Then further down near the bottom it should have something like

image=/boot/vmlinuz
root=/dev/sdb1
label=slackware
read-only

Then save and exit, and run the command `lilo' which actually installs it.

Then in theory you should be able to reboot, select the boot menu from the bios and choose the usb device and hopefully the slackware boot screen will appear. If this doesn't work you should also be able to boot into your slackware installation using your original install dvd. At the boot: prompt (assuming the usb device still comes up as /dev/sdb)
use something like

mount root=/dev/sdb1

and you should be able to boot into your new installation from where you can fiddle about with lilo and/or maybe use fdisk to make /dev/sdb1 bootable using the `a' command?

I'm in a bit of a rush, there may be some errors in the above but I hope it helps,

Michael
 
Old 03-22-2013, 03:23 PM   #6
coner
LQ Newbie
 
Registered: Mar 2013
Posts: 21

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by michaelslack View Post

Then save and exit, and run the command `lilo' which actually installs it.


Michael
Hi Michael,

Please provide more 'lilo' instructions? If, when exiting 'setup' and typing 'lilo', the only response is:

SH: LILO: COMMAND NOT FOUND

Must it be typed in root and how is root accessed from the install DVD?

coner
 
Old 03-22-2013, 03:44 PM   #7
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware-14.0 on a Lenovo T61 6457-4XG
Posts: 3,643

Rep: Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828
lilo is not included in the installer. It is (to be) run inside the freshly installed Slackware, for instance after chrooting to it before rebooting

This not a privilege problem as all you do during installation (before you reboot) is as root.

Oh, and I don't understand what you meant when you wrote: "the plan is to have the hard drive exempt from setup's installation process." Could you please elaborate a bit on:
(1) the meaning (it may be obvious for you, then sorry to ask but English is not my native language)
(2) the goal (why do you need that?)

Last edited by Didier Spaier; 03-22-2013 at 04:58 PM.
 
Old 03-22-2013, 04:44 PM   #8
michaelslack
Member
 
Registered: Feb 2013
Location: Sydney
Distribution: slackware
Posts: 78

Rep: Reputation: 25
Hi coner,

Sorry I forgot one important step: as Didier points out, after you exit setup you need to

chroot /mnt

Then you can cd /etc and open lilo.conf in an editor (the vi editor for instance), make sure it has the lines I mentioned above, save it, then execute the command

lilo

This installs lilo onto the master boot record of your usb device. Then you can (try to) reboot. If this doesn't work you can always use the install dvd to boot into the new installation (as described in my earlier post) and once there you can try to install lilo as detailed above (no chroot necessary then of course).

Michael
 
Old 03-22-2013, 05:45 PM   #9
coner
LQ Newbie
 
Registered: Mar 2013
Posts: 21

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Didier Spaier View Post

Oh, and I don't understand what you meant when you wrote: "the plan is to have the hard drive exempt from setup's installation process." Could you please elaborate a bit on:
(1) the meaning (it may be obvious for you, then sorry to ask but English is not my native language)
(2) the goal (why do you need that?)
Hi Didier Spaier,

I will translate:
Its been a year now, since making the Linux leap. The first two Distro's were Mint & Lubuntu, which installed out-of-the-box onto a 8GB USB thumb drive. Also, included was Grub2, that made a dual-boot setup. These Linux OS's functioned without using the Warranteed Windows OS's HD. This is what I mean 'exempt'. Grub2 allowed me to select either Windows or Linux.

I am simply trying to mimic this functionality with my latest Distro, Slackware 14.0

Regards,
coner
 
Old 03-22-2013, 06:05 PM   #10
coner
LQ Newbie
 
Registered: Mar 2013
Posts: 21

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by michaelslack View Post

Then you can cd /etc and open lilo.conf in an editor (the vi editor for instance), make sure it has the lines I mentioned above, save it, then execute the command

lilo


Michael
Hi Michael,

From your earlier post, you suggested skipping lilo setup, as I did. This leaves NO config at:

/etc/lilo.conf

At least I couldn't find it.

What does lilo.conf essentially need, besides the 'boot' and 'root' data, that you posted?

coner
 
Old 03-22-2013, 07:13 PM   #11
coner
LQ Newbie
 
Registered: Mar 2013
Posts: 21

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by michaelslack View Post
Hi coner,

Sorry I forgot one important step: as Didier points out, after you exit setup you need to

chroot /mnt


Michael
Hi Michael,


I tried your command:

Code:
chroot /mnt
This dialog followed:

Code:
CHROOT: CAN'T EXECUTE '/bin/sh': no such file or directory
Did setup have a failure during install?

coner
 
Old 03-22-2013, 07:23 PM   #12
coner
LQ Newbie
 
Registered: Mar 2013
Posts: 21

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by michaelslack View Post
If this doesn't work you should also be able to boot into your slackware installation using your original install dvd. At the boot: prompt (assuming the usb device still comes up as /dev/sdb)
use something like

mount root=/dev/sdb1


Michael
Hey Michael!

The Command you posted above, trapped this error:

Code:
Could not find kernel image: mount
There must be a few more additions?
coner
 
Old 03-22-2013, 09:05 PM   #13
michaelslack
Member
 
Registered: Feb 2013
Location: Sydney
Distribution: slackware
Posts: 78

Rep: Reputation: 25
OK I think I know what that is.

With each new release, the exact way to boot from the install media changes slightly. For instance, on an old slackware 13.1 CD1 I had lying around, the way to use the installation CD to boot the slackware installed on /dev/sdb1 is to enter the following at the boot: prompt

hugesmp.s root=/dev/sdb1 rdinit= ro

(sorry, the word ``mount'' is used in the same way as hugesmp.s is above here, as the label for the image to boot on the slackware usb bootdisk created during setup, my mistake. It will be different on install media, but see below...)

I tried doing this today on an old SD card I had lying around (I've got lots of things lying around). I couldn't install lilo -- I don't know why, but I tried to boot the new installation from the install CD. The first time around it didn't work -- couldn't find /dev/sdb1. But I remembered reading about a kernel option rootdelay= which lets it wait a while before trying to mount the root partition. So instead I used

hugesmp.s root=/dev/sdb1 rdinit= ro rootdelay=30

and as it booted, it stopped with a message like ``waiting 30 sec to mount root'' or something, and after a few seconds, it printed out ``found ... sdb''. So this did the trick.

Now, I know it's still a long way off from perfect, but I believe you should be able to boot into the slackware installation on your external device as follows:

0. Go ahead and install slackware onto your external device (say it is detected as /dev/sdb, for the sake of illustration, and that your root partition is /dev/sdb1). Don't try to install lilo though.
1. Boot the install media.
2. Look at the message, it will say something like ``In a pinch, you can boot your system from here with a command like:

boot: ..... root=/dev/sda1 ......''

(where the contents of the two .... vary slightly from release to release -- I'm not sure what yours will say ).

Now, at the boot: prompt type the same line as in the welcome message *BUT*
(a) change the sda1 to sdb1 (or whatever your root partition is) and
(b) add ``rootdelay=30'' (you can make it less 30 after you have tried it once to see how long it takes for your /dev/sdb1 to be detected) to the end of the line (leaving a space after what is already there), then hit Enter.

If you have installed a system on the given partition, it should detect it and boot into it.

Once this is working you can worry about installing lilo.

I'm sorry this is all a bit rough, but hopefully it will help you.

Michael

Last edited by michaelslack; 03-22-2013 at 09:10 PM. Reason: Clarify instructions
 
Old 03-23-2013, 02:14 AM   #14
coner
LQ Newbie
 
Registered: Mar 2013
Posts: 21

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by michaelslack View Post
So instead I used

hugesmp.s root=/dev/sdb1 rdinit= ro rootdelay=30



Michael
Hi Michael,

Slackware 14.0 install DVD calls for the same 'panic' command, along with your rootdelay tip. Root gets mounted, then OS freezes with caps lock LED blinking:

Code:
EXT4-fs (sdb1):mounted filesystem with ordered data mode.Opts:(null)
VFS:Mounted root (ext4filesystem) readonly on device 8:17.
devtmpfs:error mounting -2
Kernel panic-not syncing: No init found. Try passing init= option to kernel.
See Linux Documentation/init.txt for guidance.
What's this Kernel panic about? I need to locate init.txt Linux Doc.
coner
 
Old 03-23-2013, 04:31 AM   #15
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware-14.0 on a Lenovo T61 6457-4XG
Posts: 3,643

Rep: Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828
The device name of an SCSI removable device can change. You will have to designate it by its UUID instead. man liklo, man fstab, man blkid, search for "blkid UUID" inthis forum.
 
  


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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
setup for official Laptop. (Admin setup in server and user account setup in lap) vignesh4sh Linux - Server 3 11-26-2012 07:03 AM
Systemd Targets Brandon9000 Linux - General 2 10-17-2012 11:59 AM
What is the recommended way to setup Linux with iSCSI targets the_gripmaster Red Hat 3 06-17-2011 07:51 AM
Maven targets Millenniumman Programming 0 07-03-2008 08:14 PM
makefile targets dand Programming 1 07-11-2005 03:28 PM


All times are GMT -5. The time now is 06:48 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration