LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
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 11-15-2010, 03:46 PM   #16
Squall90
Member
 
Registered: Oct 2009
Distribution: Currently several distros :S
Posts: 148

Rep: Reputation: 29

On the Slackware disk, there should be an README.initrd. If not, you can read it online on Slackware ftp servers -> ftp://ftp.osuosl.org/pub/slackware/s.../README.initrd

If you follow the instructions, it should work. (At least, it worked many times for me.)
_____________

You should probably follow Pat's instructions.

Last edited by Squall90; 11-15-2010 at 03:48 PM. Reason: damn, pat was faster ;P
 
Old 11-15-2010, 03:55 PM   #17
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 813

Original Poster
Rep: Reputation: 96
Quote:
Originally Posted by volkerdi View Post
Perhaps first things first... if you didn't have any idea how to make an initrd before, I'm going to step out on a limb and guess that you did not previously have one. So rather than consider the pros and cons of using an initrd versus using the huge kernel, probably we should start by getting you back where you were. So...

First, make sure that the new 2.6.35.7 kernel packages are installed, and make sure that /etc/lilo.conf is pointing to the new huge kernel in /boot (either by using the full filename, or by making sure if lilo.conf uses a symlink, that it points to the right kernel). Then run "lilo" as root, and you should be good to reboot without the disc.

Assuming that works, you can check out README.initrd in /usr/doc/mkinitrd[...] at your leisure.

Hope this helps.
Okay, problem here. Even when I logged on using the disk as per your instructions, it failed to mount my logical volume group, which includes the /usr directory which of course includes vim or any other software I'd want to use to view/modify my /etc/lilo.conf file. Any ideas?
 
Old 11-15-2010, 03:57 PM   #18
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,390

Rep: Reputation: Disabled
Quote:
Originally Posted by 2handband View Post
God no... it's a _64 package on a _64 system.

Anyway... I followed your instructions above, and I was able to log in. I'm not sure what to do now, however. How does one go about rebuilding one's initrd?
Run the command
Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh
to get an idea (it's safe to run that command - it does not do anything, it only shows hints about building your initrd and adding it to lilo.conf).

Eric
 
Old 11-15-2010, 04:00 PM   #19
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 813

Original Poster
Rep: Reputation: 96
Quote:
Originally Posted by Alien Bob View Post
Run the command
Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh
to get an idea (it's safe to run that command - it does not do anything, it only shows hints about building your initrd and adding it to lilo.conf).

Eric
Can't... I have no access to the contents of my /usr directory... it's in the VG.
 
Old 11-15-2010, 04:11 PM   #20
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,390

Rep: Reputation: Disabled
Quote:
Originally Posted by 2handband View Post
Can't... I have no access to the contents of my /usr directory... it's in the VG.
YEs, that is th moment when you boot to the command prompt of the Slackware install disk, use the tools available in the install environment to configure your logical volumes:
Code:
vgscan --mknodes ; vgchange -ay
and once yu have your mapped devices, start mounting the partitions below /mnt

Once you ended up with the computer's complete filesystem mounted bwlow /mnt (i.e. the root fs, /home , boot and every other partitions are mounted below /mnt) you can proceed with making the virtual filesystems and devices available below /mnt as well:
Code:
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount --bind /dev /mnt/dev
And then you are ready to enter your computer's Slackware using the "chroot" command, re-create the initrd if needed - assuming that /etc/lilo.conf already had the proper section added before - and re-run lilo:
Code:
chroot /mnt
$( /usr/share/mkinitrd/mkinitrd_command_generator -r )
lilo
Note the difference between running:
Code:
/usr/share/mkinitrd/mkinitrd_command_generator -r
and
Code:
$( /usr/share/mkinitrd/mkinitrd_command_generator -r )
The first shows a mkinitrd commandline that should fit your computer's configuration, while the second command actually executes that very mkinitrd command.
Some rough edges will remain in these instructions, I wrote them in a hurry, but you will be able to go from there.

Eric
 
Old 11-15-2010, 04:13 PM   #21
brixtoncalling
Member
 
Registered: Jul 2008
Location: British Columbia
Distribution: Slackware current
Posts: 403

Rep: Reputation: 67
I know this is a little off-topic, but since this thread is related to initd problems and has attention from above, let me ask why doesn't the generic kernel have ext2/3/4 built in to begin with? I'm sure there is a very good response, but I've always been curious.
 
Old 11-15-2010, 04:20 PM   #22
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 813

Original Poster
Rep: Reputation: 96
Quote:
Originally Posted by Alien Bob View Post
YEs, that is th moment when you boot to the command prompt of the Slackware install disk, use the tools available in the install environment to configure your logical volumes:
Code:
vgscan --mknodes ; vgchange -ay
and once yu have your mapped devices, start mounting the partitions below /mnt

Once you ended up with the computer's complete filesystem mounted bwlow /mnt (i.e. the root fs, /home , boot and every other partitions are mounted below /mnt) you can proceed with making the virtual filesystems and devices available below /mnt as well:
Code:
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount --bind /dev /mnt/dev
And then you are ready to enter your computer's Slackware using the "chroot" command, re-create the initrd if needed - assuming that /etc/lilo.conf already had the proper section added before - and re-run lilo:
Code:
chroot /mnt
$( /usr/share/mkinitrd/mkinitrd_command_generator -r )
lilo
Note the difference between running:
Code:
/usr/share/mkinitrd/mkinitrd_command_generator -r
and
Code:
$( /usr/share/mkinitrd/mkinitrd_command_generator -r )
The first shows a mkinitrd commandline that should fit your computer's configuration, while the second command actually executes that very mkinitrd command.
Some rough edges will remain in these instructions, I wrote them in a hurry, but you will be able to go from there.

Eric
Point of clarification... I executed the vgscan command and successfully activated the logical volumes. Now, are you saying I need to mount the entire filesystem manually? As in:

Code:
mount /etc /mnt/etc
and so on? If this is a dumb question I'm sorry, we're WAY outside of my comfort zone here...
 
Old 11-15-2010, 04:22 PM   #23
Ilgar
Member
 
Registered: Jan 2005
Location: Istanbul, Turkey
Distribution: Slackware 14.1, Slackware64 14.1
Posts: 930

Rep: Reputation: 96
@brixtoncalling: I wonder about the same thing, too. Maybe because some people may prefer ReiserFS, XFS or other filesystems. But given that 1) we do no longer bother about fitting everything on a floppy, 2) ext* filesystems are widely used and 3) the recent kernels support shared code for ext2/3/4, compiling ext4 into the kernel wouldn't be much of a bloat, would it?
 
Old 11-15-2010, 04:28 PM   #24
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 877

Rep: Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826
Quote:
Originally Posted by brixtoncalling View Post
I know this is a little off-topic, but since this thread is related to initd problems and has attention from above, let me ask why doesn't the generic kernel have ext2/3/4 built in to begin with? I'm sure there is a very good response, but I've always been curious.
Because those filesystems are not needed to load the initrd, and the idea behind the generic kernel is to remove whatever bloat can be removed. If you don't care about that bloat, there's no longer a strong reason not to just keep running the huge kernel.
 
Old 11-15-2010, 04:31 PM   #25
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 877

Rep: Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826Reputation: 1826
Quote:
Originally Posted by 2handband View Post
Point of clarification... I executed the vgscan command and successfully activated the logical volumes. Now, are you saying I need to mount the entire filesystem manually? As in:

Code:
mount /etc /mnt/etc
and so on? If this is a dumb question I'm sorry, we're WAY outside of my comfort zone here...
Wait, /etc is on a separate partition?

I think I'm going to have to recommend that reinstall now. ;-) I've never tried putting /etc on its own partition, but can't imagine it would work. Even less so to put /etc on LVM.
 
Old 11-15-2010, 04:34 PM   #26
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,390

Rep: Reputation: Disabled
Quote:
Originally Posted by 2handband View Post
Point of clarification... I executed the vgscan command and successfully activated the logical volumes. Now, are you saying I need to mount the entire filesystem manually? As in:

Code:
mount /etc /mnt/etc
and so on? If this is a dumb question I'm sorry, we're WAY outside of my comfort zone here...
No, what you need to do is picture the layout of your filesystem in your mind, or write it down, like (random example):

Code:
root partition was /dev/myvg/root
/home partition was /dev/myvg/home
/boot partition was /dev/sda2
In such a case you'd run:
Code:
mount /dev/myvg/root /mnt
mount /dev/myvg/home /mnt/home
mount /dev/sda2 /mnt/boot
After which your original filesystem is accessible in full, below /mnt . You should then proceed making proc, sys and dev available below /mnt, using the commands I showed you.

This leads to the situation you'd have immediately after installing Slackware and before rebooting out of the installer. A "chroot" into /mnt will dump you into the fully accessible filesystem, and you can run vi, mkinitrd, lilo and whatever else you need to fix your computer.

Eric
 
Old 11-15-2010, 04:41 PM   #27
brixtoncalling
Member
 
Registered: Jul 2008
Location: British Columbia
Distribution: Slackware current
Posts: 403

Rep: Reputation: 67
Quote:
Originally Posted by volkerdi View Post
Because those filesystems are not needed to load the initrd, and the idea behind the generic kernel is to remove whatever bloat can be removed. If you don't care about that bloat, there's no longer a strong reason not to just keep running the huge kernel.
Well I always happily create an initrd or compile my own kernel so no complaints from me

I wasn't sure if there was a reason -- besides keeping the kernel size down -- that generic didn't have ext in it to begin with.

Thanks, B.
 
Old 11-15-2010, 04:44 PM   #28
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,390

Rep: Reputation: Disabled
For your information: my pal Al G. wrote a "LUKS/LVM rescue" guide here: http://bkaeg.org/blog/archives/2010/...are-excur.html which is meant to go into my Wiki sometime... I always forget to do that. May help in this case to read that article.

Eric
 
Old 11-15-2010, 04:47 PM   #29
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 813

Original Poster
Rep: Reputation: 96
Quote:
Originally Posted by volkerdi View Post
Wait, /etc is on a separate partition?

I think I'm going to have to recommend that reinstall now. ;-) I've never tried putting /etc on its own partition, but can't imagine it would work. Even less so to put /etc on LVM.
No... /etc is not on it's own partition. I just didn't understand Eric's instructions. Sorry, but we're in kinda unfamiliar territory for me.
 
Old 11-15-2010, 04:50 PM   #30
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 813

Original Poster
Rep: Reputation: 96
Quote:
Originally Posted by Alien Bob View Post
No, what you need to do is picture the layout of your filesystem in your mind, or write it down, like (random example):

Code:
root partition was /dev/myvg/root
/home partition was /dev/myvg/home
/boot partition was /dev/sda2
In such a case you'd run:
Code:
mount /dev/myvg/root /mnt
mount /dev/myvg/home /mnt/home
mount /dev/sda2 /mnt/boot
After which your original filesystem is accessible in full, below /mnt . You should then proceed making proc, sys and dev available below /mnt, using the commands I showed you.

This leads to the situation you'd have immediately after installing Slackware and before rebooting out of the installer. A "chroot" into /mnt will dump you into the fully accessible filesystem, and you can run vi, mkinitrd, lilo and whatever else you need to fix your computer.

Eric
Think I get it now; I just hope I can remember how I've got everything set up. I installed this thing last summer...
 
  


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
Unable to see shares on samba server - no authentication access desired (open access) neoelf Linux - Networking 1 06-14-2009 04:18 PM
How to access Access root(/) hard drive attached in Windows XP machine farrukhndm Linux - Software 2 07-29-2008 01:52 PM
Debian Woody: Can't access internet through router, but can access network computers marales314 Linux - Networking 3 06-09-2006 01:33 PM
WIFI WLAN / Cannot access internet but can access the router configuration page?SUSE thomas939 Linux - Wireless Networking 12 12-13-2005 11:28 AM
Samba access by Windows users locking out directory access with Konqueror harry_fine Suse/Novell 1 12-18-2004 06:33 AM


All times are GMT -5. The time now is 04: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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration