Puppy Linux Discussion Forum

[Chris_W]

PeeBee,

Booted Up this morning to try your tweak. But it seems I was premature in signalling success. Got the 'Error No such file or directory' message again before I could apply the change, and neither /root/.config/autostart nor /root/.config/lx-autostart are present.

I haven't looked into these scripts at all, but after all my install configuring and a few reboots, I only once clicked on shutdown - which was after I thought the problem was beat.
Don't know if there is anything specifically different in the shutdown script from the reboot one?

I guess it's tricky to divine the failure mechanism here, but I suspect timing issues. Is it possible to add some logging to these scripts so I can collect results that might give more clues on failure mechanism?

I'm happy to run test scripts, tweak stuff - but my understanding of scripting is currently pretty slight (happy to learn tho).

Also, it looks like I now need to re-install again (based on your advice to do this if I lose these directories). If I were to take a copy of the root/.config/autostart directory next time I'm set up, would this allow me to simply replace it, next time I lose it? - or is there more to it - like variables being changed, etc...

cheers Chris_W

[Marv]

[Chris_W]

Thanks Marv,

At work now, but will try these things later. Will prob boot from another usb & see if I can use that to do the fscheck on the save file, etc.

cheers Chris_W

[Chris_W]

PeeBee, Marv,

OK - so I booted an old pup, to look at my Lxpup 14.03 save file, and low and behold, root/.config/lx-autostart was there! Perhaps I was hasty checking this morning...
I made a backup copy of lx-autostart, shut down, and then booted from the LxPup 14.03 pup.
It came up with the 'Error No such file or directory' message, so I copied lx-autostart back in and renamed to autostart....

I then removed the previous .pet patch and applied the new one, and rebooted ........

It came up with the 'Error No such file or directory' message again.
On replacing autostart, powering down & booting, same result.

Should I try reinstalling, applying the fix .pet, and then testing it?
Any other tests you'd like me to try?


cheers Chris_W

[Chris_W]

ps. I also just booted from a copy of the save file & then had a look at the state of the save file as it had been shut down.

The lx-autostart folder was in place. So I'm thinking the problem is not in the shutdown scripts, just the startup.


Chris_W

[peebee]

[Marv]

[Chris_W]

PeeBee, Marv,

Marv is right.
When I boot up from another pup, and mount the pup save file for this one (or it's backup) I do see the .wh.lx-autostart file in the root/.config folder.

So I guess that means that on loading up into the layered file system, the folder simply just gets cancelled out. And the startup script will simply run, 'not seeing' it...

Marv, I didn't try fscking or e2fscking the save file. I guess when I saw what I was looking for, it didn't appear to be necessary (not to mention those two progs being completely new to me).

PeeBee, I have checked that root/Startup/z-lxde-startup.sh exists and that it is set to executable.

I then assumed that the obvious thing to do is to remove the .wh file from the pup save, shutdown the 'other' pup, and run up 14.03 pup, to see what happens...

Doing that now.... (remembering that this is with the .pet applied with the extra sleep in it)....

And - it all started up fine, including Retrovol.

So I guess that's a win for the new scripting - well done guys!

So now I understand that if one does ever lose root/.config/autostart,
1. shutdown,
2. boot from a different pup (or save file),
3. mount the save file in question, and look to see if root/.config/lx-autostart & its .wh.lx-autostart exist.
4. If they do, delete the .wh file, unmount, and
5. restart using the corrected save file.

cheers - Chris_W

[Chris_W]

PeeBee, Marv

Bad news, back to seeing the same error again - with new script & all.
I can easily fix it now, but it seems it is not removing the possibility of this happening after a session where I use the machine for browsing for an hour then shutdown.

cheers Chris_W

[Marv]

[Chris_W]

Hi Marv

After powering up to no error (I'd deleted the .wh file last night) a session editing spreadsheets, using firefox etc (often enough to create the error after a reboot), I read your post, so added that in.
syslinux.cfg now reads:

default vmlinuz initrd=initrd.gz pmedia=usbflash
pfix=fsck


I then restarted from the menu, but unfortunately still got the same error.

cheers Chris_W

[Chris_W]

Marv,

I had a bit more time, so I booted from another save file, and edited the one I've been used to get it's lx-autostart etc how it should be.

I noticed that on bootup I was getting a message about an unrecognised parameter, so re-read your message, and took the carriage return out of the syslinux.cfg so it all appeared on one line.

I then rebooted with the main save file (which it checked per your change), and everything started correctly. To test it (a little) I opened a bunch of spreadsheets, calculator, firefox - but I can't connect it to the internet here, so couldn't do too much.
On reboot, it came up fine.
However, I'll run it a few sessions over the next few days, to see if it still comes up ok.

cheers Chris_W
(noting potential success here ... hopefully)

[Chris_W]

Marv, PeeBee,

After about 45mins uptime with firefox open to a few pages, then a reboot, back to the same error.
Wondering if it as something to do with layered filesystem -> save file interaction at shutdown.. Also thought it might be to do with auto pup saves during use, but can't see evidence for it...


Chris_W

[Marv]

[Marv]