Fatdog64-710 Final [4 Dec 2016]

[Keef]

I'm fairly new to FatDog, having only recently got a 64bit laptop. I've installed PeasyWifi just to test. It works well, but on shutdown/reboot, after exiting X, udhcpc starts running and is looking for a lease - tries three times then gives up and the shutdown completes.

Dell XPS 1530
Processor : 2x Intel(R) Core(TM)2 Duo CPU T7250 @ 2.00GHz
Memory : 2048MB (240MB used)
Network controller : Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
kernel module iwl3945

[rcrsn51]

@Keef: Are you seeing this in the black-and-white console messages at shutdown? I have run PWF many times in many Puppies and never seen that happen.

You are the first person to ever report this, so I don't know how common it is.

It sounds like udhcpc never got a proper lease on the IP address and is trying to renew it.

The obvious solution would be to kill the udhcpc daemon during the shutdown sequence, but I don't know where.

I will think about this.

[Edit] Is this with wired or wireless connections? When Marv and I were switching the DHCP client from dhcpcd to udhcpc, we discussed whether it was even necessary to keep the udhcpc daemon running. The only reason appeared to be for allowing an automatic lease renewal during a session.

[Keef]

rcrsn51

Yes, in the console after exiting X. Manually trying to stop it (Ctrl + C) doesn't help - it shows the prompt then restarts (or probably just continues).
I have a wifi connection only.
I have tried PeasyWifi previously on Slacko/Tahr 32bit and not had this problem.

[rcrsn51]

I have tried PeasyWifi previously on Slacko/Tahr 32bit and not had this problem.

Wow. The only difference between Puppy and Fatdog would be the version of busybox udhcpc. But I don't see the problem in Fatdog either.

Try this. Before shutting down, run the command: killall udhcpc.

Does this get you a clean shutdown?

I have tried PeasyWifi previously on Slacko/Tahr 32bit and not had this problem.

Was this v4.1 with udhcpc?

[Keef]

rcrsn51

I'd tried killing udhcpc before with no luck. Tried it again, but same result.
I'm not sure which version I used previously - since moving to a new laptop, both Slacko and Tahr have had fresh installs.

If I'm the only problem child I would not worry about it too much (although I know these quirks are irritating if a cause cannot be found).

[rcrsn51]

@Keef: I may have found the problem with Fatdog.

Open the file /etc/rc.d/rc.shutdown

Comment out line 131

Code: Select all

#/etc/rc.d/rc.network stop

The PWF version of rc.network is not built to recognize the "stop" option, so it would try to run at shutdown.

[Edit] This same problem will occur in some (all?) versions of Puppy. But since PWF introduced its own rc.network in 2014, this is the first report. If you can confirm that the above fix works, I will give you a better fix.

[Keef]

Yes, that was a success.

[rcrsn51]

Yes, that was a success.

Excellent. Here is the better solution. Open /etc/rc.d/rc.network and make this change at the top

Code: Select all

#!/bin/sh
#rcrsn51 2014-08-23

[ "$1" = "stop" ] && exit #to abort calls to rc.network stop

When I started working on the PWF version of rc.network in 2014, I hunted through the current Puppy rc.network and rc.shutdown scripts, and couldn't find a reason to make it a start|stop|restart type of service. This has turned out to be a mistake.

In regular Puppies, the messages don't appear and it might just cause a slight delay in shutdown. So no one has ever reported it. Or they experienced the same thing as you, but couldn't be bothered.

Thanks.

[mini-jaguar]

I know it's not compatible with the FatDog64 600 series, but it loaded from the hard disk with the same menu and it worked fine.

It's probably been covered before, but why won't it boot from a USB drive?

Actually it worked fine on a 16GB stick formatted to ext2, I just can't get it to work on a 32GB stick with ext4.

Some error on my part is not out of the question though.

[smokey01]

I know it's not compatible with the FatDog64 600 series, but it loaded from the hard disk with the same menu and it worked fine.

It's probably been covered before, but why won't it boot from a USB drive?

Actually it worked fine on a 16GB stick formatted to ext2, I just can't get it to work on a 32GB stick with ext4.

Some error on my part is not out of the question though.

I think ext4 may be the culprit. Have you tried 32G with ext3?

[zeno]

I get a kernel panic when I boot from a frugal install: Unable to mount root fs on unknown-block(1,0)

menuentry "FatDog64" {
set root='(hd0,7)'
linux /vmlinuz
initrd /initrd
}

[rcrsn51]

Try:

Code: Select all

menuentry "FatDog64" {
set root='(hd0,7)'
linux /vmlinuz rootfstype=ramfs
initrd /initrd
}

[watchdog]

Many thanks rcrsn51! I was booting my fatdog64-710 from a usb-stick because I was unable to boot it by grub4dos or your grub2. Now I'm typing in fatdog64-710 after booting it by grub2 with the following menu entry in grub.cfg:

Code: Select all

menuentry "Fatdog64-710 ISO on sda1" {
 set root=(hd0,1)
 loopback loop /Fatdog64-710.iso
# linux (loop)/vmlinuz waitdev=5 savefile=direct:device:sdb1:/fd64save dofsck
 linux (loop)/vmlinuz rootfstype=ramfs waitdev=5 search=2 dofsck
 initrd (loop)/initrd
}

rootfstype=ramfs in linux line was needed. Many thanks again.

[zeno]

Thank you, it works.

Why does this puppy need that option?

[mini-jaguar]

I know it's not compatible with the FatDog64 600 series, but it loaded from the hard disk with the same menu and it worked fine.

It's probably been covered before, but why won't it boot from a USB drive?

Actually it worked fine on a 16GB stick formatted to ext2, I just can't get it to work on a 32GB stick with ext4.

Some error on my part is not out of the question though.

I think ext4 may be the culprit. Have you tried 32G with ext3?

I don't think I want to wipe the stick for that experiment, but you're probably right because it gets stuck on "loading ext2fs" or something like that. Used "showerr" and it didn't show anything else, but just got stuck there and didn't boot.

[rasul]

First thank you for the great job ... it works fine out of the box on a machine that most operating systems (puppy and else) fail in one or another way out of the box ... Thank you

Only some minor issues ... Seemingly FatDog is a bit different from the other puppies ... for example it seems not to contain the application that mount an encrypted puppy save file (extension 2fs) when double-clicking on the save file ... How can I fix it? which application should I add to fatdog? any binary already available?

Also, sorry if inconvenience but I couldn't get certain about what binaries does fatdog support? It seems to be slackware's applications but not slacko's, am I correcct? What about pet files? sfs's and deb files? Is there any easy way to use them for fatdog? please bear with me I'm totally novice here using fatdog ...

[rcrsn51]

Why does this puppy need that option?

Jamesbond will have to answer that.

[watchdog]

Only some minor issues ... Seemingly FatDog is a bit different from the other puppies ... for example it seems not to contain the application that mount an encrypted puppy save file (extension 2fs) when double-clicking on the save file ... How can I fix it? which application should I add to fatdog? any binary already available?

I can do it manually using a losetup-old from an old testing version of xenialpup64 which I attach. Delete the fake gz and move losetup-old in /sbin. Then in console:

Code: Select all

losetup -a

and watch a free loop device. Say it can be /dev/loop2. Then in console for a lightencrypted savefile (I have used in the test a lightencrypted slackosave from slacko 5.7):

Code: Select all

# losetup-old -E 1 /dev/loop2 /mnt/sda1/slacko57/slackosave_cryptx-s57-bk.2fs
Password: 
#mkdir /mnt/dir
# mount /dev/loop2 /mnt/dir
# ls /mnt/dir
bin  dev  etc  initrd  lib  lost+found  mnt  opt  root  sbin  sys  usr  var
# umount /mnt/dir
# losetup-old -d /dev/loop2

For an heavy encrypted savefile you can use in the example:

Code: Select all

losetup-old -e aes /dev/loop2 slackosave_save_crypta-s57-bk.2fs

[zeno]

Impressive control panel and out-of-the-box functionality, there are many recent packages (4.10 kernel, qt5, gtk3 and other chrome/firefox deps...).

I think that you should aim to achieve full compatibility with one big repository (debian/arch/rpm).

Another minor issue: On my netbook when I change the brightness/backlight, it saves the setting but it doesn't 'apply' it when I reboot.
A possible solution would be to append "tee /sys/class/backlight/acpi_video0/brightness <<< 0" (change 0 with the number) to the init start script or to the .bash_profile, is this problem common?

Edit: It doesn't seem to execute the command, maybe I should put it in the /root/Startup folder.

[rasul]

Only some minor issues ... Seemingly FatDog is a bit different from the other puppies ... for example it seems not to contain the application that mount an encrypted puppy save file (extension 2fs) when double-clicking on the save file ... How can I fix it? which application should I add to fatdog? any binary already available?

I can do it manually using a losetup-old from an old testing version of xenialpup64 which I attach. Delete the fake gz and move losetup-old in /sbin. Then in console:

Code: Select all

losetup -a

and watch a free loop device. Say it can be /dev/loop2. Then in console for a lightencrypted savefile (I have used in the test a lightencrypted slackosave from slacko 5.7):

Code: Select all

# losetup-old -E 1 /dev/loop2 /mnt/sda1/slacko57/slackosave_cryptx-s57-bk.2fs
Password: 
#mkdir /mnt/dir
# mount /dev/loop2 /mnt/dir
# ls /mnt/dir
bin  dev  etc  initrd  lib  lost+found  mnt  opt  root  sbin  sys  usr  var
# umount /mnt/dir
# losetup-old -d /dev/loop2

For an heavy encrypted savefile you can use in the example:

Code: Select all

losetup-old -e aes /dev/loop2 slackosave_save_crypta-s57-bk.2fs

thanks for the tip and the file, it saved me a lot of effort, wish I could write a script to automate it ...