LinuxQuestions.org
Register a domain and help support LQ
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-26-2012, 10:27 PM   #1
mrascii
Member
 
Registered: Jun 2012
Location: on the Net
Distribution: Slackware
Posts: 100

Rep: Reputation: Disabled
Suggested update to README.initrd in Slackware 14


Using the mkinitrd command in the README.initrd file linked to in the /boot directory will not work with a luks-encrypted file system. The result will be a system that won't boot.

I suggest that a line be added either giving the correct command or a reference to the README_CRYPT.TXT which includes the correct command.

DNA
AKA mrascii
 
Old 08-26-2012, 10:50 PM   #2
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, Slackware-14.1, PCBSD-10.0
Posts: 2,863
Blog Entries: 15

Rep: Reputation: 743Reputation: 743Reputation: 743Reputation: 743Reputation: 743Reputation: 743Reputation: 743
People still use an initrd.gz file? I though the huge kernel solved that issue entirely.
 
Old 08-26-2012, 11:14 PM   #3
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.0
Posts: 2,242

Rep: Reputation: 614Reputation: 614Reputation: 614Reputation: 614Reputation: 614Reputation: 614
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.
 
Old 08-26-2012, 11:14 PM   #4
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,507

Rep: Reputation: 405Reputation: 405Reputation: 405Reputation: 405Reputation: 405
huge kernel does solve that problem, but for daily usage, people tends to use generic kernel
 
Old 08-26-2012, 11:28 PM   #5
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,805

Rep: Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810
Sure people use initrd.gz files. Not everyone needs everything included in the huge kernel. Yes, you could compile your own kernel with everything you need and no more but it is simpler and faster just to use the generic kernels with an initrd.gz.
 
Old 08-27-2012, 12:03 AM   #6
kikinovak
Senior Member
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: ElementaryOS, Ubuntu LTS, Slackware
Posts: 1,497

Rep: Reputation: 682Reputation: 682Reputation: 682Reputation: 682Reputation: 682Reputation: 682
Quote:
Originally Posted by ReaperX7 View Post
People still use an initrd.gz file? I though the huge kernel solved that issue entirely.
First thing I do after hitting "EXIT Slackware Setup", even before the first reboot, is chroot into my freshly installed Slackware and build an initrd.

If you stay with the huge kernel, just look out for "unsupported features" in your boot messages.

Besides, with some Intel graphics cards, you need to include i915 and intel_agp into your initrd for KMS to work.
 
1 members found this post helpful.
Old 08-27-2012, 12:12 AM   #7
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,805

Rep: Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810
Quote:
Originally Posted by kikinovak View Post
First thing I do after hitting "EXIT Slackware Setup", even before the first reboot, is chroot into my freshly installed Slackware and build an initrd.
Snap, I do exactly the same!
 
Old 08-27-2012, 02:07 AM   #8
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,428

Rep: Reputation: 407Reputation: 407Reputation: 407Reputation: 407Reputation: 407
Quote:
Originally Posted by ReaperX7 View Post
People still use an initrd.gz file? I though the huge kernel solved that issue entirely.
Stop pulling my leg.
 
Old 08-27-2012, 03:23 AM   #9
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 6,897
Blog Entries: 51

Rep: Reputation: Disabled
Quote:
Originally Posted by kikinovak View Post
First thing I do after hitting "EXIT Slackware Setup", even before the first reboot, is chroot into my freshly installed Slackware and build an initrd.
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?

Last edited by brianL; 08-27-2012 at 03:25 AM.
 
Old 08-27-2012, 03:35 AM   #10
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,805

Rep: Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810
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? Also it means you don't even have to install the huge kernel at all, even for first boot (granted you could have also avoided this by booting from the huge kernel on the Live CD at the isolinux boot prompt but configuring everything up front seems neater).

In my case I don't use Lilo (and hence don't install it) any more. Instead I use extlinux. I manually setup and configure extlinux at the same time as making my initrd. By doing it all immediately after install, the whole boot process is configured and complete, without having to boot from the CD or USB disk again.

Last edited by ruario; 08-27-2012 at 05:17 AM. Reason: added a comma and deleted a word
 
Old 08-27-2012, 03:36 AM   #11
GazL
Senior Member
 
Registered: May 2008
Posts: 3,322

Rep: Reputation: 881Reputation: 881Reputation: 881Reputation: 881Reputation: 881Reputation: 881Reputation: 881
Quote:
Originally Posted by ruario View Post
Snap, I do exactly the same!
+1
Along with moving /tmp into a tmpfs.
 
Old 08-27-2012, 03:39 AM   #12
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,805

Rep: Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810
Quote:
Originally Posted by GazL View Post
Along with moving /tmp into a tmpfs.
I don't do this but have been considering it of late. Perhaps I will when I do my first clean install of Slackware 14.
 
Old 08-27-2012, 04:04 AM   #13
Ramurd
Member
 
Registered: Mar 2009
Location: Rotterdam, the Netherlands
Distribution: Slackwarelinux
Posts: 542

Rep: Reputation: 74
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.
 
Old 08-27-2012, 04:43 AM   #14
zerouno
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 254

Rep: Reputation: 69
Why not to add mkinitrd&generic kernel to the slackware installer?
 
Old 08-27-2012, 05:05 AM   #15
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,805

Rep: Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810Reputation: 810
Quote:
Originally Posted by zerouno View Post
Why not to add mkinitrd&generic kernel to the slackware installer?
I believe the team have looked at this. I recall the following discussion from another thread.

Quote:
Originally Posted by Richard Cranium View Post
Actually, the installer already should know what filesystems you intend to use for your partitions. It asks you fairly early in the process.

How many disk drive controllers are you going to build into the generic image? The installer doesn't know about that.

I think you'll end up with what we already have: a kernel with everything in it so that you can do an initial install and a generic kernel with the bare minimum to boot with which you use an initrd.

Unless someone can write a script that would troll through /sys to figure out what minimum set of modules should be loaded by initrd to allow you to boot into runlevel 3.
Quote:
Originally Posted by Alien Bob View Post
The script /usr/share/mkinitrd/mkinitrd_command_generator.sh does just that.
Quote:
Originally Posted by Richard Cranium View Post
Cool. Does the installer ask if you want to run this? (I haven't done a full install in quite a while.)
Quote:
Originally Posted by Alien Bob View Post
No, but internally, the team had this working end of 2008 already. It's just never gone public.
Not sure why it was never included in the installer, though presumably they hit an problem.

In any case they are certainly aware this would be a nice to have addition. So I suspect it could indeed turn up one day. As for the exact time scale of when that it is, I suspect it it like everything else in Slackware. It'll appear when it is ready.

Last edited by ruario; 08-27-2012 at 05:14 AM. Reason: Initially I missed out one of the quotes from the previous thread
 
  


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


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