(old)Puppy Linux Discussion Forum

Ha ha, I don't let up!

EasyOS Pyro64 version 0.7 is out:

http://bkhome.org/news/201801/easyos-py ... eased.html

The big news is inclusion of EasyShare.

EasyOS Pyro64 version 0.7

Working well. Got working xorgwizard, auto-DHCP connected & Flash. Nothing not to like, so far.

Easy version 0.6.6

I returned to Easy version 0.6.6 to check why I was not able to
connect to a Samba sever with a second PC.

I found the reason

First here is what I did....

1) Fresh install of version 0.6.6 on USB stick
2) Booted and clicked 'Share' button
3) Selected firewall and then Samba setup
Selected everything but 'Printers' option. Clicked 'Apply'
4) Checked with a second PC running Fluppy 013.
It saw the share but couldn't make a connection.
5) I booted again the second PC with old Racy CD, but I had the same problem i.e. no connection was possible.
6) I nearly gave up , but I had a Raspberry Pi 2 board nearby so I tried it.
I booted it (Quirky Xerus OS) and used Yassm 2.9 to find share.
The share showed on list. I selected it and then clicked 'Mount' . Great!!
It did mount
(see image)

My conclusion -----

The previous OS's were old and were using 'pnethood' software.
Raspberry Pi2 was using a different way of connecting to share.

(Note that Easy pyro doesn't have this problem)
____________________________________________________

Here is how pnethood works from puppylinux.org

How it works
Each time the pnethood window is loaded it uses nbtscan to get a list of computers on the x.x.0.0/16 subnet corresponding to your IP address. Each one of these computers is then scanned for shares using smbclient. This list of shares is then compared with the output from mount to find out if any of them are mounted already. From this list the interface is generated.

________________________________________________________

YASSM 2.9 uses command http://murga-linux.com/puppy/viewtopic. ... 001#973212

EasyShare looks fantastic from your tutorial. I want to try it out on my network which is created from an android wifi hotspot connecting 4k tv, tablets, phones and laptops, i have an hp 2130 usb printer scanner to try and share. It will be great if as easy as shown ... ! I also wonder if it will find printers on campus network?

To Stemsee..

If you're connecting printers you should use most recent version of Easy 0.7
and read Barry's description...
http://bkhome.org/news/201801/easy-netw ... -cups.html
___________________________________________________

Thanks don570

I read it and I installed 0.7 to a usb 2 stick using Etcher, iso/img to usb writer. Worked great.

Easy touchscreen works well, no calibration needed. No two finger gestures yet working. Still an improvement.

No broadcom wl driver ... I have trouble compiling that one. Using usb wifi dongle.

So far so good!

stemsee

I installed to a 64gb usb-3.0 flash drive:

System: Host: EASYPC7089 Kernel: 4.14.13 x86_64 bits: 64 Desktop: JWM git-976 Distro: Quirky 0.7 pyro64
Machine: Device: desktop System: LENOVO product: 7491B8U v: ThinkCentre M58e serial: MJ01509
Mobo: LENOVO model: N/A serial: INVALID BIOS: LENOVO v: 5HKT39AUS date: 06/17/2009
CPU: Dual core Intel Core2 Duo E8400 (-MCP-) speed/max: 2011/3003 MHz
Graphics: Card: NVIDIA GF108 [GeForce GT 430]
Display Server: X.Org 1.19.1 drivers: nouveau (unloaded: modesetting,fbdev,nv,vesa)
Resolution: 1920x1080@60.00hz
OpenGL: renderer: Rasterizer version: 2.1 Mesa 17.0.2
Network: Card: Marvell 88E8057 PCI-E Gigabit Ethernet Controller driver: sky2
Drives: HDD Total Size: 509.4GB (0.6% used)
Weather: Conditions: 23 F (-5 C) - Overcast Time: January 18, 5:10 AM EST
Info: Processes: 105 Uptime: 27 min Memory: 264.3/3955.1MB Client: Shell (bash) inxi: 2.3.56

The system froze a couple of times, had to hold the power button down
until the computer shut down and choose to check the file system on the next bootup.

I installed Palemoon 27.7.0 and it's working well.

That's it so far, I will see if I can get my wireless printer working
later.

Thanks.

Billtoo wrote:The system froze a couple of times, had to hold the power button down
until the computer shut down and choose to check the file system on the next bootup.

Yeah, that is a mystery. I wish that I had a PC that has that bug.

Note to everyone: EasyShare is still in early days.

Currently supporting network printing with CUPS, and file sharing with Samba.

However, for Linux-to-Linux file sharing, Samba is sub-optimal.

I am planning to add a choice, so in EasyShare you can select to use Samba, sshfs or NFS. Also thinking about bringing in rsync.

I'm working on ssh right now. A PC can make a folder available for other PCs to log into, however, I have setup the local folder as a container. So, this will be ultra-secure ssh.

Also intending that this will be setup with just a few clicks, with the client having automatic discovery of the sshd server.

I installed easy 0.7 to an hp cherrytrail 2-in-1 and touch, wifi, bt all working. But the bt app does not connect and maintain a connection. /tried with headphones and android phone. It seems the app is expecting a string, but on the app end there is no input possible. This means bt connection can only be initiated from easy not from phone. Anyway, it works but a bug prevents connection persistence.

Would not even see my android 7 phone!

Is there a bug on line 93 of the formula script?

Till date I was not able to install EasyOs. I have tried to copy all the contents to folder. ( machine having lot other Puppy linuxs versions and try to boot the same through grub. Other distros with grub have identified and made the grub entry. However unable to load the easyOs during boot up due to kernal panic etc. I don't know whether I have done the right thing.

i don't know whether any mistake has been made in my Frugal Install. I having been following Puppy Linux from early days of puppy. I don't have any proficiency in programming etc. I don't have made 1 MB fat partition. Already machine having grub menu. Grub detected Easy Linux folder created in separate partition of ext4.

i would like to install and run EasyOs ? I also like to install easy Os and also with Network Printer having Department Id. please help with simple steps.

@rameshiyer
Did you go into initrd.q and adapt the file BOOT_SPECS?

The instructions for a frugal instruction is here
http://bkhome.org/easy/easy-frugal-installation.html

I was successful installing Easy 0.6.6 and Easy 0.7
_____________________________________________________

However I have some suggestions for improving the instructions.

1) The instructions are

Obtain the "uuid" by running blkid /dev/sda3 in a terminal.

The blkid version in easy pyro doesn't work, so
I had to run gparted and find the information for my partition
Partition > Information

EDIT: I was able to get the UUID using blkid /dev/sda1
using easy 0.7

2)Instructions are

Edit file BOOT_SPECS, that you will find in the opened-up initrd.q, so it looks like this:

BOOT_DISKID='0x50e598ae'
BOOT_PARTNUM=3
BOOT_FS='ext4'
BOOT_DIR='easy/easy-0.2.5/'
WKG_DISKID='0x50e598ae'
WKG_PARTNUM=3
WKG_FS='ext4'
WKG_DIR='easy/easy-0.2.5/'
Q_DISTRO_VERSION=0.2.5

You should emphasize that Boot and WKG are the same in a frugal install


3) When I was creating a frugal install of Easy 0.7 from another Easy
frugal install I noticed the following unusual instruction. (see image)
By the way I was installing on a ext3 hard drive partition.
The disk ID number was correct.
_______________________________________________________

Mypaint was able to use an external app (GIMP) to modify a layer. GOOD.

gmic plug-in for GIMP will work nicely in Easy

Available:
gmic-1.7.9-easy.pet
Size: 3.17mb

https://drive.google.com/open?id=1InHIK ... 9awtymD-cO
______________________________________

Blender 2.79 (most recent) will work on Easy 0.7
even if intel 945 graphics chip is used by machine
That means that OpenGL works.

Here is what a launch of blender looks like.

After spending a full day with Easy, I had a crash.
I seems that when I have a lot of windows open
the window manager makes a mistake and doesn't make a top window bar
for a window. I have to reboot.


I have never seen this problem with Fatdog linux.
It uses a special version of Rox filer.
https://github.com/jun7/rox-filer/

_____________________________________________

BarryK wrote:Did you try 0.6.6 on that PC?

It has different video software.

I have now. It still "freezes", just a bit differently: some parts of the desktop come up, aplet tray, icons, background, often misplaced, for a few moments, when I move the mouse it draws the track, and then the screen turns black while the computer keeps running. I have to stop it with the push button. On restart there is a fsck (wrong date less than a day in the future on block) and Easy may or may not get to X properly.
A sure way to get to X is to stop at the prompt and type xwin.
Same thing for Easy-0.7.

A quick progress report. Not posting much here, or my blog, as I am working on EasyShare "version 3".

This is a complete rewrite, with a fairly sophisticated GUI. With QuickSamba and the first version of EasyShare, any selections in the GUI caused the app to exit and restart, rebuilding the gtkdialog XML code. Now, mostly, the GUI updates dynamically without having to restart the app -- but this requires a lot more coding.

I have also had to learn more about gtkdialog, hence lots of questions posted here:

http://murga-linux.com/puppy/viewtopic. ... start=1230

EasyShare is making everything highly automated. File sharing is by Samba or SSHFS, the latter is best for Linux-to-Linux sharing.

I am hoping to create a PET so EasyShare can be used in other pups.

Along the way, have stumbled upon some bugs in Easy. There was a problem with containers, that may cause instability -- fixed.

There is still a small but serious oversight with the boot-up defaults - the default resolution is far too high to the point of risking failure if started on older monitor. Happened to me this morning when testing a SOTA with new PSU. Grabbed an older monitor - amazingly got a picture with 1600x1200 and an error message floating across stating 'out of range' or similar. Managed to drop to 1240x687/whatever without damage, but the risk of overdriving perfectly good test gear is there whether a liveCD.iso or a boot-USB stick is deployed.

Please, please, Barry - surely it can't be too arduous to adjust this? If you describe the modification(s) I'll give it try, but unless the source is changed, someone else could be seeing puffs of white smoke...

Today: confirmed risky default resolution on several additional systems.