Download your favorite Linux distribution at LQ ISO.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 09-21-2012, 05:02 PM   #1
Registered: Jun 2002
Distribution: Slackware
Posts: 52

Rep: Reputation: 4
Slackware 14 RC5 install image has a typo in boot up message

The install image has a small typo when first bootup. This is from the usbboot.img, I did not try the other.

It says:
In a pinch, you can boot your system from here with a command like:
boot: huge.s root=/dev/sda1 rdinit= ro
Where rdinit should be initrd to avoid loading the initrd image.
Old 09-21-2012, 06:05 PM   #2
Registered: Sep 2009
Distribution: Slackware -current x64
Posts: 372

Rep: Reputation: 73
I thought it always said rdinit?
1 members found this post helpful.
Old 09-21-2012, 08:26 PM   #3
Senior Member
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,913

Rep: Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054Reputation: 1054
That is not a typo. From /usr/src/linux/Documentation/kernel-parameters.txt
	rdinit=		[KNL]
			Format: <full_path>
			Run specified binary instead of /init from the ramdisk,
			used for early userspace startup. See initrd.
1 members found this post helpful.
Old 09-21-2012, 08:31 PM   #4
Registered: Nov 2006
Distribution: Slackware
Posts: 292

Rep: Reputation: 39
It's rdinit. I always used that when fixing broken Slackware installations.
1 members found this post helpful.
Old 09-22-2012, 02:24 AM   #5
Registered: Aug 2010
Distribution: slackware64-current
Posts: 48

Rep: Reputation: 10
Yes, kind of interesting... for example, if you are using an initrd.gz in lilo.conf:

boot: vmlinuz rdinit=/bin/sh

This runs /bin/sh inside the initrd instead of the usual /init script. This gets you a sh shell and nothing that /init normally does happens at all. Then, you can fix something maybe, and manually run /init (exec it so it is pid 1):

exec /init

Then, the system starts normally.

But, "rdinit=" tells the kernel to ignore the initrd and skip along with regular "legacy" boot of the root= device.

Last edited by foobarz; 09-22-2012 at 02:29 AM.
2 members found this post helpful.
Old 09-22-2012, 11:46 AM   #6
Registered: Jun 2002
Distribution: Slackware
Posts: 52

Original Poster
Rep: Reputation: 4
That is something interesting to know. As in my case, I don't need the extra support from initrd, so I used initrd= to skip the loading of it.


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
Slackware install boot cd image files located? AngryAngry Slackware 2 01-23-2011 06:06 PM
SSL version number typo in repository clifford227 Slackware 3 04-01-2010 04:33 PM
fedora 10 install via hard disk got a wrong message!---Missing ISO 9660 image netyq Linux - Newbie 1 01-31-2009 09:28 AM
Typo in slackware-current/source/a/lilo/liloconfig drumz Slackware 7 02-22-2008 12:53 PM
kernel 2.6.17-rc5 with Slackware-stable? uselpa Slackware 10 06-04-2006 06:50 PM

All times are GMT -5. The time now is 02:13 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration