View Single Post
Old 05-03-2012, 08:02 PM   #11
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by qlob View Post
seaniko7's custom kernel was already installed. All i did to brick it was do
Code:
cd /
./linuxrc 0
OK, understood now -
"messing with /linuxrc" means "using" not "changing the content of"

The key to what happened to your brick can probably be found in the /etc/init.d/kernel_toggle script.

My guess:
That: "set next boot to autoselect kernel" may not be playing well with the custom kernel.

For others who stumble into this thread:

/linuxrc -> /sbin/init
/sbin/init -> /sbin/init.sysvinit
(Not exactly an FHS setup - but that is what it is on the K3, v-3.2.1)

/sbin/init.sysvinit 0
(or, if the executables had their common names/functions: /sbin/init 0)

I admit it, you have me on two counts with that one:
1 - What was the expected (or intended) result; a system shutdown?
2 - What actually happened - since this may well be a modified 'standard' utility.

Background:
/sbin/init -
A special program that runs with the PID of #1 (always) that is the parent of all other processes. (The kernel only runs ONE program, this is it. This program is what runs the dozens to thousands of other processes).

The sysv version of /sbin/init is also responsible for controlling the current runlevel of the system.

The 'normal' way to change run levels is to use a program named /sbin/telinit - which in the sysv version is a link to /sbin/init

So my guess is that you where trying to change your Kindle to runlevel 0 (the runlevel reserved for 'halt').

Looking at /etc/inittab (in K3, v3.2.1) runlevel 0 is defined as: /etc/init.d/rc 0

Which translates to running (in order) all of the scripts in /etc/rc0.d

You can list those, they will run in sorted order, from:
K04framework (the first thing to kill)
through:
K99syslog-ng (the last thing to kill)
followed by (starting):
S50kernel_toggle
S95poweroff

Each of those are links to the actual scripts in ../init.d of the same name (minus the K/S## ordering characters).
With the Amazon/Kindle exception of: poweroff -> ../init.d/halt

Each of the K## scripts will be called with the option: 'stop'
Each of the S## scripts will be called with the option: 'start'

So the end result (seen in /etc/init.d/halt script) of :
./linuxrc 0
__should__ have been a clean shutdown and power off.

Last edited by knc1; 05-03-2012 at 08:13 PM.
knc1 is offline   Reply With Quote