Fatdog64-710 Final [4 Dec 2016]

A home for all kinds of Puppy related projects
Message
Author
bpuppy2

#401 Post by bpuppy2 »

Greetings,

Timestamping of the system messages is showing my desktop clock time fine now. It makes it more realistic. Thanks.

I am posting the output here:

bpuppy2
Attachments
Shot-1025.png
(58.72 KiB) Downloaded 110 times

User avatar
SFR
Posts: 1800
Joined: Wed 26 Oct 2011, 21:52

#402 Post by SFR »

Alright, thanks for confirmation!

Anyway, the output of ls -v /sys/fs/aufs/*/br[0-9]* turned out to be not enough. Can you post the output of:

Code: Select all

ls -v /sys/fs/aufs/*/br[0-9]* | xargs sed 's/=.*//'
Oh, and this time as a text, not a screenshot, if you could.

Thanks &
Greetings!
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]

User avatar
rufwoof
Posts: 3690
Joined: Mon 24 Feb 2014, 17:47

#403 Post by rufwoof »

sda1 ext3 partition cleared except for menu.lst and grldr (grub4dos) bootloaders.

Installed FD by extracting the main sfs from initrd and extracting the main sfs to a savefolder (/fd64save). Dropped initrd (that excludes the main sfs) and vmlinuz into /boot

... booted, installed all outstanding updates and configured to UK locale/keyboard/timezone.

Changing the resolution had my monitor (I use a TV as a monitor) having to be readjusted each time (using the TV remote to Adjust Position). At FD startup it would frame/jig around ... and then just click to a incorrect position.

Running cvt and dropping the modeline into xorg.conf didn't help. Adding another xrandr command into Startup folder however did. It starts up off centre and then when that Startup file runs it correctly repositions the screen nicely.

Tried out skype sfs (figured out you also have to install the 32 bit sfs) and that's working well.

Using a grub4dos menu.lst of

title FatDog
find --set-root /menu.lst
kernel /boot/vmlinuz basesfs=none savefile=ram:device:sda1:/fd64save
initrd /boot/initrd

it boots nice and quickly.

bpuppy2

#404 Post by bpuppy2 »

[quote="SFR"]
Anyway, the output of ls -v /sys/fs/aufs/*/br[0-9]* turned out to be not enough. Can you post the output of:

Code: Select all

ls -v /sys/fs/aufs/*/br[0-9]* | xargs sed 's/=.*//'
I get this, this time:

sed: can't read /sys/fs/aufs/si_ef4eb0245344c929/br0: No such file or directory
sed: can't read /sys/fs/aufs/si_ef4eb0245344c929/br1: No such file or directory
sed: can't read /sys/fs/aufs/si_ef4eb0245344c929/br2: No such file or directory
sed: can't read /sys/fs/aufs/si_ef4eb0245344c929/br3: No such file or directory
sed: can't read /sys/fs/aufs/si_ef4eb0245344c929/br4: No such file or directory
sed: can't read /sys/fs/aufs/si_ef4eb0245344c929/br5: No such file or directory

bpuppy2

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#405 Post by step »

@rufwoof, an unpacked basesfs as the saveforlder... it's a neat idea. Did you have a specific application in mind for this setup, or is it just for experimenting?
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#406 Post by step »

@bpuppy2, those sed errors are rather strange, they shouldn't happen. Did you run the command from inside sandbox.sh? If so, run it again outside sandbox.sh.
@SFR, line 104 should be: else if (mode == 4), though it doesn't matter, by chance.
Last edited by step on Fri 28 Apr 2017, 21:48, edited 1 time in total.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

bpuppy2

#407 Post by bpuppy2 »

@step

The output comes from outside sandbox.sh already.

User avatar
rufwoof
Posts: 3690
Joined: Mon 24 Feb 2014, 17:47

#408 Post by rufwoof »

step wrote:@rufwoof, an unpacked basesfs as the savefolder... it's a neat idea. Did you have a specific application in mind for this setup, or is it just for experimenting?
Its the way I usually prefer to run frugals Step. HDD space nowadays is extremely inexpensive. In the Debian based system I boot as a everyday the save partition is / and again the main sfs is empty ... which means it can also be booted as though a full install; Or be booted frugally without saving (useful for testing things out, or to be using a layered system so that sfs's can also be loaded).

Conceptually for FD if everything is in the save folder and fd64.sfs is empty/non existent as I currently have it setup, then I can make a sfs of that savefolder and reboot using that sfs ... without a 'savefile' as a no changes saved type session for testing things out (just shutdown and not save at the end of the session).

In Debian I run mostly as a restricted user session, so if a hacker breaks out of the browser they drop into a very limited user account (I went around and chmod most folders so that that userid can't get to see other folders/files such as personal documents). For documentation I just ctrl-alt-Fn and login as a normal user ... but don't use that account for any web stuff (kodi, skype, firefox ...etc). Most pup's are single user, FD is multi-user (can also ctrl-alt-F1 for instance and log in). However there's less need for that as FD isolates web programs anyway (run as spot). Another benefit of FD is that its like most other pup's ... already setup and ready to go. Debian is a headache to setup (and the group are nowhere near as friendly either, rather the complete opposite).

One of the best pup's around is FD. The main negative as I see it is not being a rolling release and having to re-setup all over again at each new release.

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#409 Post by step »

@bpuppy2, try this on a command line

Code: Select all

( . $BOOTSTATE_PATH ; ls -v /sys/fs/aufs/$AUFS_ROOT_ID/br[0-9]* | xargs sed 's/=.*//' )
And if you still get the sed error, that's the reason why dialog fails short of arguments. I'm writing this comment for SFR, when he will be able to take a look again.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#410 Post by step »

@rufwoof, which pups are rolling, do you know? I don't.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

bpuppy2

#411 Post by bpuppy2 »

@step: i get same output as previously except the si_# has changed.

bpuppy2

User avatar
SFR
Posts: 1800
Joined: Wed 26 Oct 2011, 21:52

#412 Post by SFR »

step wrote:And if you still get the sed error, that's the reason why dialog fails short of arguments. I'm writing this comment for SFR, when he will be able to take a look again.
bpuppy2 wrote:@step: i get same output as previously except the si_# has changed.
Yep, this is most likely the reason why dialog fails.
But why the br* files are inaccessible is another question; maybe it's still the aftermath of updating util-linux..?
The best I can suggest at the moment is to try the sandbox with a clean savefile/folder (having the same set of SFSes loaded) and if it works, just switch to that savefile for good.

Greetings!
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]

stemsee

#413 Post by stemsee »

Has anyone else had issues after upgrading to fd 4.10.8 kernel?

User avatar
SFR
Posts: 1800
Joined: Wed 26 Oct 2011, 21:52

#414 Post by SFR »

stemsee wrote:Has anyone else had issues after upgrading to fd 4.10.8 kernel?
I was running it for a short while - got problems with sustaining a stable connection to a wireless AP I've set on my laptop (RTL8191SEvB WLAN Controller).
Other than that, seems ok.

Greetings!
[color=red][size=75][O]bdurate [R]ules [D]estroy [E]nthusiastic [R]ebels => [C]reative [H]umans [A]lways [O]pen [S]ource[/size][/color]
[b][color=green]Omnia mea mecum porto.[/color][/b]

bpuppy2

#415 Post by bpuppy2 »

Yesterday, i booted into Fatdog64 with the savefile loaded and sandbox.sh worked just fine.

I have no idea what or why i had trouble with it before, but now it's ok, so like the old saying, i won't fix it if it ain't broke!

thanks,
bpuppy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Isaac Asimov's AI laws have been violated by 'killer drones'.

bpuppy2

Seamonkey mail

#416 Post by bpuppy2 »

Hello again,

I am using Seamonkey mailer but can't have it contact my ISP without stopping the firewall. How should i deal with this?

watchdog
Posts: 2021
Joined: Fri 28 Sep 2012, 18:04
Location: Italy

Re: Seamonkey mail

#417 Post by watchdog »

bpuppy2 wrote:Hello again,

I am using Seamonkey mailer but can't have it contact my ISP without stopping the firewall. How should i deal with this?
Read:

http://www.murga-linux.com/puppy/viewto ... 635#936635

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

Re: Seamonkey mail

#418 Post by step »

bpuppy2 wrote:Hello again,

I am using Seamonkey mailer but can't have it contact my ISP without stopping the firewall. How should i deal with this?
Try this (untested):

Edit /etc/eztables/eztables.cfg.

Look for the line that starts with BASIC_SERVICES="
Add $MAIL to the list. On my PC the result looks like this

Code: Select all

BASIC_SERVICES="

    $WEB
    $DNS
    $NTP
    $SSH
    $MAIL
"
Insert before BASIC_SERVICES=" this block of lines:

Code: Select all

MAIL="
    25/tcp
    2525/tcp
    110/tcp
    995/tcp
    143/tcp
    993/tcp
    587/tcp
    465/tcp
"
Restart the firewall.
More examples like this >

edit: watchdog beat me to the finish line by a hair! The information we gave is the same. However, be careful cutting and pasting from the link referenced in watchdog's message, because the syntax is wrong. Also, if you need to copy code blocks from a post, click the reply with quote button and copy from the block from the edit box. This way you'll avoid the invisible spaces that this forum software appends to each copied line.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

eowens2
Posts: 177
Joined: Wed 27 Aug 2008, 17:57

Thunderbird

#419 Post by eowens2 »

Is anyone using Thunderbird version 52.1.0 with Fatdog64_710-Final?

I have been using Thunderbird Version 45.8.0 with Fatdog for the last 6 months, booting it in the manner described by Smokey01 (http://www.murga-linux.com/puppy/viewto ... &start=58)). But this version of T-bird is now superseded.

However, using the same technique described above to boot T-bird Version 52.1.0 does not work (I cannot find any error log that seems to have any useful information).

Any help getting the new T-bird version to boot would be appreciated.

eowens2
Posts: 177
Joined: Wed 27 Aug 2008, 17:57

#420 Post by eowens2 »

Is anyone using Thunderbird Version 52.1.0 with Fatdog64_710-Final?

I have been using Thunderbird Version 45.8.0 for the last 6 months, booting it in the manner described by Smokey01 (http://www.murga-linux.com/puppy/viewto ... 7&start=58). But this version of T-bird is now superseded.

However, using the same technique described above to boot T-bird Version 52.1.0 does not work (I cannot find any error log that contains any relevant information).

Any help getting the new T-bird version to boot would be appreciated.

Post Reply