When I shut down my 1.0.3 multisession disc, it tries to write to the CD but fails, giving an error something like this:

Premature EOF on stdin
Input buffer read error, aborting.

It then just continues shutting down. The odd thing is that its certainly been able to write back to it at least twice before- is there any reason why it might refuse to now? If I start it up, do nothing, and shut down, it goes through the whole writing part without error- but, of course, writes no data.

Erp. It looks like I have been wasting your time rather. When I was messing around trying to get it to write, a line caught my eye as it whizzed past: ¨directories too deep¨. This, of course, reminded me of the bug report on the News page. In short, adding -D to the mkisofs line got it to work fine. Thanks for your help, though.

Edit: Ok, looks like I am having some problems. Both /tmp/rc.reboot and /etc/rc.d/rc.reboot-cd seem to be resetting after reboot- even when the write goes ok. Is there any easy way to make the changes ¨stick¨?

Well- I took a little break from Puppy, and just today I tried your instructions. I´m afraid I can´t tell if they work, because it won´t write, even if I add the -D parameter! I have tried this at least three times, it persists in not working. I even burned a new Puppy, and got all my data off the old one using that prompt during boot- I couldn´t get that to write either.

One thing I noticed when shutting down is that it lists a few files with ¨file exists¨ afterwards- this never used to happen. Are those the ones which are meant to be archived?

Hmm. As far as I can tell, every file that little snippet finds comes up as ¨No¨. I took pictures of it as it shut down- I can attach them, but I´ll have to boot into Windows to get them off my camera, so I´ll add them in a bit.

Oh, I'll need to check how the script works... all those files are prefixed with the CD folder name, for example 2005-10-1-6-5, rather than /root.
So, the test code I supplied won't work.

I'll attempt to do something for 1.0.4, some extra testing of the validity of the entries in the /tmp/listfinalshutdown.txt file.

I've seen the same problem but so far haven't been able to nail down the cause.

I trimmed down a copy of the shutdown script to just the file name collection and burning sections. I believe that it did burn fine when running from the icewm session but it failed when running the full script (with -D) during a normal shutdown. If I remember right it had problems restoring the session from the trimmed down script but I attributed that to open files in the /proc directory. (I am by no means a linux guru so take the above for what it's worth)

I would like to see more error checking in the shutdown script. I think that if there is an error, the script should prompt to save the session in a different manner or return to the session rather than loosing all changes.

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