LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
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 08-27-2012, 06:09 AM   #16
kikinovak
Senior Member
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 1,960

Rep: Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978Reputation: 978

Quote:
Originally Posted by brianL View Post
I do it after the first reboot, using /usr/share/mkinitrd/mkinitrd_command_generator.sh as a guideline. Is there any advantage to doing it before the first reboot?
One less reboot, since you'd have to configure LILO accordingly. When you have more than twenty machines to install (as I do right now in a school), this sort of detail is a timesaver. (Thus I can spend the time saved playing minesweeper or posting on LQ )
 
Old 08-27-2012, 06:20 AM   #17
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,145
Blog Entries: 52

Rep: Reputation: Disabled
Quote:
Originally Posted by kikinovak View Post
When you have more than twenty machines to install (as I do right now in a school), this sort of detail is a timesaver. (Thus I can spend the time saved playing minesweeper or posting on LQ )
Ah, yes, never thought of that. I've only got three.
 
Old 08-27-2012, 09:24 AM   #18
mrascii
Member
 
Registered: Jun 2012
Location: on the Net
Distribution: Slackware
Posts: 100

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Ramurd View Post
afaik you need to build an initrd.gz also for LVM; at least if your entire setup is on LVM. iirc I would get kernel panics if I didn't build the initrd before the first reboot... A simple mkinitrd -k <kernel version> -f <filesystem> -r <root device> -h <resume from hibernate device> -L -o <outputfile> is all that's needed, but still, it's needed.
Exactly right. I should have made it clear that I encrypted /, /home and swap. Even booting huge.s an initrd is needed. In addition, following the recovery instructions to boot using "root=/dev/sdax" will not work if root is encrypted. The / volume must first be decrypted and made active then /proc and /sys mounted before lilo can be used to write a new lilo.comf file.

DNA
AKA mrascii
 
Old 08-27-2012, 09:33 AM   #19
mrascii
Member
 
Registered: Jun 2012
Location: on the Net
Distribution: Slackware
Posts: 100

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by T3slider View Post
I'm pretty sure the generic kernel+initrd was solving the problem of on-demand module loading with configurable options. The huge kernel solved installation with a single monolithic kernel rather than having to ship several but its purpose in a running system has always been as a backup.

As to the question at hand, if you're using LUKS encryption then you're expected to read README_CRYPT.TXT anyway, which gives you more than enough information including how to create a satisfactory initrd. I think that file is more appropriate since it is more specific (and thus trumps the more generic README.initrd). Just my opinion though.
Yes, The README_CRYPT.TXT is excellent and your point his well taken, T3slider. However, a sentence in README.initrd would remind anyone to use the instructions in the README.CRYPT.TXT instead if they are using luks and LVM. I purposely used the mkinitrd command in README.initrid upgrading from RC2 to RC3 to see if it would break my test box which it did and to make sure I could recover from a non-bootable encrypted LVM if needed.

DNA
AKA mrascii
 
Old 08-29-2012, 01:35 AM   #20
ReaperX7
Senior Member
 
Registered: Jul 2011
Location: California
Distribution: LFS-7.6, Slackware 14.1, FreeBSD 10.1
Posts: 3,851
Blog Entries: 15

Rep: Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191
Choosing a kernel was, at one time, included originally in the Slackware installation, but the scripts were removed possibly because it was confusing to do so and using the generic kernel with initrd.gz was considered a customization feature that often proved unnecessary for common systems.

Plus with the addition of rerunning LILO each time you reconfigured the kernel, you would also have to regenerate the initrd.gz with the specific modules you needed if you upgraded the kernel. Huge eliminated the need to hunt down and trial and error solve which modules were needed at load time so it became the default.

The last time I saw this was between releases 10.0 and 13.0 before EXT4 was finalized as the recommended default Slackware filesystem. Haven't seen it since.
 
Old 08-29-2012, 12:50 PM   #21
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,298

Rep: Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722
From -current's CHANGES_AND_HINTS.TXT (and as far as I know CHANGES_AND_HINTS.TXT from at least 12.0, which introduced the huge/generic split):
Code:
Use one of the provided generic kernels for daily use.  Do not report
  bugs until/unless you have reproduced them using one of the stock 
  generic kernels.  You will need to create an initrd in order to boot
  the generic kernels - see /boot/README.initrd for instructions.
  The huge kernels are primarily intended as "installer" and "emergency" 
  kernels in case you forget to make an initrd.
The generic kernel replaced the myriad of specific kernels shipped with pre-12.0 Slackware, and was always meant to be used as the standard kernel. Even in 12.0's CHANGES_AND_HINTS.TXT it mentions the huge kernel's use as primarily an install kernel. Huge has always been the default kernel because it requires no setup, but it has always been advised to switch to the generic kernel. An initrd should be nothing new to those using post-11.0 Slackware.
 
Old 08-29-2012, 04:49 PM   #22
ReaperX7
Senior Member
 
Registered: Jul 2011
Location: California
Distribution: LFS-7.6, Slackware 14.1, FreeBSD 10.1
Posts: 3,851
Blog Entries: 15

Rep: Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191Reputation: 1191
The good thing is we do have a choice.
 
Old 08-30-2012, 02:25 PM   #23
ottavio
Member
 
Registered: Nov 2007
Posts: 312

Rep: Reputation: 46
Quote:
Originally Posted by kikinovak View Post

If you stay with the huge kernel, just look out for "unsupported features" in your boot messages.
I am using the huge kernel but nothing here:
Code:
root@local:~# grep -i 'unsupported features' /var/log/dmesg 
root@local:~# grep -i 'unsupported feature' /var/log/dmesg 
root@local:~# grep -i 'unsupported' /var/log/dmesg 
root@local:~#
 
  


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
[SOLVED] Linux\Slackware Suggested Reading? YourCyborg Slackware 11 10-04-2011 09:57 AM
initrd creation on update breaks dm-drives almatic Debian 8 11-26-2008 01:15 PM
update initrd cccc Debian 3 11-03-2008 05:33 AM
Is it possible to update the pxe network install initrd.img and vmlinuz ? lets-eat-gary Fedora 1 08-22-2006 05:54 AM
Slackware suggested partition sizes? Nikon01 Slackware 8 07-17-2003 09:22 AM


All times are GMT -5. The time now is 05:26 PM.

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