EasyOS version 2.3.2, June 22, 2020

[slavvo67]

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]

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]

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]

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]

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]

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]

Yes that's how it done in 710 .
_______________________

[slavvo67]

BarryK:

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

Best,

Slavvo67

[tigs]

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]

what happened to the forum?

[BarryK]

what happened to the forum?

Do you mean lack of recent posts to this thread?

I have been working on other things.

There are various issues reported, intend to get onto them soon. Also; planning a Bionic Beaver easyOS release soon.

[BarryK]

Can't find the post, think it was quite a way back in this thread, a report that booting with "qfix=bak" (or just choose from boot menu), it rolls back to a pristine first-bootup, not to last saved session. I think it was rufwoof who reported that.

Fixed.

[rufwoof]

a report that booting with "qfix=bak" (or just choose from boot menu), it rolls back to a pristine first-bootup, not to last saved session. I think it was rufwoof who reported that

Tip : A good way to search the forum is to use google and append

Code: Select all

site:murga-linux.com

to your search criteria. For instance when I did a google search of

Code: Select all

rufwoof qfix=bak site:murga-linux.com

that came back with a link to this threads page 57 link that contains
http://murga-linux.com/puppy/viewtopic. ... 363#994363

[Billtoo]

I installed to a 64gb flash drive:

System: Host: EASYPC28367 Kernel: 4.18.8 x86_64 bits: 64 Desktop: JWM git-1685 Distro: Quirky 0.9.3 beaver64
Machine: Device: desktop System: HP product: 260-p029 serial: CNV6240BWP
Mobo: HP model: 81B4 v: 01 serial: PFPSK0BWJ301LW UEFI [Legacy]: AMI v: F.04 date: 05/10/2016
CPU: Dual core Intel Core i3-6100T (-MT-MCP-) speed/max: 823/3101 MHz
Graphics: Card: Intel HD Graphics 530
Display Server: X.Org 1.19.6 drivers: modesetting (unloaded: fbdev,vesa) Resolution: 1600x900@60.00hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) version: 4.5 Mesa 18.0.5
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
Card-2: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be
Drives: HDD Total Size: 1064.7GB (0.9% used)
Weather: Conditions: 68 F (20 C) Time: September 19, 1:52 AM EDT
Info: Processes: 128 Uptime: 55 min Memory: 325.5/3873.7MB Client: Shell (bash) inxi: 2.3.56

Installed some applications with petget, haven't explored much yet.

Thanks for the new version.

[BarryK]

Yes, EasyOS "Easy Beaver" 0.9.3 is out, built from Ubuntu Bionic Beaver 18.04.1 LTS DEBs. Blog announcement:

http://bkhome.org/news/201809/easy-beav ... eased.html

[BarryK]

Regarding Easy Beaver 0.9.3, it is interesting that Xorg now defaults to using the modesetting driver, not the intel driver (when your PC has intel video). I did see a post about that somewhere.

You would have to run the Xorg Wizard to change to the intel driver.

scsijon sent me an email, the 4.18.8 kernel has a security flaw. I am compiling 4.18.9 right now.

There was another email with some bug reports, one of them was that the youtube downloader doesn't work. Will check that out. Looks like a bugfix release is coming very soon!

Note about youtube downloader, it uses youtube-dl, which is a perl (python?) script. It has to be upgraded every now and again, as youtube.com people move the goal posts, to foil downloaders.

[rufwoof]

Easy Beaver 0.9.4 frugal installed to HDD (272GB free space). Booted straight to desktop (used to have to run xorgwizard for my Radeon ATI). Seamonkey container - youtube sounds etc. OK.

Didn't have a Easy to hand, so had to extract the BOOT_SPECS old-school style. fdisk -l for the nix I was running didn't show DiskID either so had to resort to lsblk -O. Even then I messed it up by not duplicating the UUID in the two entries (and nearly forgot to add the trailing slash on the paths (but seem to recall that might no longer be a necessity).

Great choices available in the extensive repo's.

Containered Seamonkey was slowish to load, recompressed the sfs and much better. Does still seem to have some juttery performance at times, maybe the newer kernel isn't so good on my 10 years old Phenom X4 (maybe I just need to tweak some things).

Boy, to get to the containers seamonkey UserChrome.css to tweak to a larger font ... buried so deed.

Love the containerisation. I'm now running with data on a pure OpenBSD base system (old single core) box, that reverse sshfs mounts one of its folders, no inbound originated accepted so secure - excepting the data folder content that is presented via sshfs. With main Easy B' acting as the manager, browser running in refreshed containers, sshfs mount my android phone - a very nice combination

As I'm typing this (with Miss Monique video playing in the background), I am getting key stutters. Relatively frequently - type a few letters and the cursor/screen lags behind maybe for a few letters before presenting them in a single update type behaviour.

[rufwoof]

Trying another post after having reverted back to a clean seamonkey container snapshot (I've also copied across the hosts (pup ad block) file from the main session into the seamonkey container's /etc/host file - before making another 'clean' seamonkey container snapshot) and without youtube playing - text entry is nice/normal (responsive).

[rufwoof]

Easy B' 0.9.4. Containers show comment option - when clicked after a container/snapshot is selected shows a empty leafpad text editor content despite the snapshot having comments added.

[scsijon]

Barry, I've come across f2fs in the latest set of kernel fixes and wonder if it could be at least added to the kernel config for testing and comparison please when you build the kernel next.

F2FS 's origons are back in 3.8 in 2012 and is designed to build a linux filesystem that, from the start, takes into account the characteristics of flash memory-based storage devices. Nowadays it includes such devices as solid-state disks, eMMC, and SD cards, which are being widely used in systems ranging from embeded mobile devices through to large scale server farms.

It was origonally a Samsung package with Jaegeuk Kim being the principal F2FS author so it's not a quick-lifespan filesystem as some have been.

Further details at wikipedia https://en.wikipedia.org/wiki/F2FS and kernel.org's wiki https://f2fs.wiki.kernel.org/ to start with.

It seems to be on par with ufs for us, with the only problem at present for us being that currently it's not grub compatable, which is why I only ask for testing not release.

People like Greg Kroah-Hartman (linux-foundation) and Sasha Levin (think microsoft's top filesystem person) are also directly involved so it's got some backing after six years.