Page 1 of 1
1.0.5 bugs
Posted: Wed 28 Sep 2005, 08:59
by BarryK
Install to hard drive, option 2.
cannot find X.
See this thread:
http://www.murga.org/~puppy/viewtopic.php?t=2495
I cannot reproduce this bug.
One thing. During bootup of the live-CD, /usr is temporarily a link to /.usr_cram, then a bit later the directory /usr is created and unionfs is used to join /.usr_cram and /root/.usr onto /usr.
Maybe something has gone wrong when booting the live-CD.
Check to see that you do have an actual /usr directory, not a
symlink.
There must be something in your setup that interrupts the normal logic of the boot script and prevents that second step.
If I type "df" I get this:
Code: Select all
Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 513688 57112 456576 11% /
tmpfs 513688 57112 456576 11% /
/dev/hda4 31894064 30057728 216184 99% /mnt/home
/dev/loop1 507749 308823 177955 63% /root
/dev/loop0 46528 46528 0 100% /.usr_cram
none 554277 355351 177955 67% /usr
Does it differ for you?
(note, in rxvt, just drag to highlight text, it will automatically
go into the clipboard)
Posted: Wed 28 Sep 2005, 12:06
by Guest
I get this error using option 2 install during step 5.
Code: Select all
Now copying files and directories...
cp: cannot stat `/proc/self/fd/3': No such file or directory
...done.
Since it doesn't copy, it goes along rather quickly & cannot find X after rebooting to hdd.
df yields this after install, but before reboot.
Code: Select all
# df
Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 128280 60672 67608 47% /
tmpfs 128280 60672 67608 47% /
/dev/loop0 46528 46528 0 100% /.usr_cram
Posted: Wed 28 Sep 2005, 12:28
by keenerd
I posted this on another thread, but is the /usr symlink deleted before copying /usr ? If it isn't, the copy fails.
Posted: Wed 28 Sep 2005, 13:35
by BarryK
df yields this after install, but before reboot.
Code:
# df
Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 128280 60672 67608 47% /
tmpfs 128280 60672 67608 47% /
/dev/loop0 46528 46528 0 100% /.usr_cram
I presume you mean that you ran df while still running from the live-CD.
What you get shows something is wrong.
is this a normal CD. Not running as multi-session?
There is no pup001 file. The partition containing the pup001
file should be mounted on /mnt/home.
So, Puppy is running totally in ramdisk.
Is this the case for the other people getting this bug?
Posted: Wed 28 Sep 2005, 17:01
by Guest
BarryK wrote:
I presume you mean that you ran df while still running from the live-CD.
What you get shows something is wrong.
is this a normal CD. Not running as multi-session?
There is no pup001 file. The partition containing the pup001
file should be mounted on /mnt/home.
So, Puppy is running totally in ramdisk.
Is this the case for the other people getting this bug?
Sorry Barry, I should have stated that the drive was unprepared/unformatted, so it was only in ram. Manually deleting /usr & then copying /usr files as other threads mention works fine.
Posted: Wed 28 Sep 2005, 19:25
by flavour
ok, am now on the eagerly-anticipated 1.0.5 final
1st bug:
JWM restart is using the destructive method of <Program> 'restartwm jwm' isntead of the nicer <Restart>
F
Posted: Wed 28 Sep 2005, 23:10
by BarryK
Okay (grrr), I didn't realise that you guys had booted the
live-cd only in ram.
Now I know how to fix it.
Would you kindly repeat the install, using the attached script,
doing exactly as before, booting up only in ram.
That should fix it.
If it does, I'll announce it on the news page and also upload the iso file again.
You can't copy install-hd2.sh to /usr/sbin as /usr is not
writable.
So run it directly:
# gunzip install-hd2.sh.gz
# ./install-hd2.sh
Posted: Thu 29 Sep 2005, 00:30
by Guest
BarryK wrote:Okay (grrr), I didn't realise that you guys had booted the
live-cd only in ram.
Now I know how to fix it.
Would you kindly repeat the install, using the attached script,
doing exactly as before, booting up only in ram.
That should fix it.
If it does, I'll announce it on the news page and also upload the iso file again.
You can't copy install-hd2.sh to /usr/sbin as /usr is not
writable.
So run it directly:
# gunzip install-hd2.sh.gz
# ./install-hd2.sh
Running the above script as "sh install-hd2.sh" it ends with the error...
Code: Select all
chmod: /tmp/boot/boot/grub/menu.lst: No such file or directory
/usr/sbin/grubconfig: cannot create /tmp/grubconfig/null: No such file or directory
however the result is perfect, rebooted into a brand new puppy 1.0.5
Thanks Barry!!
Posted: Thu 29 Sep 2005, 02:32
by BarryK
chmod: /tmp/boot/boot/grub/menu.lst: No such file or directory
/usr/sbin/grubconfig: cannot create /tmp/grubconfig/null: No such file or directory
That's something to do with the grubconfig script.
Well, at least it still works!
Posted: Thu 29 Sep 2005, 04:55
by Previously known as Guest
BarryK wrote:chmod: /tmp/boot/boot/grub/menu.lst: No such file or directory
/usr/sbin/grubconfig: cannot create /tmp/grubconfig/null: No such file or directory
That's something to do with the grubconfig script.
Well, at least it still works!
Yes indead, many thanks!
After posting above as "Guest" ...and lurking for months... ++
I'm finally registered on Puppy forums.
PkaG
Posted: Thu 29 Sep 2005, 18:35
by mouldy
ignore
Posted: Sat 08 Oct 2005, 00:06
by Guest
Hello!
I thought I would never see the day when Puppy Bug Report would be a sticky on the forum. I had too many expectations from 1.0.5
I am getting the error at the end of session when I am saving it that
can not sort Directory xyz and EOF or something and reboots
In good old days of 1.0.4, if I had such a problem, I used to use bkup2cd and used to write my sessions. Not the case with 1.0.5 as I saw someone reported a bug in bkup2cd which I am experiencing too.
BTW I run puppy on a hard drive less computer with AMD AthelonXP 2100, 700+ of DDR Ram and nVidea 128mb AGP card
Dear Barry, Please help, I don't want to give up on this New Puppy so soon