Hello,
i have some questions about puppy...
There is some key to run the terminal? Because i manage my jwmrc for change the menu, then it is hide...
How to run terminal to repair it? How to show the menu if hidden (ALT-F1)?
How to turn off the Xserver?
There is a file to configure the networks? Otherwise how to run the visual configuration by terminal?
Thanks
Some questions: Run the Terminal, confgure the network...
-
Pizzasgood
- Posts: 6183
- Joined: Wed 04 May 2005, 20:28
- Location: Knoxville, TN, USA
You can probably fix JWM by copying in a pristine /root/.jwmrc file from a pup_xxx.sfs file. If you don't have a full-hd install, this can be done by going to /initrd/pup_ro2/root/. Otherwise, you can click the ISO file to mount it, then click the pup_xxx.sfs file to mount that, then grab the file from there.
There should be an icon on the desktop labeled "console" which will open a terminal. Another option is to open a ROX-Filer window and press backquote or right-click->Window->Terminal-Here.
You can press [ctrl]-[alt]-[F2] to switch to another virtual terminal. You'll have to log in though (user: root, pass: woofwoof). To get back to the first one, press [alt]-[F3]. You must use the LEFT [ctrl] and [alt] keys.
To kill X without the menu, press [ctrl]-[alt]-[backspace]. Start it again with either startx or xwin (they are both the same thing in Puppy).
You can also boot with the puppy pfix=nox option to disable autostarting X.
For the gui network wizard, three options:
Click the "connect" icon on the desktop.
Navigate to /usr/local/apps and click the "connect" icon there.
Open a terminal and run /usr/local/apps/Connect/AppRun
There should be an icon on the desktop labeled "console" which will open a terminal. Another option is to open a ROX-Filer window and press backquote or right-click->Window->Terminal-Here.
You can press [ctrl]-[alt]-[F2] to switch to another virtual terminal. You'll have to log in though (user: root, pass: woofwoof). To get back to the first one, press [alt]-[F3]. You must use the LEFT [ctrl] and [alt] keys.
To kill X without the menu, press [ctrl]-[alt]-[backspace]. Start it again with either startx or xwin (they are both the same thing in Puppy).
You can also boot with the puppy pfix=nox option to disable autostarting X.
For the gui network wizard, three options:
Click the "connect" icon on the desktop.
Navigate to /usr/local/apps and click the "connect" icon there.
Open a terminal and run /usr/local/apps/Connect/AppRun
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
Thank you very much... tomorrow i will try.
I have another question... if I can:
I installed puppy on an Ebox, a thin client with IDE and Compat Flash. Puppy is installed on the IDE HDD, but i clone it to the CF (with 'dd if=/dev/hda of=/dev/hdb'). Now if i set the cmos to boot from CF puppy may runs on CF?
Thanks!
I have another question... if I can:
I installed puppy on an Ebox, a thin client with IDE and Compat Flash. Puppy is installed on the IDE HDD, but i clone it to the CF (with 'dd if=/dev/hda of=/dev/hdb'). Now if i set the cmos to boot from CF puppy may runs on CF?
Thanks!
-
Pizzasgood
- Posts: 6183
- Joined: Wed 04 May 2005, 20:28
- Location: Knoxville, TN, USA
I suppose it might. It would be a good idea to open up your menu.lst (assuming you use Grub) and change the pmedia=idehd to pmedia=ideflash. You'll probably also have to fix the paths in Grub from (hd0,0) to (hd1,0) unless you moved Grub itself (since I think Grub names the partitions relative to where it's installed). If there's an actual file on the CF card named "idehd" you should rename it to "ideflash".
Then, if Grub is configured properly, I think it should work. I don't have much experience with CF cards though so I could easily be missing something.
Also, if you used a Full-HD install previously on the HD, you may want to reconsider. Puppy has a special means of handling Flash based drives to prevent premature failure from writing to it often, but it doesn't work with a Full-HD install. I think a Full-HD install should still work, it just might wear out the card faster. Not sure how much faster though. Like I said though, I don't have much experience with CF installs.
Then, if Grub is configured properly, I think it should work. I don't have much experience with CF cards though so I could easily be missing something.
Also, if you used a Full-HD install previously on the HD, you may want to reconsider. Puppy has a special means of handling Flash based drives to prevent premature failure from writing to it often, but it doesn't work with a Full-HD install. I think a Full-HD install should still work, it just might wear out the card faster. Not sure how much faster though. Like I said though, I don't have much experience with CF installs.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
boot parameter pfix=noxGoldEmish wrote:There is way to stop the Xserver loading at startup?
you don't have reboot, just hit CTRL-ALT-F2 to open a second VT, login with
username=root
password=woofwoof
edit with mp
when you have finished CTRL-ALT-F3 gets you back to X
restart X
Will
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]