How to Modify the Boot Process in Puppy 5.7?

Using applications, configuring, problems
Post Reply
Message
Author
fgluck
Posts: 2
Joined: Mon 28 Apr 2014, 19:51

How to Modify the Boot Process in Puppy 5.7?

#1 Post by fgluck »

I need to make some modifications to the boot process for Puppy 5.7. Specifically, I want to know what files Puppy uses for the boot process and what order they are executed in.

Can somebody point me toward where this is written down?

I am working toward a configuration that will be a Kiosk with Firefox that supports printing.

The Kiosk would:

Boot and start the Graphical Server
Start Firefox immediately after the GUI starts but not start the window manager.
When FFX is exited, it would immediately restart to a known configuration.

I found a couple of write ups about this but only for older versions of Puppy.

User avatar
8-bit
Posts: 3406
Joined: Wed 04 Apr 2007, 03:37
Location: Oregon

Re: How to Modify the Boot Process in Puppy 5.7?

#2 Post by 8-bit »

fgluck wrote:I need to make some modifications to the boot process for Puppy 5.7. Specifically, I want to know what files Puppy uses for the boot process and what order they are executed in.

Can somebody point me toward where this is written down?
...
Start Firefox immediately after the GUI starts but not start the window manager.
My question to you is will Firefox run without a window manager?

If I boot with the option of pfix=nox, I am left at a command prompt.
Then typing "xwin jwm" gives the desktop.
But what happens if one instead just types "firefox"?

User avatar
saintless
Posts: 3862
Joined: Sat 11 Jun 2011, 13:43
Location: Bulgaria

Re: How to Modify the Boot Process in Puppy 5.7?

#3 Post by saintless »

8-bit wrote:Then typing "xwin jwm" gives the desktop.
But what happens if one instead just types "firefox"?
I'm not sure if this will help fgluck but it is related to the question.
If you boot to command prompt in Debian and type:

Code: Select all

xinit firefox
Firefox will start without active WM. Only background terminal messages with Firefox window will be active. In fact I'm typing this from Dillo started this way in Debian.
I don't know how will be possible to do the same in Puppy. Even DPup does not behave this way.

Toni

cthisbear
Posts: 4422
Joined: Sun 29 Jan 2006, 22:07
Location: Sydney Australia

#4 Post by cthisbear »

Newer release.
" Puli is a high security, "kiosk" flavor of pemasu's
Upup Precise v3.8.3.1, intended to boot from a USB pendrive and
run safely even if the boot device is unplugged. "

http://murga-linux.com/puppy/viewtopic.php?t=88691

Maybe worth a look at.

"""""""

There are a few Puppy Kiosk versions around.

How to Create a Kiosk using Racy 5.2.2

http://murga-linux.com/puppy/viewtopic.php?t=75519

""""

How to make a Precise Puppy 5.4 kiosk

http://murga-linux.com/puppy/viewtopic.php?t=81701

"""""

http://www.canbike.ca/off-topic/linux/c ... ition.html

" Why the Can Bike OS (5.5): Kiosk Edition?
The primary reason was the desire to instantly turn a computer into a web kiosk for kids and guests, while protecting the contents of the hard drive.

It runs great on older hardware and instantly turns it into a web browsing kiosk
Simply place the live-cd into the CD/DVD drive.
Boot the computer from the disc drive and wait for it too load."

"""

etc....Chris.

fgluck
Posts: 2
Joined: Mon 28 Apr 2014, 19:51

But... Where do I find how the boot process works?

#5 Post by fgluck »

Thanks so much for all the info -- I will check it out.

But can someone point me to an overview of how the boot process works and what files are involved in the boot process and what order they are processed?

Many Thanks...

Peterm321
Posts: 411
Joined: Thu 29 Jan 2009, 14:09
Location: UK

#6 Post by Peterm321 »

There is a brief description of the boot sequence in the file:

/etc/rc.d/README.txt

I have altered the boot process myself and the two key files for me are

/etc/rc.d/rc.sysinit

and

$HOME/.xinitrc

rc.sysinit mounts certain filesystems and loads kernel modules.

$HOME/.xinitrc gets run when Xorg starts up, it would appear that changing this file is one way to disable the windowmanager (typically JWM). I believe that there is a startup folder that can be used to autostart applications, for me it is easy enough to start them from $HOME/.xinitrc

Post Reply