Wireless works again, new icons, fast boot, terrible bluetooth through VLC (but who knows if an applet will "fix" this), otherwise great.
Thanks
Fatdog64-800 Alpha / Beta [20 Dec 2018] [CLOSED]
jamesbond wrote:Yes.belham2 wrote:Am I correct in assuming UML is still an option for us in 800
1. Edit /usr/bin/start-uml.sh with geany.
Replace line 137 with this one:2. Download uml kernel from http://distro.ibiblio.org/fatdog/packag ... 6_64-1.txz and install it (or use gslapt).Code: Select all
myip=$(ifconfig $HOST_ADAPTER | sed '/inet6/d; /inet/!d; /127.0.0/d; s/.*inet [^0-9]*//; s/[^0-9]*netmask.*//' | head -n 1)
3. Enjoy.
Thank you, Jamesbond!
Fantastic job by the Fatdog team. Outstanding. Thanks for all your laborious efforts/time in creating this wonder.
Only positive feedback I can offer is that under some (larger) DPI the default ambiance theme can result in the menu icons overlapping the menu text. For 23Smokey theme (as per attached) ... no such overlaps are apparent.
Seeing two menu entries for TigerVNC
Not seeing a menu entry for peasydisc
Only positive feedback I can offer is that under some (larger) DPI the default ambiance theme can result in the menu icons overlapping the menu text. For 23Smokey theme (as per attached) ... no such overlaps are apparent.
Seeing two menu entries for TigerVNC
Not seeing a menu entry for peasydisc
- Attachments
-
- 800.jpg
- (38.63 KiB) Downloaded 299 times
Last edited by rufwoof on Sat 24 Nov 2018, 14:59, edited 1 time in total.
[size=75]( ͡° ͜ʖ ͡°) :wq[/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
-
stemsee
A couple of issues.
I installed Firefox. Now it's menu entry is gone. I may be imagining things, but I think the menu has changed a few times with things appearing and disappearing as new things are installed (obviously appearing is normal!).
I tried installing Virtualbox the normal way, using the .run file and compiling it. It doesn't work as it has for me in the past, complaining that the kernel sources aren't loaded (they are)
I installed Firefox. Now it's menu entry is gone. I may be imagining things, but I think the menu has changed a few times with things appearing and disappearing as new things are installed (obviously appearing is normal!).
I tried installing Virtualbox the normal way, using the .run file and compiling it. It doesn't work as it has for me in the past, complaining that the kernel sources aren't loaded (they are)
VBox installer is no longer compatibile with FD.p310don wrote:I tried installing Virtualbox the normal way, using the .run file and compiling it. It doesn't work as it has for me in the past, complaining that the kernel sources aren't loaded (they are)
At some point (IIRC with v5.1 or v5.2) they started using a diffrently arranged PATH in their install scripts, where /bin is before /usr/bin.
The installer uses readlink's '-e' option in a few places, but /bin/readlink in FD is BusyBox's applet that doesn't support this option.
The easiest fix is to remove/rename /bin/readlink before running the installer, so /usr/bin/readlink will be used instead.
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]
[b][color=green]Omnia mea mecum porto.[/color][/b]
Why not change the link from busybox to /usr/bin/readlink as a permanent solution.SFR wrote:VBox installer is no longer compatibile with FD.p310don wrote:I tried installing Virtualbox the normal way, using the .run file and compiling it. It doesn't work as it has for me in the past, complaining that the kernel sources aren't loaded (they are)
At some point (IIRC with v5.1 or v5.2) they started using a diffrently arranged PATH in their install scripts, where /bin is before /usr/bin.
The installer uses readlink's '-e' option in a few places, but /bin/readlink in FD is BusyBox's applet that doesn't support this option.
The easiest fix is to remove/rename /bin/readlink before running the installer, so /usr/bin/readlink will be used instead.
Greetings!
Perfect solution - worked like a charmVBox installer is no longer compatibile with FD.
At some point (IIRC with v5.1 or v5.2) they started using a diffrently arranged PATH in their install scripts, where /bin is before /usr/bin.
The installer uses readlink's '-e' option in a few places, but /bin/readlink in FD is BusyBox's applet that doesn't support this option.
The easiest fix is to remove/rename /bin/readlink before running the installer, so /usr/bin/readlink will be used instead.
http ssh proxy
Out and about, and its nice to be able to use a ssh tunnel to your home based system to use that as a http proxy. When you use key based ssh access that pretty much voids any man in middle attacks in a internet cafe (unless you accept any warnings about changes of ssh keys/man in middle risk threat warnings). That way and all your html traffic routes through a secure encrypted ssh tunnel and uses your home based network to retrieve web pages rather than that traffic flowing through the internet cafe's network.
As a quick test I set up a local version
Use control panel, Manage Services so that sshd is enabled (at each reboot) and started. ... to create the private and public keys.
Add the ~/.ssh/id_rsa.pub key to the ~/.ssh/authorized_keys file (if it doesn't already exist just copy id_rsa.pub to it).
In xterm set up the proxy server(you need to leave that tunnel open i.e. just minimise the xterm window)
In another xterm window and assuming chrome has been installed ...
chrome starts up fine, and works well browsing for instance bbc.co.uk. If the above ssh -D 8080 .... xterm is exited then the browser no longer can view any web pages (as the proxy is down).
In seamonkey however (fatdogs default browser), no matter what settings I set in advanced/proxy ... it just doesn't work !!!
The above is just a local test. If (as you should) you have eztables (firewall) also set to be started (its not by default), then you need to add a ssh entry for that (/etc/eztables/eztables.cfg) so that it lets ssh through. Also to remotely ssh into your home system you need to know its external IP ... and have the home router set to port forward ssh to the fatdog PC (that must be running). For the ssh key you also need to have the laptop (remote) systems public key created and added to the home fatdog's authorized_keys list, along with using
ssh -D 8080 -p 22 root@<home_system_IP>
(substituting <home_system_IP> for whatever your home PC IP address is) instead of ssh -D 8080 -p 22 root@localhost as above. Lastly its not a good idea to have root ssh available from externally - better to use a more restricted userid (created for that purpose).
Crux of this post however ... is that for Fatdog 800 for Seamonkey, setting a proxy doesn't seem to work. I'm also seeing similar in fatdog 721 for Seamonkey (again Chrome is fine). [Suspect its may because of Seamonkey being set to run as userid spot].
As a quick test I set up a local version
Use control panel, Manage Services so that sshd is enabled (at each reboot) and started.
Code: Select all
ssh-keygenAdd the ~/.ssh/id_rsa.pub key to the ~/.ssh/authorized_keys file (if it doesn't already exist just copy id_rsa.pub to it).
In xterm set up the proxy server
Code: Select all
ssh -D 8080 -p 22 root@localhostIn another xterm window and assuming chrome has been installed ...
Code: Select all
cd /opt/google/chrome
./chrome --no-sandbox --proxy-server="socks://localhost:8080"In seamonkey however (fatdogs default browser), no matter what settings I set in advanced/proxy ... it just doesn't work !!!
The above is just a local test. If (as you should) you have eztables (firewall) also set to be started (its not by default), then you need to add a ssh entry for that (/etc/eztables/eztables.cfg) so that it lets ssh through. Also to remotely ssh into your home system you need to know its external IP ... and have the home router set to port forward ssh to the fatdog PC (that must be running). For the ssh key you also need to have the laptop (remote) systems public key created and added to the home fatdog's authorized_keys list, along with using
ssh -D 8080 -p 22 root@<home_system_IP>
(substituting <home_system_IP> for whatever your home PC IP address is) instead of ssh -D 8080 -p 22 root@localhost as above. Lastly its not a good idea to have root ssh available from externally - better to use a more restricted userid (created for that purpose).
Crux of this post however ... is that for Fatdog 800 for Seamonkey, setting a proxy doesn't seem to work. I'm also seeing similar in fatdog 721 for Seamonkey (again Chrome is fine). [Suspect its may because of Seamonkey being set to run as userid spot].
- Attachments
-
- xscreenshot-20181124T193729.jpg
- (75.78 KiB) Downloaded 687 times
[size=75]( ͡° ͜ʖ ͡°) :wq[/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
If you're a MetaARPA member of sdf ($9/quarter) https://sdf.org/?join
Then you can use sdf as your proxy, so your ISP only sees encrypted/secure ssh traffic between you and sdf. And any web site you visit will see you as being located wherever the sdf server is located, not your home IP/geolocation (??? unsure about whether setup would be as a transparent proxy or anonymous proxy)
https://sdf.org/?tutorials/SSH-SDF#socks
Then you can use sdf as your proxy, so your ISP only sees encrypted/secure ssh traffic between you and sdf. And any web site you visit will see you as being located wherever the sdf server is located, not your home IP/geolocation (??? unsure about whether setup would be as a transparent proxy or anonymous proxy)
https://sdf.org/?tutorials/SSH-SDF#socks
If anonymity isn't possible through ssh proxy then they also support X-forwarding which is more inclined to be anonymous.Alternatively, issue a command from your workstation similar to this one (MetaARPA membership required):
ssh -D 9999 -p 443 username@sverige.freeshell.org
Then, configure your browser to use the SOCKS proxy on "localhost" using port 9999
[size=75]( ͡° ͜ʖ ͡°) :wq[/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
Chrome is running as spot as well, if you used the builtin installer. Do make sure you have libicu installed as mentioned on the first post. Other than that it may be a Seamonkey bug.Crux of this post however ... is that for Fatdog 800 for Seamonkey, setting a proxy doesn't seem to work. I'm also seeing similar in fatdog 721 for Seamonkey (again Chrome is fine). [Suspect its may because of Seamonkey being set to run as userid spot].
Control Panel ... Display Properties alternative (xrandr) ... saves the changes to ~/.config/autostart/lxrandr-autostart.desktop, however that's not run i.e. if restartX
I sym linked to that from ~/Startup so that it gets run.
I sym linked to that from ~/Startup so that it gets run.
[size=75]( ͡° ͜ʖ ͡°) :wq[/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
There's also a built-in way to execute stuff from 'autostart' locations at boot, via /etc/xdg/Startup/launch-autostart script. Just enable:rufwoof wrote:Control Panel ... Display Properties alternative (xrandr) ... saves the changes to ~/.config/autostart/lxrandr-autostart.desktop, however that's not run i.e. if restartX
I sym linked to that from ~/Startup so that it gets run.
CP -> Desktop -> Manage desktop startup programs -> System startup programs -> launch-autostart
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]
[b][color=green]Omnia mea mecum porto.[/color][/b]
-
WB7ODYFred
- Posts: 169
- Joined: Sun 14 Dec 2008, 02:15
- Location: Oregon & Washington
FatDogArm
Hello All,
Wish to start working to Port / Boot FatDog64-800a to QEMU ARM Arch64
Then onto my NanoPi2 Hardware with Quad core ARM s5p4418 processor and 1 Gigabyte DRAM memory, and HDMI output.
I am expressing my interest in running Fatdog64 800a on real quad core ARM hardware to see how it compares with x86 hardware.
Looking for other interested individuals, Who also Have interest in porting to real ARM 64bit hardware, like chinese set top boxes or the ASUS Tinkerboard. $64 at Frys electronics store. Google for other sources like https://newegg.com
https://www.asus.com/us/Single-Board-Co ... ker-Board/
I have been reading and studying the valuable information JameBond has posted on his http://LightofDawn.org web site about porting FatDog64 to FatDogARM.
Running QEMU ARM on x86 hardware
http://lightofdawn.org/wiki/wiki.cgi/-w ... ArmForQemu
FatdogArm Wiki Index page
http://lightofdawn.org/wiki/wiki.cgi/-w ... -WikiIndex
Building Applications page
http://lightofdawn.org/wiki/wiki.cgi/-w ... plications
I enjoyed the installed debian linux on the NanoPi2 with wifi. Was able to play 720P youtube videos on the television monitor with the HDMI output. Now interested in porting a real puppylinux to ARM 64bit hardware
I have got the U-Boot sources for NanoPi2 compiling and outputing a boot image.
NanoPi2 development tools for U-Boot and the debian O/S
https://github.com/friendlyarm/uboot_nanopi2
http://www.nanopi.org/nanopi-2_development.html
http://wiki.friendlyarm.com/wiki/index.php/NanoPi_2
http://wiki.friendlyarm.com/wiki/index. ... load_Links
https://drive.google.com/drive/folders/ ... sDskO94d9Z NanoPi2 Sources for Android and Linux
The NanoPi2 has been discontinued but there are other models available like the NanoPi K2 that could be a FatdogArm Linux desktop to connect with your HDMI television / monitor Display.
North American distributor
https://andahammer.com/
Model NanoPi K2 with 2Gigabytes DRAM and 4 USB ports
https://andahammer.com/index.php?route= ... uct_id=196
Looking to long term port FatDog64 800 to run on 64 bit Arm Hardware. First testing out on the QEMU running ARM 64 bit on the FatDog64 x86 software.
Anybody else interested? Your comments? Welcome to open a new topic specifically for this porting exercise.
Cheers to the FatDog64 team,
Fred Finster
Wish to start working to Port / Boot FatDog64-800a to QEMU ARM Arch64
Then onto my NanoPi2 Hardware with Quad core ARM s5p4418 processor and 1 Gigabyte DRAM memory, and HDMI output.
I am expressing my interest in running Fatdog64 800a on real quad core ARM hardware to see how it compares with x86 hardware.
Looking for other interested individuals, Who also Have interest in porting to real ARM 64bit hardware, like chinese set top boxes or the ASUS Tinkerboard. $64 at Frys electronics store. Google for other sources like https://newegg.com
https://www.asus.com/us/Single-Board-Co ... ker-Board/
I have been reading and studying the valuable information JameBond has posted on his http://LightofDawn.org web site about porting FatDog64 to FatDogARM.
Running QEMU ARM on x86 hardware
http://lightofdawn.org/wiki/wiki.cgi/-w ... ArmForQemu
FatdogArm Wiki Index page
http://lightofdawn.org/wiki/wiki.cgi/-w ... -WikiIndex
Building Applications page
http://lightofdawn.org/wiki/wiki.cgi/-w ... plications
I enjoyed the installed debian linux on the NanoPi2 with wifi. Was able to play 720P youtube videos on the television monitor with the HDMI output. Now interested in porting a real puppylinux to ARM 64bit hardware
I have got the U-Boot sources for NanoPi2 compiling and outputing a boot image.
NanoPi2 development tools for U-Boot and the debian O/S
https://github.com/friendlyarm/uboot_nanopi2
http://www.nanopi.org/nanopi-2_development.html
http://wiki.friendlyarm.com/wiki/index.php/NanoPi_2
http://wiki.friendlyarm.com/wiki/index. ... load_Links
https://drive.google.com/drive/folders/ ... sDskO94d9Z NanoPi2 Sources for Android and Linux
The NanoPi2 has been discontinued but there are other models available like the NanoPi K2 that could be a FatdogArm Linux desktop to connect with your HDMI television / monitor Display.
North American distributor
https://andahammer.com/
Model NanoPi K2 with 2Gigabytes DRAM and 4 USB ports
https://andahammer.com/index.php?route= ... uct_id=196
Looking to long term port FatDog64 800 to run on 64 bit Arm Hardware. First testing out on the QEMU running ARM 64 bit on the FatDog64 x86 software.
Anybody else interested? Your comments? Welcome to open a new topic specifically for this porting exercise.
Cheers to the FatDog64 team,
Fred Finster
-
WB7ODYFred
- Posts: 169
- Joined: Sun 14 Dec 2008, 02:15
- Location: Oregon & Washington
Errors found when using SFS files, tools to compile DTC
Missing symbolic link from libmpfr.so.4
/gcc/armv7l-fatdog-linux-gnueabihf/4.8.1/cc1 was missing a file. so I created a symbolic link to enable cc1 operation.
Well, downloaded Device Tree Compiler from dgibson site using Git
You can download a gzip version here from kernel.org sources
https://git.kernel.org/pub/scm/utils/dtc/dtc.git
/gcc/armv7l-fatdog-linux-gnueabihf/4.8.1/cc1 was missing a file. so I created a symbolic link to enable cc1 operation.
Compiling U-Boot software for NanoPi2# cd /usr/lib64/
# ls -la libmpfr*
-rw-r--r-- 1 root root 954050 May 26 2018 libmpfr.a
lrwxrwxrwx 1 root root 16 May 26 2018 libmpfr.so -> libmpfr.so.6.0.1
lrwxrwxrwx 1 root root 16 May 26 2018 libmpfr.so.6 -> libmpfr.so.6.0.1
-rwxr-xr-x 1 root root 430528 May 26 2018 libmpfr.so.6.0.1
## make the symbolic link here to current version of libmpfr.so shared object file
# ln -s libmpfr.so.6.0.1 libmpfr.so.4
# pwd
/usr/lib64
Loading SFS files for use in Cross Compiling# PATH=$PATH\:/aufs/pup_ro11/opt/arm-cross/usr/bin
# export PATH
# pwd
/opt/friendlyarm/u-boot
# echo $PATH
/usr/local/bin:/usr/bin:/usr/sbin:/bin:/sbin:/opt/qt5/bin:/aufs/pup_ro11/opt/arm-cross/usr/bin
# make CROSS_COMPILE=armv7l-fatdog-linux-gnueabihf-
scripts/kconfig/conf --silentoldconfig Kconfig
CHK include/config.h
GEN include/autoconf.mk
/aufs/pup_ro11/opt/arm-cross/usr/bin/../libexec/gcc/armv7l-fatdog-linux-gnueabihf/4.8.1/cc1: error while loading shared libraries: libmpfr.so.4: cannot open shared object file: No such file or directory
make[1]: *** [scripts/Makefile.autoconf:72: include/autoconf.mk] Error 1
make: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/uboot.release'. Stop.
## FIX missing libmpfr.so.4 by making a symbolic link in FATDOG64 /usr/lib64
Code: Select all
Load SFS files to obtain use of development tools git and gcc
Download and save files to /mnt/home/SFS_Files directory
# mkdir /mnt/home/sfs_files
# cd /mnt/home/sfs_files
Download the 3 .SFS files to SFS_files directory
# ls -lah *.sfs
-rwxr-xr-x 1 root users 87M Apr 6 2015 arm-cross-gcc-4.8.1.sfs
-rwxr-xr-x 1 root users 552M Nov 12 15:42 fd64-devx_800a.sfs
-rwxr-xr-x 1 root users 137M Nov 8 13:56 kernel-source-4.19.1.sfs
#
# cd /mnt/home
create this shell file mk_sfs_sym_link.sh Copy the next 4 lines into file mk_sfs_syn_link.sh
#!/bin/sh
# Quick Symbolic Link creator for my use
echo Zero token: $0 first Token: $1 name of .SFS file to link without .SFS extension in the /mnt/home directory. This is done so .SFS squash files will be loaded in the aufs as a read only file when booting up.
ln -s ./sfs_files/$1.sfs ./$1.sfs
#chmod +x ./mk_sfs_sym_link.sh
## Create Symbolic Links for the following 3 files from /mnt/home directory to their location in a sub directory.
#./mk_sfs_sym_link.sh fd64-devx_800a.sfs
#./mk_sfs_sym_link.sh arm-cross-gcc-4.8.1.sfs
#./mk_sfs_sym_link.sh kernel-source-4.19.1.sfs
To start System SFS Loader use this sequence below:
Menu --> Setup --> Fatdog64 Control --> System --> System SFS Loader
## check version of tools being used.
# git --version
git version 2.17.1
# gcc --version
gcc (GCC) 7.3.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
You can download a gzip version here from kernel.org sources
https://git.kernel.org/pub/scm/utils/dtc/dtc.git
GIT U-BOOT for NanoPi2 code and ARM cross compile# cd /usr/src/linux-4.19.1/scripts
# pwd
# git clone https://github.com/dgibson/dtc.git
# cd dtc
# make
or edit the Makefile line x35 and change $(HOME) to /usr before executing "make install"
#PREFIX = $(HOME)
PREFIX = /usr
# make install
Code: Select all
# echo $PATH
/usr/local/bin:/usr/bin:/usr/sbin:/bin:/sbin:/opt/qt5/bin
example: PATH=$PATH\:/dir/path ; export PATH for bash shell
PATH=$PATH\:/aufs/pup_ro11/opt/arm-cross/usr/bin ; export PATH
mkdir /opt/friendlyarm
cd /opt/friendlyarm
git clone https://github.com/friendlyarm/u-boot.git
cd u-boot
git checkout nanopi2-v2016.01
make s5p4418_nanopi2_defconfig
make CROSS_COMPILE=armv7l-fatdog-linux-gnueabihf-
I see that the default /dev/fb0 permissions have been changed for the better. Nice!
Adding a password when creating a ssh key makes it more difficult if your laptop is stolen.
Adding both key and password authentication when accessing a server helps if either the key or the password is eavesdropped, and pretty much mitigates man-in-middle attacks (excepting if you accept and continue despite the system throwing out a message to the effect that a man-in-middle attack could be in place).
Not ssh'ing from X, instead using console (ctrl-alt-F2 for instance) helps avoid passwords being eavesdropped through X, and when the console (framebuffer) permissions are correctly set (as they are now in Fatdog), then less likely that the console based password entry is being eavesdropped.
Adding a password when creating a ssh key makes it more difficult if your laptop is stolen.
Adding both key and password authentication when accessing a server helps if either the key or the password is eavesdropped, and pretty much mitigates man-in-middle attacks (excepting if you accept and continue despite the system throwing out a message to the effect that a man-in-middle attack could be in place).
Not ssh'ing from X, instead using console (ctrl-alt-F2 for instance) helps avoid passwords being eavesdropped through X, and when the console (framebuffer) permissions are correctly set (as they are now in Fatdog), then less likely that the console based password entry is being eavesdropped.
[size=75]( ͡° ͜ʖ ͡°) :wq[/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
Thank you. TigetVNC icon should already be fixed for the next dev build.rufwoof wrote:Seeing two menu entries for TigerVNC
Not seeing a menu entry for peasydisc
Missing peasydisc icon - I can't reproduce this. I installed peasydisc with gslapt. The icon is added and visible at the bottom of the Multimedia menu.
Doh! My mistake. I thought peasydisc was one of the default programs (already installed in base FatDog).step wrote:Missing peasydisc icon - I can't reproduce this. I installed peasydisc with gslapt. The icon is added and visible at the bottom of the Multimedia menu.
[size=75]( ͡° ͜ʖ ͡°) :wq[/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
[url=http://murga-linux.com/puppy/viewtopic.php?p=1028256#1028256][size=75]Fatdog multi-session usb[/url][/size]
[size=75][url=https://hashbang.sh]echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh[/url][/size]
Waiting for beta stage
For now I will Zucker-out of any alpha testing but might give it a go once a beta version becomes available.
Key issues for me:
1 - being able to run X as a non-root user (which worked well in FD64 7.2.1)
2 - being able to modify the main sfs file
3 - maintaining the system free of critical security issues
4 - having as many of the specte/meltdown bugs fixed as is possible.
I noticed some microcode from 20180915. Will that make it into the next release?
Of all the distributions I have looked at this year the best that the meltdown checker script file could pass was 6 out of 8 flaws.
Chipzilla might say 6 out of 8 is not bad but I say 6 out of 8 is not great.
I did not use FD64 7.2.1 because I thought the toolset (mainly gcc) was a bit too old.
I suppose it is too late to change to gcc 8 series?
Modifying the main sfs file in FD 7.2.1 was a bit of a pain but I got used to it.
It would be helpful if the mksquashfs and cpio paramters used to create the files could be posted somewhere inside the iso file.
It would be nice to see abiword and gnumeric in the beta test iso or at least provided as a sfs file.
These two apps are not very big but they use much less memory than LibreOffice.
Having LibreOffice in the iso file is very useful. I can always strip it out and make a sfs file in case I want to use it.
I can understand using one of the latest kernels but I would have thought using one of the LTS kernels (like 4.14.x) would have made maintenance easier similar to what Slackware does.
A few weeks ago I read somewhere that 4.19.x was supposed to be the next LTS but I am not sure if the kernel people will ever release any more LTS versions.
What happens 6 months from now if 4.19.x is no longer supported?
I have yet to see any aufs-Linux system that handled maintenance issues well.
Most of these systems have been "issue once and wait until the next release" to fix any problems (which can take a year sometimes).
Any ideas on how to improve system security patches for users in the future?
I am sure that you do not have the time to deliver a new release every month nor would I request such a schedule.
Thanks
Key issues for me:
1 - being able to run X as a non-root user (which worked well in FD64 7.2.1)
2 - being able to modify the main sfs file
3 - maintaining the system free of critical security issues
4 - having as many of the specte/meltdown bugs fixed as is possible.
I noticed some microcode from 20180915. Will that make it into the next release?
Of all the distributions I have looked at this year the best that the meltdown checker script file could pass was 6 out of 8 flaws.
Chipzilla might say 6 out of 8 is not bad but I say 6 out of 8 is not great.
I did not use FD64 7.2.1 because I thought the toolset (mainly gcc) was a bit too old.
I suppose it is too late to change to gcc 8 series?
Modifying the main sfs file in FD 7.2.1 was a bit of a pain but I got used to it.
It would be helpful if the mksquashfs and cpio paramters used to create the files could be posted somewhere inside the iso file.
It would be nice to see abiword and gnumeric in the beta test iso or at least provided as a sfs file.
These two apps are not very big but they use much less memory than LibreOffice.
Having LibreOffice in the iso file is very useful. I can always strip it out and make a sfs file in case I want to use it.
I can understand using one of the latest kernels but I would have thought using one of the LTS kernels (like 4.14.x) would have made maintenance easier similar to what Slackware does.
A few weeks ago I read somewhere that 4.19.x was supposed to be the next LTS but I am not sure if the kernel people will ever release any more LTS versions.
What happens 6 months from now if 4.19.x is no longer supported?
I have yet to see any aufs-Linux system that handled maintenance issues well.
Most of these systems have been "issue once and wait until the next release" to fix any problems (which can take a year sometimes).
Any ideas on how to improve system security patches for users in the future?
I am sure that you do not have the time to deliver a new release every month nor would I request such a schedule.
Thanks