I've been doing some research, look:
http://murga-linux.com/puppy/viewtopic.php?p=883566
With this rc.sysinit I was able to boot correctly the following puppies:
- slacko 6.3.0 - 'huge' kernel 3.14.55
- precise puppy - old kernel 3.2.48 [no devtmpfs]
- precise puppy - old kernel 3.9.11 [no devtmpfs]
- precise puppy - 'huge' kernel 3.14.55
New puppies use a slightly different rc.sysinit, this rc.sysinit makes 2 become 1.
Details:
* includes code from woof-ce/woof-code/huge_extras/rc.sysinit
* more info that goes into /tmp/bootsysinit.log
* a few tweaks
--
Instructions:
1) Install the pet file in a test install.
Keep using and configuring puppy.
Report whether it's working as expected or not...
Test this rc.sysinit
-
jlst
Test this rc.sysinit
- Attachments
-
- rc_sysinit-20160124-noarch.pet
- (13.61 KiB) Downloaded 93 times
Nothing special.musher0 wrote:Euh... thanks jlst, I'm sure there's a lot of work involved there, but...
what does an "rc.sysinit" do?
It is mainly useful for full installs PUPMODE 2 .
«Give me GUI or Death» -- I give you [[Xx]term[inal]] [[Cc]on[s][ole]] .
Macpup user since 2010 on full installations.
People who want problems with Puppy boot frugal :P
Macpup user since 2010 on full installations.
People who want problems with Puppy boot frugal :P
@Karl_Godt:Karl Godt wrote:Nothing special.musher0 wrote:Euh... thanks jlst, I'm sure there's a lot of work involved there, but...
what does an "rc.sysinit" do?
It is mainly useful for full installs PUPMODE 2 .
Isn't that the script the kernel modules are loaded from? I'd need a script like that
for my new Wheezy Pooches, in which the kernel modules do not load automatically.
Thanks in advance for any pointers.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)