How or where do I configure puppy to NOT start xwin at boot?
How or where do I configure puppy to NOT start xwin at boot?
Hello puppy linux forum users and moderators,I'm trying to get puppy 5.2 to NOT start xwin at bootup time,I want everything elase to load as normal but just no xwin,is there a configuration file I can edit to do this?,your help and knowledge is greatly appreciated thanks
Hello,
Read the instructions at the boot prompt...
Entering "pfix=nox" starts Puppy without the xserver..
It is even in the example given...
Hope that helps...
Read the instructions at the boot prompt...
Entering "pfix=nox" starts Puppy without the xserver..
It is even in the example given...
Hope that helps...
Close the Windows, and open your eyes, to a whole new world
I am Lead Dog of the
Puppy Linux Users Group on Facebook
Join us!
Puppy since 2.15CE...
I am Lead Dog of the
Puppy Linux Users Group on Facebook
Join us!
Puppy since 2.15CE...
Hello,
Go to /mnt/home/boot/grub
Open the file "menu.lst" in a text editor
Find the line that begins with "kernel=" and at the end add:
"pfix=nox" (without the quotes, of course)
Save the file and reboot...
Go to /mnt/home/boot/grub
Open the file "menu.lst" in a text editor
Find the line that begins with "kernel=" and at the end add:
"pfix=nox" (without the quotes, of course)
Save the file and reboot...
Close the Windows, and open your eyes, to a whole new world
I am Lead Dog of the
Puppy Linux Users Group on Facebook
Join us!
Puppy since 2.15CE...
I am Lead Dog of the
Puppy Linux Users Group on Facebook
Join us!
Puppy since 2.15CE...
I thought .png would display and not be a download,sorry bout that[/code]
- Attachments
-
- menu1st.png
- (113.21 KiB) Downloaded 373 times
-
- menu1st.png
- (113.21 KiB) Downloaded 322 times
I bet if you delete xinitrc, the thing won't come up in X!!!ap72 wrote: can I delete or modify some other system file more or less breaking xwin or somthing ,I really don't need it anyway for this particular puppy project,thanks again
Want me to try it??
Curious.. but I never tried it.ap72 wrote:Still scratching my head tho,I wonder just why the pfix=nox don't work on a full install?
RP
Edit /etc/rc.d/rc.local and add the following code. If it works, let me know - I'll explain why it works. If it doesn't work - well, I don't need to explain anything right?
Code: Select all
touch /tmp/bootcnt.txt
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
Stop xwin
To start without xwin, I just remark it out in /etc/profile at the bottom.
Kal
Code: Select all
#want to go straight into X on bootup only...
if [ ! -f /tmp/bootcnt.txt ];then
touch /tmp/bootcnt.txt
# aplay -N /usr/share/audio/bark.au
dmesg > /tmp/bootkernel.log
#exec xwin #Just add the # here
fi
fi
Kal
If you see the code in Kal's posting above, before it runs xwin, it checks whether a file /tmp/bootcnt.txt exists. So the trick is just to create this /tmp/bootcnt.txt (touch /tmp/bootcnt.txt does exactly that) before /etc/profile is run - and rc.local is the right place, as it is run before /etc/profile.jamesbond wrote:Edit /etc/rc.d/rc.local and add the following code. If it works, let me know - I'll explain why it works. If it doesn't work - well, I don't need to explain anything right?Code: Select all
touch /tmp/bootcnt.txt
And yes, this is what pfix=nox actually does. Pfix=nox doesn't work in full install because the code that interprets this only exists in initrd.gz, and full-install doesn't use initrd.gz. (In fact, all other puppy boot parameters will not work in full install).
cheers!
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]
I only offered my way as an alternative because jamesbond was not sure it would work.
Kal
I have finally tested jamesbond’s way, it does work and is more technical, but, in the end I believe they both work. I’ve just been using my simple way for years. Good work jamesbond.If it works, let me know - I’ll explain why it works. If it doesn’t work - well, I don’t need to explain anything right?
Kal
Thanks to put light on the bootcnt.txt file .
I must say , that I thought it would have something to do with ¨bootcritical¨ or something like that ( to be read from "pfix=rdsh" mode .... ) .
But must be somethig like "bootconsoleandterminal" .
I still will have to look a lot into /etc/rc.d and for myself I would have placed `xwin` in the rc.sysinit file and not in a configuration file, that is read all the time when launching a[n] rxvt .
On the one hand I had no cause to delete this always empty bootcnt file , but on the other hand I could have done it and would have been wondering about messages like ¨X already running on display 0¨
I must say , that I thought it would have something to do with ¨bootcritical¨ or something like that ( to be read from "pfix=rdsh" mode .... ) .
But must be somethig like "bootconsoleandterminal" .
I still will have to look a lot into /etc/rc.d and for myself I would have placed `xwin` in the rc.sysinit file and not in a configuration file, that is read all the time when launching a[n] rxvt .
On the one hand I had no cause to delete this always empty bootcnt file , but on the other hand I could have done it and would have been wondering about messages like ¨X already running on display 0¨