Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 19 Jul 2019, 21:46
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Derivatives
EasyOS 1.0.29 (1.1RC) July 19, 2019
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 102 of 106 [1581 Posts]   Goto page: Previous 1, 2, 3, ..., 100, 101, 102, 103, 104, 105, 106 Next
Author Message
rufwoof


Joined: 24 Feb 2014
Posts: 3252

PostPosted: Thu 21 Mar 2019, 09:08    Post subject:  

Finding that running large LibreOffice spreadsheet or word documents across Xephyr is very laggy. i.e. DISPLAY=:1 swriter from the main session, so I can cut/paste from firefox running inside the (:1) container, has swriter as good as useless (very slow to scroll etc.).

Seems to be Xephyr alone causing that lag.

In view of that, had the idea to drop containers and just use the main session, but where the main session has cap_sys_chroot capability dropped. I renamed /root/.xinitrc to .xinitrc-capd and created a .xinitrc that calls .xinitrc-capd with the chroot capabilities dropped i.e. .xinitrc contains ...

#!/bin/sh
capsh --drop=cap_sys_chroot -- /root/.xinitrc-capd

Also inside initrd I modified init to chroot into the main session rather than switch-root. I also mount my sda3 (data partition) inside init so that partition is inaccessible within X. So the tail end of init inside initrd now looks like
Code:
mount -t devtmpfs devtmpfs /easy_new/dev #need to do this before switch_root.
sync
#umount /sys
#umount /proc
#exec switch_root /easy_new /sbin/init

# mount our data partition outside of the main system, so inaccessible to X
# i.e. console login and exit-chroot to access data (mc)
mkdir /mnt/sda3
mount /dev/sda3 /mnt/sda3
exec chroot /easy_new /sbin/init

To access data I ctrl-alt-F3 and login and root, escape the chroot (I have posted exit-chroot.c code for that in previous posts) and I've also installed mc inside initrd so I can use that to move files in/out of my data partition as desired (to make data files/folders visible (or not) to X).

Rebooting to 'clean' each/every time (no saves) and that's moderately secure. Data is isolated, a cracked firefox (root cli) cannot chroot into initrd; Could see other X windows and/or keystrokes, but no different to how it might also see other windows inside a container.

_________________
( ͡° ͜ʖ ͡°) :wq
Fatdog multi-session usb

echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3252

PostPosted: Thu 21 Mar 2019, 16:18    Post subject:  

Dropping capabilities in /root/.xinitrc is weak, easily uncoded by a cracker and X restarted.

So ...

Compiled exit-chroot.c of
Code:
#include <sys/stat.h>
#include <unistd.h>
#include <fcntl.h>

int main(int argc, char** argv) {
    int dir_fd, x;
    setuid(0);
    mkdir(".42", 0755);
    dir_fd = open(".", O_RDONLY);
    chroot(".42");
    fchdir(dir_fd);
    close(dir_fd);
    for(x = 0; x < 1000; x++) chdir("..");
    chroot(".");
    return execl("/bin/busybox", "sh",argv[1], NULL);
}


and adding
Code:
exit-chroot /tmp/CHR
to the end of /etc/profile, along with modified the end of init (inside initrd) code to look like

Code:
mount -t devtmpfs devtmpfs /easy_new/dev #need to do this before switch_root.
sync
#umount /sys
#umount /proc
#exec switch_root /easy_new /sbin/init

echo "#!/bin/sh" >/tmp/CHR
echo "capsh --drop=cap_sys_admin,cap_sys_chroot --chroot=/easy_new --keep=1 -- /usr/bin/xwin" >>/tmp/CHR
chmod +x /tmp/CHR

# mount our data partition outside of the main system, so inaccessible to X
# i.e. console login and exit-chroot to access data partition (sda3)
mkdir /mnt/sda3
mount /dev/sda3 /mnt/sda3
exec chroot /easy_new /sbin/init

... has the system boot as normal, but chroot the main session instead of switch-root, and the end sof /etc/profile results in a exit-chroot action (as the first time through chroot capabilities are enabled), and that exit-chroot results in /tmp/CHR being run in the initrd space, which restarts the main session, but with cap_sys_admin and cap_sys_chroot capabilities dropped. So that next time around the exit-chroot at the end of /etc/profile simply fails, as chroot capabilities are no longer enabled.

That also mounts sda3 (my data partition) from within initrd, i.e. outside of the main systems space, so inaccessible. To get to data (sda3) ctrl-alt-F3 and login as root and run exit-chroot to gain access to the initrd space ... and hence sda3 (data). I've installed mc inside of the initrd to make moving files around easier.

In effect the real root main X desktop is restricted. It can't mount sda3 as its already mounted outside of X space, can't change it with gparted ...etc. And X can't exit-chroot as chroot capabilities are dropped.

_________________
( ͡° ͜ʖ ͡°) :wq
Fatdog multi-session usb

echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3252

PostPosted: Fri 22 Mar 2019, 16:57    Post subject:  

Plenty of links/files for Puppy in Gopherspace, but nowt for EasyOS Sad
gopher-EasyOS.png
 Description   
 Filesize   83.82 KB
 Viewed   1638 Time(s)

gopher-EasyOS.png


_________________
( ͡° ͜ʖ ͡°) :wq
Fatdog multi-session usb

echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3252

PostPosted: Sat 23 Mar 2019, 06:42    Post subject:  

I do like the EasyOS 1.0 (more extensive) busybox. My 'mini' boot of just the vmlinuz and initrd - with additionals, works very well. Basically I just installed the sky2 ethernet (for my hardware) module into that and have it so it boots to net connected (using static IP) and it loads/starts with tmux loaded and tmux windows of calcurse (diary), weather (via wttr.in), mc (file manager/text editor), lynx (browser), sc-im (spreadsheet), top and ssh (dropbear) auto connected to sdf.org (from where I can browse the web/gopher/message boards etc. through that ssh link).

Runs totally in ram, all changes lost, but I've included capabilities support (along with framebuffer pdf viewing etc.), so being frugally booted I can mount sda1 and open up initrd/record changes/close initrd ... so that changes persist, whilst being able to drop the capabilities of the ssh/lynx processes.

I had previously attempted to xz extreme compress that initrd, but it wouldn't boot. Then I remembered you have to include the --check=crc32 xz compression parameter when forming a initrd.xz with extreme compression and that boots fine. 12MB xz compressed initrd.xz filesize (alongside a 5MB vmlinuz).
c.png
 Description   
 Filesize   9.55 KB
 Viewed   1578 Time(s)

c.png


_________________
( ͡° ͜ʖ ͡°) :wq
Fatdog multi-session usb

echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3252

PostPosted: Sun 24 Mar 2019, 18:28    Post subject:  

I've set my (1.0) main desktop so that both seamonkey and firefox portable are available running under spot. Where spot's default shell is set in /etc/passwd to be /bin/limited-shell ... which is a simple script that just permits very few commands/programs to be run. I also added that /bin/limited-shell to the /etc/shells list. Similar code as per http://murga-linux.com/puppy/viewtopic.php?p=1023044#1023044

Found that doing real work inside the container with largish docs/spreadsheets (libreoffice) wasn't really workable for me. Having a main desktop spot browser and using the main sessions LibreOffice works better, at least for me. Not that the container is redundant, as for other activities it shines.

I'm sticking with having the main desktop tray as most of the width, but with a smaller area left free for the container's tray when that is activated. I personally find that works better for me than the alt-F6 type switching.


(clickable thumbnail animated gif)

Desktop 1 for browser and general work; Desktop 2 for music (typically for me its headphones on as soon as I sit down at the PC); Desktop 3 for cli (tmux, mc, calcurse, ssh ...etc.).

_________________
( ͡° ͜ʖ ͡°) :wq
Fatdog multi-session usb

echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3252

PostPosted: Mon 25 Mar 2019, 19:50    Post subject:  

Can't get this http://murga-linux.com/puppy/viewtopic.php?p=1006716#1006716 to compile under EasyOS. Any suggestions (or alternatives for dynamic dns updating under EasyOS?).
_________________
( ͡° ͜ʖ ͡°) :wq
Fatdog multi-session usb

echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3252

PostPosted: Tue 26 Mar 2019, 07:21    Post subject:  

As a alternative I did try ddnsclient https://github.com/ddclient/ddclient, but that's perl and in EasyOS some of the required modules for that to run are apparently missing.

EDIT: With much compilation hand-holding by OscarTalks (thanks Oscar) managed to create a easyPak (sfs) for inadyn ... http://murga-linux.com/puppy/viewtopic.php?p=1023355#1023355

_________________
( ͡° ͜ʖ ͡°) :wq
Fatdog multi-session usb

echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh
Back to top
View user's profile Send private message 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8922
Location: Perth, Western Australia

PostPosted: Wed 27 Mar 2019, 21:31    Post subject:  

rufwoof wrote:
Finding that running large LibreOffice spreadsheet or word documents across Xephyr is very laggy. i.e. DISPLAY=:1 swriter from the main session, so I can cut/paste from firefox running inside the (:1) container, has swriter as good as useless (very slow to scroll etc.).

Seems to be Xephyr alone causing that lag.

In view of that, had the idea to drop containers and just use the main session, but where the main session has cap_sys_chroot capability dropped. I renamed /root/.xinitrc to .xinitrc-capd and created a .xinitrc that calls .xinitrc-capd with the chroot capabilities dropped i.e. .xinitrc contains ...

#!/bin/sh
capsh --drop=cap_sys_chroot -- /root/.xinitrc-capd

Also inside initrd I modified init to chroot into the main session rather than switch-root. I also mount my sda3 (data partition) inside init so that partition is inaccessible within X. So the tail end of init inside initrd now looks like
Code:
mount -t devtmpfs devtmpfs /easy_new/dev #need to do this before switch_root.
sync
#umount /sys
#umount /proc
#exec switch_root /easy_new /sbin/init

# mount our data partition outside of the main system, so inaccessible to X
# i.e. console login and exit-chroot to access data (mc)
mkdir /mnt/sda3
mount /dev/sda3 /mnt/sda3
exec chroot /easy_new /sbin/init

To access data I ctrl-alt-F3 and login and root, escape the chroot (I have posted exit-chroot.c code for that in previous posts) and I've also installed mc inside initrd so I can use that to move files in/out of my data partition as desired (to make data files/folders visible (or not) to X).

Rebooting to 'clean' each/every time (no saves) and that's moderately secure. Data is isolated, a cracked firefox (root cli) cannot chroot into initrd; Could see other X windows and/or keystrokes, but no different to how it might also see other windows inside a container.


Yes, I wondered about offering something like that at bootup. That alternative busybox utility to switch_root that I mentioned awhile back, that can drop capabilities. Offer at the first bootup menu, to run "more secure", and drop one or more of the capabilites.

_________________
http://bkhome.org/news/
Back to top
View user's profile Send private message Visit poster's website 
BarryK
Puppy Master


Joined: 09 May 2005
Posts: 8922
Location: Perth, Western Australia

PostPosted: Wed 27 Mar 2019, 21:47    Post subject:  

Doing a complete recompile of all packages, based on latest OpenEmbedded release codenamed "Thud".

My port of OE has about 150 extra packages that I had imported and developed compile recipes for.

Recompiling everything, much is broken, had to do many fixes. Still on-going.

The original intention was that when I rebased EasyOS on a new release of OE, I would bump the major version number of Easy. So 1.x will become 2.x, so the first release of Easy based on "Thud" will be 2.0.

Have to make this major version bump, as many of the previous packages will be broken. For example, now using openssl 1.1.x, before it was 1.0.x. However, I do plan to include the 1.0.x library in the Easy build.

If I do include some older libs in the build, then perhaps pre-installed older binary packages won't get broken when do an update. That's what I have to think very carefully about, people who have installed Easy 1.0.x to hd and want to do the simple method of upgrading. I am also in that situation, so will test the upgrading carefully.

_________________
http://bkhome.org/news/
Back to top
View user's profile Send private message Visit poster's website 
rufwoof


Joined: 24 Feb 2014
Posts: 3252

PostPosted: Thu 28 Mar 2019, 05:11    Post subject:  

Fundamentally, without Xephyr (X separation) container security is relatively weak. Accordingly I've simplified my setup to be just the main session and a Xephyr/unshare/capsh/chroot container session, that both use the same easy.sfs base, but each having its own separate changes folder.

I've also set it up so that at each reboot, and each start of the container results in a sfs copy of the 'clean' changes folder content being used. i.e. at bootup the main systems changes.sfs is unsquashed as the changes folder area, and the same for the container. In effect not saving changes. Only when I run a mksquashfs of the changes folder are changes applied to future boots/loads.

I've also split the main tray to be shorter, with the containers tray filling the gap whenever that's loaded.

Makes EasyOS a lot easier IMO. Validation of the mbr, grldr, vmlinuz, initrd, easy.sfs, main systems changes.sfs and container systems changes.sfs ... also provides potential intrusion detection flags.

Another issue I have with EasyOS 1 is of conflict if other sfs's such as devx are loaded. I found that merging the main sfs with devx sfs to work better for me. But I frugal boot and don't copy the main sfs into ram at bootup, so size of easy.sfs isn't a issue (mines around 1GB when lzo level 1 compressed i.e. perhaps around 2GB uncompressed). That would perhaps be a issue for flashstick based boots.

Yes it does make bootup or starting the container slower. For instance both of my changes sfs files for the main and container are around 130MB, predominately because I have firefox portable also installed into both. But I show the unsquashfs progress bar as a visual indicator and it only takes a few seconds to complete, such that in a 'typical' setup the delay is acceptably small. Whilst I could run firefox portable outside of EasyOS space (same version used for both the main session and container) which would reduce down bootup and container load times, I prefer rolling back to clean versions of firefox at each reboot/container start.

Typically now I only update the snapshots (clean versions) when a new firefox version is apparent. i.e. when I see firefox was updated, then reboot (or restart container) clean, and let firefox update again, then run the snapshot update so that new version of firefox is used in subsequent reboots (or container started).

Quite a few do seem confused by EasyOS. Perhaps simplification in Easy 2.0 such as the above two desktops only arrangement might help reduce such confusion. That way, the default version would comprise vmlinuz, initrd, easy.sfs, container-changes.sfs (that likely would be very small). And then once installed/run, the main sessions changes.sfs is added to that (after the user 'saves' (creates a snapshot of the main systems changes).
s.png
 Description   
 Filesize   53.74 KB
 Viewed   1208 Time(s)

s.png


_________________
( ͡° ͜ʖ ͡°) :wq
Fatdog multi-session usb

echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3252

PostPosted: Sat 30 Mar 2019, 09:14    Post subject:  

Cautionary advice. If like me you're no firewall rules expert then be mindful that Puppy (or at least EasyOS 1.0) creates a allow all rule as the first line in iptables.

You can inspect the rules using
Code:
iptables -L -n --line

I'm running a open ssh server in a container and wanted to block China IP's due to the high volume of ssh hack attempts that originate out of China, and originally created a script to add (append) those IP's into iptables, but had to change that code to insert each DROPped IP at the start of iptables i.e. now looks like ...
Code:
cd /etc
wget -P . http://www.ipdeny.com/ipblocks/data/countries/cn.zone
# Add each IP address from the downloaded list into iptables
for i in $(cat /etc/cn.zone ); do
   iptables -I INPUT 1 -s $i -j DROP
done

If (as per my original code) the IP drops are just appended (-A) then as sequence/order matters in iptables, the seemingly dropped IP's could still connect due to being overiden by the very first allow all default rule that puppy firewall sets up.

I call that script in /etc/init.d/rc.firewall (appended it at the end), which does slow down initial net connect upon bootup considerably, can be a few minutes before the trays network icon changes from disconnected to connected (i.e. the above script completes due to the high number of IP's being inserted one by one into iptables). For me that isn't a issue and there are quicker/easier ways, such as using iptables-save and then restoring the save, however for my purposes as the China list is quite dynamic I prefer to grab (wget) and install the latest version of IP's at each reboot. Doesn't seem to affect just restarting X, i.e. exit/restartx again and it net connects quickly (I guess the firewall/network doesn't cycle as part of just restartX).

I verified that insertions at the top of dropped IP's did work by using a online ssh in browser service and connected using that, noted its IP number (/var/log/messages) and then inserted a DROP for that IP into IP tables, after which I couldn't connect.

I have my ssh running without userid and without key authentication i.e anyone can access it running as spot inside a Easy container where spot has its own bespoke shell ... that has very limited commands available. That's only accessible when my PC is booted and the container is running, but you might be able to drop in by opening a terminal and running
Code:
ssh -t -p 443 ssh@ssh.ddnsfree.com
.
If once connected you type help, there's a few other tricks you can do, such as directly download/play sounds/videos. Bear in mind however that I don't check connections before rebooting etc. so being able to connect is subjective as is continuity of connections. I've another thread about ssh here

For instance open a terminal window and run
Code:
ssh ssh-p 443 ssh@ssh.ddnsfree.com 'testvideo' | mpv -

You can even run mpv (or vlc) in the framebuffer i.e. ctrl-alt-F2 and login as root (woofwoof password unless you've changed it). On my kit I have to actually download the video i.e.
Code:
ssh -p 443 ssh@ssh.ddnsfree.com 'testvideo' >bb.mkv

and then I can run that in the framebuffer (i.e. run mpv bb.mkv)

_________________
( ͡° ͜ʖ ͡°) :wq
Fatdog multi-session usb

echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh
Back to top
View user's profile Send private message 
FeodorF


Joined: 07 Jul 2010
Posts: 258
Location: Heidelberg, Germany

PostPosted: Thu 11 Apr 2019, 06:51    Post subject: Scanner doesn't work in EasyOS 0.9.x ... 1.0.xx [SOLVED]
Subject description: Scanner connected via parallel port
 

My scanner doesn't work with EasyOS [SOLVED]

I'm still using two old Mustek-600-III EP (ccd300) scanners with Quirky Xerus 8.5 via line printer port. The scanners were never detected while using EasyOS. Yesterday I did some reading at:

//forum.ubuntuusers.de
user 'Kellerkind_2009' from Schleswig-Holstein had a smart idea.

Entering "export SANE_DEBUG_DLL=255 && scanimage -L" into the terminal.

This showed right away what was wrong.

Troubles found:
=========
1) /etc/sane.d/DLL.conf 'mustek_pp' is not activated
2) /etc/sane.d/ 'mustek_pp.conf' is missing
3) /usr/lib/sane/ 'libsane-mustek_pp.so.1.0.25' and 'libsane-mustek_pp.so.1' (link) are missing
4) /usr/lib/ 'libieee1284.so.3.2.2' and /usr/lib/ 'libieee1284.so.3' (link) are missing

To fix the problem I copied everything that showed up missing from Quirky Xerus 64-bit to my EasyOS setups.

mustek_pp.conf needs three entries:
#
option no_epp
auto probing:
scanner mustek-ccd300 * ccd300
Scanner-not-found.png
 Description   
 Filesize   7.93 KB
 Viewed   685 Time(s)

Scanner-not-found.png


Last edited by FeodorF on Wed 17 Apr 2019, 05:05; edited 1 time in total
Back to top
View user's profile Send private message 
rufwoof


Joined: 24 Feb 2014
Posts: 3252

PostPosted: Thu 11 Apr 2019, 14:59    Post subject: EasyOS as a ssh server  

For cross reference purposes ... http://murga-linux.com/puppy/viewtopic.php?p=1024991#1024991 ... that outlines a potential means to have multiple ssh logins to EasyOS (i.e. EasyOS running as a ssh server), to each have their own unique environment upon login. ssh login in as user 'ssh' and end up running as user spot within a EasyOS container, that is separate from anyone else that might also ssh login as user 'ssh'.

And where for each, its just a aufs mount of the EasyOS sfs, alongside a 'changes' folder, that yields a 'top' folder that is chroot'ed into. i.e. very low overheads (and very quick to set up).

I have ssh userid set with no password, so ssh'ing into it doesn't require a password of ssh keys. Open access. As chroot and sys_admin capabilities are dropped, and its running as spot that can't su or sudo inside the container, nor can it see/mount the main systems HDD's then very limited to what damage such open access might achieve, other than the destruction of the containers content, which is disposable anyway (I remove the 'changes' folder after disconnect/logoff, so each new login starts 'clean'). As security flaws/cracks could still potentially occur however, it would be best if that sort of setup was run on a DVD based setup, with no local HDD's and ideally on a separate LAN segment (isolated from the rest of the LAN).

_________________
( ͡° ͜ʖ ͡°) :wq
Fatdog multi-session usb

echo url|sed -e 's/^/(c/' -e 's/$/ hashbang.sh)/'|sh
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1484
Location: not Bulgaria

PostPosted: Thu 11 Apr 2019, 20:59    Post subject:  

rufwoof wrote:
Finding that running large LibreOffice spreadsheet or word documents across Xephyr is very laggy. i.e. DISPLAY=:1 swriter from the main session, so I can cut/paste from firefox running inside the (:1) container, has swriter as good as useless (very slow to scroll etc.).

Seems to be Xephyr alone causing that lag.


I haven't tried EasyOS as yet but often used Xnest and Xephyr in the past and been doing a lot with overlayfs in VoidLinux of late to provide persistence and allow use of sfs files using chroot into separate overlays of main system. If you are running apps in some kind of chroot setup, an alternative to using Xnest or Xephyr is simply to do things the other way round to what I gather you've been doing i.e. start the app up in the chroot but make DISPLAY point back to the main session DISPLAY as outlined here:

https://wiki.gentoo.org/wiki/Project:X86/Chroot_Guide#Running_X_apps_inside_the_chroot

In terms of security, I suggest using sshd server running in your container and then ssh -X (tunnel) into that from client on main desktop session (if that is possible?) - that should set DISPLAY automatically whilst providing secure X communications. Then I guess cut and paste and so on would work fine.

Whilst I don't know how EasyOS implements containers, I came across the following for Docker (EDIT: though I haven't myself ever used Docker so don't know the ins and outs of it):

https://stackoverflow.com/questions/47800486/ssh-between-local-docker-containers
https://docs.docker.com/engine/examples/running_ssh_service/

https://unix.stackexchange.com/questions/12755/how-to-forward-x-over-ssh-to-run-graphics-applications-remotely

Alternatively, and even safer, use VNC over ssh.

http://nnc3.com/mags/Networking2/ssh/ch09_03.htm
https://help.ubuntu.com/community/VNC

wiak

_________________
Tiny Linux Blog: http://www.tinylinux.info/
Check Firmware: www.murga-linux.com/puppy/viewtopic.php?p=1022797
tinycore/slitaz: http://www.murga-linux.com/puppy/viewtopic.php?p=990130#990130
Back to top
View user's profile Send private message 
FeodorF


Joined: 07 Jul 2010
Posts: 258
Location: Heidelberg, Germany

PostPosted: Fri 12 Apr 2019, 03:14    Post subject: Pale Moon as an alternative to Sea Monkey 2.49.4
Subject description: Installing Pale Moon 28.4.1 to EasyOS 0.9.x ... 1.0.xx
 

If someone would like to give 'Pale Moon 28.4.1' a go on EasyOS look right there for your download:
http://linux.palemoon.org/datastore/release/palemoon-28.4.1.linux-x86_64.tar.bz2
Download x64 tar.bz2 (direct download)
Size: 46.64 MB
SHA-256 checksum: fcf92a086019f22880e54fa83d5a43033d0c26349d3a86cbc64612443146e37a
System requirements: http://linux.palemoon.org/download/mainline/

How-To-Install/Setup:
Click on the downloaded file and extract it to /usr/lib
pull /usr/lib/palemoon/ palemoon to the desktop

The following changes might be helpful:
->Tools->Prefrencess->General->Startup: file:///usr/share/doc/easy/home_en.htm
->Tools->Preferences->General->Startup: Show my windows and tabs from last time
->Tools->Preferences->Tabs: Always show the tab bar
->Tools->Preferences->Advanced: deactivate 'Use smooth scrolling'
PaleMoon.png
 Description   
 Filesize   8.01 KB
 Viewed   544 Time(s)

PaleMoon.png

Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 102 of 106 [1581 Posts]   Goto page: Previous 1, 2, 3, ..., 100, 101, 102, 103, 104, 105, 106 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Derivatives
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0906s ][ Queries: 12 (0.0177s) ][ GZIP on ]