EasyOS version 2.3.2, June 22, 2020

Message

rufwoof · #981 Post by **rufwoof** » Mon 20 Aug 2018, 19:05

As above (running container console and seamonkey), but changing it to use xephyr rather than xorg (Filesystem, easy container manager, selecting the sh0 dropdown and Edit to set EC_XSERVER='xephyr') and when you start the console container you get a black screen/desktop with just the console/terminal window. After starting seamonkey however you can ctrl-alt-F6 and see both the normal xorg X session with the console and seamonkey tray/taskbar entries.

Given that X is notoriously weak, potentially with a dark-hat able to see all other windows/key strokes, I assume that running under xephyr instead of xorg adds that bit extra protection ??? Raises the bar higher

rufwoof · #982 Post by **rufwoof** » Mon 20 Aug 2018, 19:15

Default (new) setup and the Main session desktop wallpaper looks fine. If I open the desk container however then the wallpaper looks wrong.

rufwoof · #983 Post by **rufwoof** » Tue 21 Aug 2018, 20:22

Had yet another case of the MMC/SD no longer booting - as though the flashstick/card had been overused/spent. Re-dd'ing and it works OK again.

Starting to suspect that it could be containers not closing down fully resulting in some file corruption such that a fsck is needed.

Seen one other (can't recall who) hereabouts who seemed to be encountering a similar problem so it could be a obscure bug.

BarryK · #984 Post by **BarryK** » Wed 22 Aug 2018, 01:02

Due to popular demand (well, two people, in the last few months), here is a 32-bit Pyro EasyOS, version 0.9.6:

http://bkhome.org/news/201808/easyos-32 ... n-096.html

Need an i686 CPU and has 4GB RAM limit -- the PC can have more, but the extra won't be recognized.

Cu Chulinux · #985 Post by **Cu Chulinux** » Wed 22 Aug 2018, 01:08

I got Easy 0.9.6 to work on HD. I had to start from fresh and boot to commandline and then rename /etc/11/xorg.conf.d/20-Intel-sna.confDISABLED to remove the "DISABLED". Then I could boot to X. Running xorgwizard didn't work and this laptop doesn't seem to like modesetting anymore. Initial bootups without making the change just went to a black screen with a cursor in the top left corner.

Problem is I have to re-setup everything all over again every time I upgrade, including manually setting sound in containers.

slavvo67 · #986 Post by **slavvo67** » Wed 22 Aug 2018, 01:41

BarryK:

While I've gotten away from 32bit distro's, I like the idea of supporting them. I actually have quite a few old, old computers that are 32bit only!

Going to play with this one a bit and maybe enhance or add to the software. Which WoofQ did you use to build it?

Update: Just tried it. Welcome back "Green Screen!" Missed you! Noticed DEVX is 0.6.1. Still okay to use or is there a newer one required? I know usually the older are okay.

Thanks,

Slavvo67

BarryK · #987 Post by **BarryK** » Wed 22 Aug 2018, 10:16

slavvo67 wrote:BarryK:

While I've gotten away from 32bit distro's, I like the idea of supporting them. I actually have quite a few old, old computers that are 32bit only!

Going to play with this one a bit and maybe enhance or add to the software. Which WoofQ did you use to build it?

Update: Just tried it. Welcome back "Green Screen!" Missed you! Noticed DEVX is 0.6.1. Still okay to use or is there a newer one required? I know usually the older are okay.

Thanks,

Slavvo67

Um, I will check that. Thought that I had uploaded 0.9.6 devx.

I also need to upload latest woofq, will do so and announce it.

EDIT:

The easyos devx 0.9.6 is there:

http://distro.ibiblio.org/easyos/x86/packages/sfs/pyro/

...um is "sfsget" looking in the wrong place? Maybe it is looking in the quirky repo on ibiblio, in which case, that's a bug.

Here is the latest woofq, 20180822:

http://distro.ibiblio.org/easyos/project/woofq/

BarryK · #988 Post by **BarryK** » Wed 22 Aug 2018, 10:19

I received an email from someone who prefers to remain anonymous, regarding a bug in easyshare.

For connecting to android phone, you have to manually create folder /mnt/phone

Do that before running easyshare.

BarryK · #989 Post by **BarryK** » Wed 22 Aug 2018, 12:39

Well, this is a pleasant surprise.

I have an old laptop, the first that I ever bought, an Acer Aspire 3681 WXMi, with 32-bit Celeron CPU, 512MB RAM, 60GB HDD, 1280x800 14.1 inch screen.

Dont recall what year I bought it. There is a reference to it in 2007:

http://bkhome.org/archive/puppylinux/ne ... 0b-300.htm

It has been in storage for years. Dug it out of the closet, connected power (the battery no longer holds a charge for more than a few minutes), plugged in EasyOS Pyro32 0.9.6, and it booted, everything runs, fast, a very nice experience.

It resurrects an old computer, so I can see why there is value in continuing to release a 32-bit distro.

Nooo, the usb mouse has stopped working! Touchpad still works. Oh well.

Replugged the mouse, it is working again. Interesting, anyone else ever had that problem?

rufwoof · #990 Post by **rufwoof** » Wed 22 Aug 2018, 13:41

BarryK wrote:Nooo, the usb mouse has stopped working! Touchpad still works. Oh well.

Replugged the mouse, it is working again. Interesting, anyone else ever had that problem?

Not with Easy, but in some other cases I've found that a USB mouse can repeatedly trigger interrupts (connected system messages). A cure for me (later (desktop) version of Acer Aspire) was to use a PS2 to USB adapter and have the USB mouse physically connected to the PS2 port. I've left it that way ever since and haven't seen any repeats of mouse issues.

slavvo67 · #991 Post by **slavvo67** » Wed 22 Aug 2018, 17:12

BarryK:

I put together with help from the web, a mouse and keyboard reset and made a menu entry under Utility called Reset Mouse and Keyboard. If you F12 and arrow down to choose, it should reset the mouse without rebooting. Feel free to adopt as needed....

#!/bin/bash
Xdialog -center -title "Mouse Reset" --no-buttons -infobox "USB mouse resetting now..." 0 0 3000
mousie=`lsusb|grep -i "mouse"`
bus1=$(echo $mousie | awk 'BEGIN {FS=" " }{print $2}')
device1=$(echo $mousie | awk 'BEGIN {FS=" " }{print $4}')
device2=$(echo $device1 | awk 'BEGIN {FS=":" }{print $1}')
usbreset /dev/bus/usb/$bus1/$device2 &&
Xdialog -center -title "Keyboard Reset" --no-buttons -infobox "Keyboard resetting now..." 0 0 3000
keyboard1=`lsusb|grep -i "keyboard"`
bus2=$(echo $keyboard1 | awk 'BEGIN {FS=" " }{print $2}')
device1b=$(echo $keyboard1 | awk 'BEGIN {FS=" " }{print $4}')
device2b=$(echo $device1b | awk 'BEGIN {FS=":" }{print $1}')
usbreset /dev/bus/usb/$bus2/$device2b &&
Xdialog -center -title "USB Resets Completed" --no-buttons -infobox "USB resets completed..." 0 0 2000

Sage · #992 Post by **Sage** » Wed 22 Aug 2018, 18:02

USB mouse can repeatedly trigger interrupts

- it must do this because it's an 'hot-pluggable (unpluggable) device", although some of the early v1.1 were not entirely reliably h-p. USB is sometimes claimed to be just a direct development of the PS/2 plug with hot-pluggability. Like all things in this field, early adopters will always encounter early flaws and oversights in the technology! Some keyboards were claimed to be USB or PS/2, some were supplied with an 'adapter' - most of the early 'adapters' didn't work, although some of the dual-purpose k/b s did actually work.
As for Easy32, bit of another catch-22. Loads of 'old' 32bit kit, BIOS-only, were not able to boot to an USB fob or SD card. Various SW utilities were offered to achieve this but for non-SW literaties like YT these weren't always easy to operate, esp. as some require a FDD as well and these are/were a disappearing feature. ipso facto, - thanks for the 32bit offering, very grateful, but generally speaking an .iso might be more reliable on anything over 5yrs old? Seem to remember an .iso writer from a running Puppy system? Never used it as it seem a bit beyond my ability, although that contention may need testing!

scsijon · #993 Post by **scsijon** » Wed 22 Aug 2018, 22:48

BarryK wrote:Need an i686 CPU and has 4GB RAM limit -- the PC can have more, but the extra won't be recognized.

quick thought

?4gig limit is 32bit, but maybe .....

extra ram => ramdisk

ramdisk => ram swapfile

ram swapfile could be set to be used before the hard drive swapfile, or disable use of hard drive swapfile if exists

can't remember what the program or lib was barry, but it was about the era of the mageia puppy's

regards

scsijon

damn class in ten minutes (teaching), got to go.

BarryK · #994 Post by **BarryK** » Wed 22 Aug 2018, 23:39

For the 32-bit Easy 0.9.6, the desktop "sfsget" icon doesn't work.

You need to gunzip the attached and copy it to /root/.packages

It has a variable that specifies where the sfs files are on ibiblio.org.

don570 · #995 Post by **don570** » Wed 22 Aug 2018, 23:48

BarryK wrote:Replugged the mouse, it is working again. Interesting, anyone else ever had that problem?

I was having a strange freeze of my mouse in Fatdog64 linux 710.
I thought it was serious, but after a lot of effort I discovered that fatdog has
set the function keys (by default) so that 'Xscreenshot' is launched if the print key is pressed.
http://www.lightofdawn.org/wiki/wiki.cgi/Xscreenshot

So I was accidentally pressing the print key and a cursor was appearing that I couldn't move.
My keyboard worked though. I should have pressed the ENTER key to take the screenshot.
____________________________________________

rufwoof · #996 Post by **rufwoof** » Thu 23 Aug 2018, 00:07

don570 wrote:I was having a strange freeze of my mouse in Fatdog64 linux 710.
I thought it was serious, but after a lot of effort I discovered that fatdog has
set the function keys (by default) so that 'Xscreenshot' is launched if the print key is pressed.
http://www.lightofdawn.org/wiki/wiki.cgi/Xscreenshot

So I was accidentally pressing the print key and a cursor was appearing that I couldn't move.
My keyboard worked though. I should have pressed the ENTER key to take the screenshot.
____________________________________________

For me (FD 721), when you press Print Screen the select cursor remains until you press Print Screen again. you can mouse click/drag regions and each time you release the mouse it creates a new image in your home folder of that region.

don570 · #997 Post by **don570** » Thu 23 Aug 2018, 00:12

Yes that's how it done in 710 .

_______________________

slavvo67 · #998 Post by **slavvo67** » Thu 23 Aug 2018, 00:20

BarryK:

Thank you. I note there are only 2 sfs files so far, though important ones.

Best,

Slavvo67

tigs · #999 Post by **tigs** » Sun 26 Aug 2018, 05:04

Trying the 0.9.6. It works perfectly fine booting from USB. But unable to boot to x from HDD. lots of kernel loading error. reverted back to 0.9.2 to check if the drive or partition was corrupted, the 0.9.2 booted just fine.

tigs · #1000 Post by **tigs** » Sat 15 Sep 2018, 22:01

what happened to the forum?

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

EasyOS version 2.3.2, June 22, 2020