EasyOS version 2.3.2, June 22, 2020

For talk and support relating specifically to Puppy derivatives
Message
Author
Antipodal
Posts: 253
Joined: Thu 26 Mar 2009, 16:52
Location: The other side of the world

Re: gnumeric

#961 Post by Antipodal »

lp-dolittle wrote:you should transform the Gnumeric-files into the *.odf-format in the OS which you used so far, and which obviously was able to run Gnumeric.
Yes, transforming them into .ods from Gnumeric on another operating system allowed me to (after closing a little window that said "not all attributes could be read") read them with Libre Office in my EasyOS.
lp-dolittle wrote: Start LibreOffice.Calc, go to 'File' > 'open' > 'All files', and then scroll down until you reach the Gnumeric-option.
In my case it didn't work. Working from my EasyOS, and using Libre Office I was able to transform another .gnumeric file into a .ods but when I tried to open it, a "Text Import Configuration" opened. Without making any changes on it I clicked on its OK button and after (at least) 15 minutes a little window with an OK button announced "The data could not be loaded completely because the maximum number of character per cell was exceeded" and a chains of characters that were not what I was expecting appeared. Take a look at them in the attachment.

@ Cu Chulinux

I'm extremely bad at working on the CLI .
I will put your comments in the list of things I must study and test.
I'll let you know if I get to solve the problem following your indications.

Thank you both for sharing your experiences.
Attachments
2018-08-06.png
(65.44 KiB) Downloaded 1229 times

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

#962 Post by step »

I copied the easyOS 0.9.6 gz to an 8GB USB stick per instructions and attempted a Normal boot on a netbook. It failed I think immediately after creating the repository partition. The limited netbook console shows the following text:

Code: Select all

Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 1
Number of ids (uniqui uids + gids) 1
Number of uids 1
      unknown (0)
Number of gids 1
      unknown (0)

sed: can't create temp file '/mnt/sdb1/syslinux.cfgXXXXXX': Read-only file system
sed: can't create temp file '/mnt/sdb1/EFI/BOOT/refind.confXXXXXX': Read-only file system
Mounting read-only layer of layered filesystem
   Mounting squashfs file q.sfs
mont: mounting /dev/loop0 on /q_ro/q_sfs failed: Invalid argument
ERROR: failed to mount q.sfs
Have now dropped into a shell in the initramfs.
Note1: Type "exit", the int script will attempt to continue, however,
       only an expert who is debugging the bootup should do this.
Note2: On some PCs the keyboard does not work at this stage of bootup.
PLEASE HOLD DOWN THE POWER BUTTON TO SHUTDOWN
/bin/sh: can't access tty; job control turned off
#
Typing "exit" leads into a kernel panic.

edit: I repeated all steps with the same USB stick. Before the first boot I confirmed that partition easy1 is writable (touch x; rm x)

While preparing the stick with dd and before dd finished, dmesg showed the following error messages

Code: Select all

[ 5705.042343]  sdh:
[ 5705.044440] sd 9:0:0:0: [sdh] Attached SCSI removable disk
[ 5787.007670] udevd[464]: worker [18646] /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/host9/target9:0:0/9:0:0:0/block/sdh timeout; kill it
[ 5787.007685] udevd[464]: seq 3850 '/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8/2-1.8:1.0/host9/target9:0:0/9:0:0:0/block/sdh' killed
[ 5881.228189] udevd[464]: worker [18646] terminated by signal 9 (Killed)
edit2: Changed stick same errors, including dmesg. I wonder if it's due to the PC that I use to prepare the keys...
Last edited by step on Mon 06 Aug 2018, 16:58, edited 2 times 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]

Sage
Posts: 5536
Joined: Tue 04 Oct 2005, 08:34
Location: GB

#963 Post by Sage »

0.9.6 works well. Extract the .gz to the .img file and write it using USB Image Writer from one of the major distros. The CLI dd command seems to give lots of problems to the uninitiated so I leave that to the gurus and use the desktop utility.

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

#964 Post by rufwoof »

step wrote:I copied the easyOS 0.9.6 gz to an 8GB USB stick per instructions and attempted a Normal boot on a netbook. It failed I think immediately after creating the repository partition. The limited netbook console shows the following text:

Code: Select all

Number of device nodes 0
Number of fifo nodes 0
Number of socket nodes 0
Number of directories 1
Number of ids (uniqui uids + gids) 1
Number of uids 1
      unknown (0)
Number of gids 1
      unknown (0)

sed: can't create temp file '/mnt/sdb1/syslinux.cfgXXXXXX': Read-only file system
sed: can't create temp file '/mnt/sdb1/EFI/BOOT/refind.confXXXXXX': Read-only file system
Mounting read-only layer of layered filesystem
   Mounting squashfs file q.sfs
mont: mounting /dev/loop0 on /q_ro/q_sfs failed: Invalid argument
ERROR: failed to mount q.sfs
Have now dropped into a shell in the initramfs.
Note1: Type "exit", the int script will attempt to continue, however,
       only an expert who is debugging the bootup should do this.
Note2: On some PCs the keyboard does not work at this stage of bootup.
PLEASE HOLD DOWN THE POWER BUTTON TO SHUTDOWN
/bin/sh: can't access tty; job control turned off
#
I had a similar experience with 0.9.5 but sometimes it booted OK. I assumed it was a overused SD/MMC card, blowing and switching the caddy lock/unlock latch a few times seemed to do the trick.

I've dd'd 0.9.6 to the same 2GB MMC and it booted straight to desktop for me this time (usually have to run xorgwizard, but Barry's tweaks in 0.9.6 seem to have rectified that for my onboard Radeon/ATI.

I download and dd'd using OpenBSD

Code: Select all

root@acer> gzip -d eas*.gz    
root@acer> dmesg | grep MMC   
sd3 at scsibus2 targ 1 lun 2: <Generic-, SD/MMC, 1.00> SCSI0 0/direct removable                                         
root@acer> disklabel sd3      
# /dev/rsd3c:                 
type: SCSI                    
disk: SCSI disk               
label: SD/MMC                 
duid: 0000000000000000        
flags:                        
bytes/sector: 512             
sectors/track: 63             
tracks/cylinder: 255          
sectors/cylinder: 16065       
cylinders: 246                
total sectors: 3964928        
boundstart: 0                 
boundend: 3964928             
drivedata: 0                  

16 partitions:                
#                size           offset  fstype [fsize bsize   cpg]                                                      
  c:          3964928                0  unused                                                                          
  i:          1308672             2048   MSDOS                                                                          
  j:          2654208          1310720  ext2fs                                                                          
root@acer> dd if=easy-0.9.6-amd64.img of=/dev/rsd3c bs=1M                                                               
641+0 records in              
641+0 records out             
672137216 bytes transferred in 93.238 secs (7208771 bytes/sec)
All looks good so far, but limited use (ran through the first run setup, turned firewall on, run the Puppy ad-block setup, added video=800x600 to the "normal" boot parameters in syslinux.cfg on sdd1, increased dpi to 130) and rebooted a second time ... to see the desktop pop up ok).
[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]

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

#965 Post by step »

Still unable to make 0.9.6 complete the first boot I prepared the same two sticks on a different PC, and tested them on the same netbook. I got the same error message that I reported three posts above.

I prepared the sticks again and this time I tested them with my desktop PC. No errors, easyOS completed the first run setup. Then I shutdown my PC and tried booting the now-fully-initialized stick on my netbook. This time it booted straight to desktop.

So it's possible that easyOS generates an error trying to complete the first boot on that netbook only, which is an ASUS 1001 PX with 2MB RAM and an SSD that replaced the HDD.

All sticks were prepared with dd following the instructions on the EasyOS web page.
[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]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#966 Post by BarryK »

I have posted about 'adbfs', a possible contender for seamless integration of Android phone file access into EasyShare:

http://bkhome.org/news/201808/android-t ... in-oe.html

Only tested with usb cable, but in theory could work over wifi, I think.

But, EasyShare is already using sshfs, so it would seem a logical step to use sshfs also for the phone. There are some apps for the phone, SSHelper and SSHDroid -- has anyone experience with these?

Or any other simple way to view the files in the phone with a file manager?

There is an old method, where Android could be set to behave as "usb mass storage device" over usb, the simplest, but I read somewhere, that is no longer supported in Android.
[url]https://bkhome.org/news/[/url]

foxpup
Posts: 1132
Joined: Fri 29 Jul 2016, 21:08

#967 Post by foxpup »

BarryK wrote:Or any other simple way to view the files in the phone with a file manager?
Probably not want you want: dukto
http://murga-linux.com/puppy/viewtopic.php?p=997259

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

#968 Post by rufwoof »

BarryK wrote:EasyShare is already using sshfs, so it would seem a logical step to use sshfs also for the phone. There are some apps for the phone, SSHelper and SSHDroid -- has anyone experience with these?

Or any other simple way to view the files in the phone with a file manager?
cli with tmux and mc are a great combination IME. ssh into a box, run tmux and you have multiple terminals (windows) that you can scroll, cut/paste etc. Two of you can even ssh into the same box using the same userid and attach to the same tmux session so you can collaborate. mc over ssh and running in a tmux window works reasonably well and provides a easier text editor than using vi or whatever. You can also detatch from a tmux session whilst it continues to run in the background, and later reattach again perhaps using another device such as a smartphone and continue on with that session. https://news.ycombinator.com/item?id=3438732. You can also run X over ssh, ssh -X someIP ... type switch, such that you can open a X window on the remote and see it on your local X screen.

For file transfers I tend to use scp, pretty much the same as normal cp but where you prefix the filename with user@IP: for the remote end of the cp action. scp somefile user@somehost:/home/user/somefile type syntax. sshfs is another thing worth looking at, in effect mount a fs over ssh so that it appears as a local mount point that you can then open/transfer files etc. using rox or whatever - as though it were any other local folder.

Running a free dynamic name service is useful, as you have a static domain name associated to a dynamic IP. I use ddnsfree so that whenever my desktop is up and running its web server can be accessed by anyone using a static domain name. Handy for sharing larger files that cannot be sent/received via email. i.e. drop it into your web server folder, open up http port forwarding so others can http://.... in and download the file(s).

Generally for a desktop setup you'd more often have remote http and ssh turned off for security reasons, only opening them up on a as and when basis and turning them off again afterwards. Having those all set up and ready to go (running, but not remotely accessible) does make it easier for when you do want to "turn them on" (permit remote access).
[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]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

Re: Possible Bug?

#969 Post by BarryK »

belham2 wrote:Hi Barry,

Possible BUG to report.

0.9.5 Easy

Network Tray Icon --- impossible to "Disconnect from Network" as a right-click option. Nothing happens.

Also, if you physically unplug the network cable from your machine/laptop---the tray icon still assumes it is connected (this despite wi-fi is not enabled nor in the picture).

This "bug" has happened with Easy 0.9.5 across several intel & amd platforms. For those that like to "work-offline", this bug is a bit of a pain.


Thanks.
Yes, this is a very old bug. It occurs when ethernet connection has been auto-detected at bootup, so none of the connection wizards got run.

Fixed, so now the "Disconnect from network" and "Reconnect" work.
[url]https://bkhome.org/news/[/url]

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

#970 Post by step »

I plugged in an SD card and easy didn't show a desktop icon for it. dmesg shows the following error:
udevd[4068]: failed to execute '/usr/sbin/obex-check-device' '/usr/sbin/obex-check-device 058f 6366': No such file or directory
[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]

lp-dolittle
Posts: 156
Joined: Mon 25 Apr 2016, 17:35

EasyOS Pyro 0.9.6

#971 Post by lp-dolittle »

@ Barry,

running EasyOS 0.9.6 via an external card reader (on several laptops which are unable to boot directly from the internal card slot; EasyOS installed on a 64 GB Micro SD-card), I'm faced with a so far unnoticed problem. As soon as I try to insert an additional flash-stick, I get the following error message:

Error saving pinboard /root/Choices/ROX-filer/PuppyPin: input/output error

Thereafter, the desktop proves to be partially or fully unresponsive, and irrespective of whether the OS can be restarted via the reboot command or only via a hard shutdown, during the reboot process a filesystem check is performed. Sometimes, the reboot only works at a second attempt because the correct decryption password initially is rejected until a new reboot is initiated by pressing the ctrl-alt-delete keys.

scsijon
Posts: 1596
Joined: Thu 24 May 2007, 03:59
Location: the australian mallee
Contact:

#972 Post by scsijon »

Since you have android in easyshare i was wondering what we do about i-phones?

User avatar
technosaurus
Posts: 4853
Joined: Mon 19 May 2008, 01:24
Location: Blue Springs, MO
Contact:

#973 Post by technosaurus »

scsijon wrote:Since you have android in easyshare i was wondering what we do about i-phones?
Get a bunch of them and use them to tile your bathroom.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#974 Post by BarryK »

@G@tA wrote:Hi all,

what is the root password for Pyro 0.9.5?

I've started SSHD on it and allowed root login. But woofwoof as password wont apply. Also the password from beginning at boot doesn't apply.
The default password for root is woofwoof, however, in the next release of EasyOS, it will be automatically set to whatever password you entered at bootup.
[url]https://bkhome.org/news/[/url]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

Re: initial EasyOS password

#975 Post by BarryK »

lp-dolittle wrote:@ Barry,

maybe, it should be mentioned that the setting of the initial EasyOS password, irrespective of the keyboard's layout, always follows the US American default. Later changes of the keyboard setting do not affect this setting but may create confusion since the booting OS asks for 'the correct sequence of keyboard hits' and not for the characters and symbols which the user saw when the password was set, and whose location, on a non-US keyboard now may have changed!

Furthermore, I realised that at bootup, during password-toggling, wrongly set characters cannot be deleted. Every hit - also hitting the delete-key - results in the addition of a *.

kind regards
I've been thinking how to fix this. Maybe the user could make a choice about basic keyboard layout, such as azerty, qwerty or qwertz, then enter the password.

...but, that leaves out all the non-Latin keyboards.

Or, all of the console keyboard layouts can be presented, maybe as a numbered list, the user types a number, then the password.
[url]https://bkhome.org/news/[/url]

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#976 Post by don570 »

Maybe the user could make a choice about basic keyboard layout, such as azerty, qwerty or qwertz, then enter the password.
This makes sense to me.

Apparently there is a large number of dvorak keyboard layouts, however
anybody who can use a dvorak keyboard layout can use azerty, qwerty or qwertz.
_____________________________________________________

lp-dolittle
Posts: 156
Joined: Mon 25 Apr 2016, 17:35

initial EasyOS password

#977 Post by lp-dolittle »

@ Barry,

in order to spare you complex modifications of the EasyOS setup, I'm thinking of a pragmatic alternative. In fact, a simple alerting notification might do.

I imagine an obvious hint which points out that the initial password-setting follows the US-keyboard layout and that users of other keyboards, in view of ensuing boots, strictly should remember the SEQUENCE of the keys, including the SHIFT- and ALT-combinations, which were hit when the encryption password was set. This way, everybody later can feel free to 'translate' the password according to any currently used keyboard's layout.

At the same time, I again would like to mention that the XKB Configuration Manager's 'third level chooser'-option might be a source of confusion, as for the EasyOS container-specific ALT+F6 command.

kind regards

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#978 Post by don570 »

If the password was a seven digit number i.e. the user's telephone number
then it wouldn't matter if azerty, qwerty or qwertz.
___________________________________________________

Or maybe six numbers (or eight) --> the person's birthday

08/18/18

08/18/2018
____________________________________

User avatar
Cu Chulinux
Posts: 59
Joined: Sun 28 Jan 2018, 18:49
Location: About 180 degrees from Australia

#979 Post by Cu Chulinux »

I installed Easy 0.9.6 to USB and it worked fine.

I upgraded my hd install of Easy and for the second upgrade in a row it did not cleanly boot. It refused to boot to X. Boots to console fine, I ran xorgwizard and tried a number of options but still no X screen.

I tried renaming the .sessions dir and rebooting to a pristine install - still no joy. This time it booted to a gui but with a solid grey background and three choices in window menu: xterm, reboot, and exit I think. Looked a lot like the old twm or maybe fvwm. There was a panel on the bottom but no menu there.

I also installed Quirky 8.6. It works well as long as I don't change the display DPM. If I do that the screen will freeze after a few minutes.

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

#980 Post by rufwoof »

EasyPyro 0.9.6

Would be nice to have user rover set as a member of the audio group by default

Code: Select all

adduser rover audio
Also extend /usr/bin/seamonkey to include rover in addition to spot i.e. changing the code snippet ....

Code: Select all

NAMEOFUSER="$(id -n -u)"                                                        
if [ "$NAMEOFUSER" == "spot" ];then                                             
 HOMEDIR="/root/spot/.mozilla/seamonkey"                                        
 NAMEEXE='seamonkey.bin'                                                        
else #called as seamonkey or mozilla...                                         
 HOMEDIR="/root/.mozilla/seamonkey"                                             
 NAMEEXE='seamonkey'                                                            
fi
to

Code: Select all

if [ "$NAMEOFUSER" == "spot" ];then                                             
 HOMEDIR="/root/spot/.mozilla/seamonkey"                                        
 NAMEEXE='seamonkey.bin'   
else
 if [ "$NAMEOFUSER" == "rover" ];then                                             
  HOMEDIR="/home/rover/.mozilla/seamonkey"                                        
  NAMEEXE='seamonkey'   
 else #called as seamonkey or mozilla...                                         
  HOMEDIR="/root/.mozilla/seamonkey"                                             
  NAMEEXE='seamonkey'                                                            
 fi
fi
As that eliminates the long delayed orange coloured message box and sets things up correctly for rover.

Having a /home/rover/.profile that

Code: Select all

export DISPLAY=:0
would also help.

With the above, starting the desktop and running the container console (icon near the top/middle of screen) ... to open a containered root cli, and then

Code: Select all

su - rover
so as to invoke rover cli (dash is important as that ensures rovers profile is run) ... and then running

Code: Select all

seamonkey
... has seamonkey start with sound enabled (rover being a member of audio group as above) i.e. running seamonkey in a container as a restricted userid with very low levels of permissions/authority (running capsh --print as rover in the sh0 (console) container shows a empty 'Current=' set of authorities :))

I've noticed that if you open up the easy version control (under the Filesystem menu) and select the sh0 drop down option in the bottom "Containers" section, then even with a 'empty' selection (no snapshots having been created), clicking Rollback clears out the browser session so its back to a nice clean version again. Otherwise even if you rollback the main 0.9.6 and reboot, former browser stuff under sh0 container still persists from earlier usage.
Attachments
capture24139.png
(65.88 KiB) Downloaded 898 times
Last edited by rufwoof on Mon 20 Aug 2018, 19:42, 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]

Post Reply