No need to change the rc.shutdown, but the deletimg /tmp/* is required in the rc.sysinit._________________Downloads for Puppy Linux http://shino.pos.to/linux/downloads.htmlLast edited by shinobar on Sat 28 Apr 2012, 11:18; edited 1 time in total

I can't sync with woof right now. Rolling back pupsaveconfig is a safer fix. Isn't the goal of pupsaveconfig to work with older versions of woof? If not, it would be good to put a note in the thread so devs to get the right version for their puplet.

Yes, pupsaveconfig works with old wooof but also with the old woof bug.

If the finding of the moving 'rf -f /tmp*' from shutdown to the init is real solution, we are better to move. (but i am not quite sure what is the real cause.)_________________Downloads for Puppy Linux http://shino.pos.to/linux/downloads.html

That one change is fine but I'm likely to introduce a lot of new problems by only partially syncing. I'm not convinced the rm -rf thing is the issue though. Having it in rc.shutdown worked fine in the past and should continue to work.

I have been using Saluki from the start. By doing a frugal install with only a few problems. Found that it was easier to delete the older install and make a total new one.
Only once did I have a problem with it not shutting down after a frugal install. All it did was boot back to the desktop and when I wanted to shut down it did with no problem.
Now I have it install on four system with each a different setup. No problem with any and love to use it.

Reading the manpage of mingetty i found that it seems to need access to /var[/run/utmp] .

Seems that /var is by default

drwxr-xr-x and owned by root:root

i am not running Puppy in other USER mode than root ...
except few times to try to reproduce sound issues posted on the forum which seems to have been fixed by a udev rule to chown /dev directory ..
(i did it with /etc/init.d/alsa) ..

This is not a vital post. Just reporting a curiosity.
I was exploring playdaz's latest iteration of Lupu, scrolling thru the pets I've stored for something else and noticed a Hulu pet I had forgotten I downloaded sometime ago. So I installed and started it in Lupu. I ran, but complained about being out of date: offering to "update." Figuring that could break something, I deleted the Hulu pet, but --then being in Lupu-- decided to download the current "ubuntu" version from ubuntu. That ran without a hitch.
Now, wondering if it would run in Saluki, I booted into Saluki 20, clicked install and then opened Hulu. It complained about being unable to locate Flash, offering the alternatives of your manually editing Hulu's config file (/.huludesktop), or downloading flash.
On that Saluki, I have installed firefox from Saluki's repo, Opera downloaded from Opera to /mnt/home and run via a hand-made pet which created a script in /my-applications/bin and a desktop file, and Google-Chrome-Stable.sfs from Saluki's repo. All played flash files. I had assumed that Opera was employing the same flashplayer.so as firefox, which from prior experience had been installed to /usr/lib/mozilla/plugins, and Google-Chrome was using its own. Uncertain what downloading another flash-player would do to my system, I decided to edit /.huludesktop, opening it in geany.
Scrolling revealed a line, which at the time read “flash_location = (null). As I was uncertain that my memory was accurate regarding the location of the flash-player.so, I opened pfind and entered the argument “flash.” Except for an .so relating to libreoffice –which I didn't test:enables running flash files in impress?-- the only flash-player.so disclosed was /opt/google/chrome/libgcflashplayer.so. Note the gc in that name. After typing that into .huludesktop, hulu opened and ran.
Did I miss it? Is Puppy –or only Saluki-- locating the flash-player.so in /opt/google/chrome rather than, for example, /usr/lib/mozilla/plugins?

Reading the manpage of mingetty i found that it seems to need access to /var[/run/utmp] .

Seems that /var is by default

drwxr-xr-x and owned by root:root

i am not running Puppy in other USER mode than root ...
except few times to try to reproduce sound issues posted on the forum which seems to have been fixed by a udev rule to chown /dev directory ..
(i did it with /etc/init.d/alsa) ..

Remember that mingetty is not actually running if there is an open shell on tty1. It gets executed by init when the tty1 shell exits. Once mingetty opens a new shell, it exits. So its the shell that may or may not be getting killed - not mingetty.

If the new shell opens while /tmp/bootcnt.txt does not exist, then X starts - otherwise you get a prompt.

I think that would be a good idea unless it is possible to work out why it is buggy. I guess people who are more experienced with usb installs would have already learned to ignore this option. Or does it apply to all "FULL" installs, not just non_save_to_file usb installs?

Are you referring to the looping back to desktop problem? If so, here is how I generated the problem repeatedly on my Acer netbook:
Boot Saluki 20 from CD, pfix=ram
Insert blank usb stick
Run universal installer and when it brings up Gparted create 3 partitions: part 1: Fat32 for data, part2: Ext2 "boot", part 3: swap. (no idea if this particular partition config has any effect or not)
Install to partition 2. Accept default mbr, wipe all files. Choose NOT to load files to ram at boot time.
Shutdown, remove CD drive.
Reboot, change to en_AU (two step process as you have to select standard en english first, then select en_AU from the next list that pops up, then allow restart of X. Then shutdown, then accept "legacy" save, and select the usb ext2 partition. (512Mb)
Wait long time till shutdown.

Future reboots/shutdowns should show the looping reboot problem. (although I have seen variable behaviour - sometimes it succeeds on the very first shutdown after locale config, then fails on later shutdowns. Test thoroughly)

EDITED Needed to clarify that this was my test with Saluki 20 only - I am just about to start testing with Saluki 21 next. Also clarified that my chosen locale was Australian english. Added the step to NOT copy files into ram at boot time.Last edited by greengeek on Sat 28 Apr 2012, 20:20; edited 2 times in total

1) It seems that it is an overall problem that should be discussed in a separate general thread .
2) I am responsible to some adjustments lately
and after looking inside the code i can only guess :

2a) regular sed depends on locale settings .. especially LC_ALL and as stated in the html of the source that might not compile because the devx might not include many text formatting binaries LC_COLLATE and LC_CTYPE

2aa) LC_COLLATE and LANG are defined in /etc/profile (login,*getty) and should get adjusted by the various Puppy locale setting scripts (chooselocale,firstrunwizard,...)

2ab) I don't actually have a mount output example for PUPMODE=6 (save to entire partition) .. it might be possible that the home partition gets unmounted or remounted read-only too early

2ac) busybox can be configured with locale(s) or utf-8 option(s) -> init,umount

2b) the killzombie function of rc.shutdown might catch a defunct process and might kill a process that should better not be killed ??? (ps -A -H in urxvt could reveal them before selecting a shutdown button in the menu)

2c) I have no idea about gettext and eval_gettext .. ??

2d) rc.shutown attempts to killall X (another time) .. ??

2e) the whole LAN mount things are unknown to me, so i don't know if bringing down the network attached to local routers could be responsible for anything (especially mounted puppy archive files (.sfs,.2fs) on network shares)

Just in case it helps to narrow down the problem I thought I would mention the following:

If I install Gray's Racy 5.2.2 NOP in the same way as I have been installing Saluki 20 I do not have any shutdown problems at all.

NOP 5.2.2 seems to use a different routine for specifying the locale - I can choose en_AU on the first stage - it does not require me to go to a second screen to select en_AU, Also, it does not offer the "Legacy" prompt to do the install to partition. I have now tried both the "save to file" and "save to partition" with NOP 5.2.2 and they both work fine.

EDITED have corrected spelling of aus locale to en_AU to reflect choice of Australian english.
.Last edited by greengeek on Sat 28 Apr 2012, 20:25; edited 5 times in total

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum