EasyOS version 2.3.2, June 22, 2020
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
rufwoof posted awhile back that EasyOS did not go to sleep when the laptop lid is closed, and he created a fix:
http://murga-linux.com/puppy/viewtopic. ... 45#1025945
Thanks, that got me started, and hopefully now, we have sleep when lid is closed, and power-off when the power button is pressed:
http://bkhome.org/news/201907/acpi-hand ... press.html
Have only done this in theory, not yet tested.
http://murga-linux.com/puppy/viewtopic. ... 45#1025945
Thanks, that got me started, and hopefully now, we have sleep when lid is closed, and power-off when the power button is pressed:
http://bkhome.org/news/201907/acpi-hand ... press.html
Have only done this in theory, not yet tested.
[url]https://bkhome.org/news/[/url]
EasyOS 1.0.14 will not read ExFAT created by Windows 10
Like the subject line says, EasyOS will not see/read a USB stick which was formatted ExFAT by Windows 10. Fedora 29 can.
“A wise man can learn more from a foolish question than a fool can learn from a wise answer.†--Bruce Lee
BionicPup won’t run an HP 2740p’s WiFi either
Just discovered that BionicPup (64-bit) (Puppy 8.0) won’t run the HP Elitebook 2740p’s wifi either. modprobe’ing iwlwifi then iwldvm automatically brings in cfg80211 and mac80211 but, no WiFi shows in the network managers. Fedora 29 and Windows 10 can run WiFi on this computer.
“A wise man can learn more from a foolish question than a fool can learn from a wise answer.†--Bruce Lee
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: EasyOS 1.0.14 will not read ExFAT created by Windows 10
Thanks for reporting that. It is fixed for the next release:Keisha wrote:Like the subject line says, EasyOS will not see/read a USB stick which was formatted ExFAT by Windows 10. Fedora 29 can.
http://bkhome.org/news/201907/easyos-no ... exfat.html
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: darktable install possible?
I would like to create a couple of extra SFSs for Easy, thinking of "graphics apps" and "multimedia apps" SFSs. That is, have multiple apps in one SFS, with a particular theme.gychang wrote:Really like EasyOS Pyro64 1.0.14 install on my HD. Is there a way to install darktable for photo editing?
Any suggestions what apps should be in these, let me know.
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: Wireless not working in EasyOS 0.9.4
I have bumped the kernel to 5.1.15 (it was previously 4.14.105), so hopefully your wifi will be fixed with the next release of Easy.Keisha wrote:Downloading 1.0.14 now, will try it. This is on a vintage-2010 HP EliteBook 2740p. On Quirky and Fedora 29 the wireless modules are iwlwifi, iwldvm, mac80211, cfg80211. Modprobe'ing these four into EasyOS 0.9.4, no wifi shows in the network setup app. Will try 1.0.14 presently and report back.
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
zygo posted earlier about hiawatha web server not support xslt.
I have recompiled hiawatha, and latest version:
http://bkhome.org/news/201907/hiawatha- ... r-pet.html
I have recompiled hiawatha, and latest version:
http://bkhome.org/news/201907/hiawatha- ... r-pet.html
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
EasyOS Édition française 1.1RC
Yes, a French Edition of EasyOS. There have been French builds of earlier releases, but this one has fixed many bugs and limitations, and a more complete translation.
Blog announcement:
http://bkhome.org/news/201907/easyos-ed ... caise.html
French-speaking testers welcome!
German and English builds coming soon.
Yes, a French Edition of EasyOS. There have been French builds of earlier releases, but this one has fixed many bugs and limitations, and a more complete translation.
Blog announcement:
http://bkhome.org/news/201907/easyos-ed ... caise.html
French-speaking testers welcome!
German and English builds coming soon.
[url]https://bkhome.org/news/[/url]
Propose for the next releases, to update/upgrade the international version of Easyos first, that is the English version. :)BarryK wrote:EasyOS Édition française 1.1RC
Yes, a French Edition of EasyOS. There have been French builds of earlier releases, but this one has fixed many bugs and limitations, and a more complete translation.
Blog announcement:
http://bkhome.org/news/201907/easyos-ed ... caise.html
French-speaking testers welcome!
German and English builds coming soon.
Although, English is not my native language.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Ha ha, yes, it does seem the wrong way round. Apart from French readers picking up missing or missed translations, I thought that their might be weaknesses that will show up in the non-English edition, that might also show up if someone were to install one of the other langpacks.blgs wrote:Propose for the next releases, to update/upgrade the international version of Easyos first, that is the English version. :)BarryK wrote:EasyOS Édition française 1.1RC
Yes, a French Edition of EasyOS. There have been French builds of earlier releases, but this one has fixed many bugs and limitations, and a more complete translation.
Blog announcement:
http://bkhome.org/news/201907/easyos-ed ... caise.html
French-speaking testers welcome!
German and English builds coming soon.
Although, English is not my native language.
Anyway, German and English builds coming soon.
I noticed one bug. When started SeaMonkey in the Easy containerized-desktop, it took a very long time to start, then crashed when I tried to resize the window.
There was a network connection to the modem, but no Internet connection, and it seems SM was waiting for something and timing out. After I had established an Internet connection, started SM in the containerized-desktop and it started up immediately and did not crash.
[url]https://bkhome.org/news/[/url]
I did manage to install the french version of Easyos and converted into a more or less English version.
Some remarks :
- sfsget manager doesn't show devx file. On internet it's available
- based slackware64-14.xx repository? Or still in progress for next release?
- sfsget manager still provides xenialpup-7.5. Is it possible to replace it by a newer bionicpup64 or a slacko64 pup version?
- please remove easyos/oe/thud in sfsget manager. Pyro is used.
- possibility to create sfs files with easyos and install it with sfsmanager containerized or in main system
When booted in containerized xenialpup64 or Easyos no strange icons/desktop appears as in in previous versions. Problem is solved now.
That's it for now.
Some remarks :
- sfsget manager doesn't show devx file. On internet it's available
- based slackware64-14.xx repository? Or still in progress for next release?
- sfsget manager still provides xenialpup-7.5. Is it possible to replace it by a newer bionicpup64 or a slacko64 pup version?
- please remove easyos/oe/thud in sfsget manager. Pyro is used.
- possibility to create sfs files with easyos and install it with sfsmanager containerized or in main system
When booted in containerized xenialpup64 or Easyos no strange icons/desktop appears as in in previous versions. Problem is solved now.
That's it for now.
Hum at the second start (the first start was really success full) EasyOS, new French version, will and can't continue
(so I am now under wary64-6.99.iso again, with new problems, see separate thread)
because of
/bin/sh: accès à tty échoué; contrôle du service stoppé)
«exit» is proposed. If I do that, a block of texts is coming in English but I find it can continue to stay in English (excepted you will absolute perfection of the translation) else in a French version as the most important words are existing in French!
(all the paragraph of usage comes in English)
(from img on memory card on USB-adapter)
the unique USB port (*2 is USB3 (but has to be compatible with the used USB hardware for USB2)
(*2 they are only 2 USB port on that laptop and the other one, real USB2, is in use
(so I am now under wary64-6.99.iso again, with new problems, see separate thread)
because of
(proposal of translation to enter:/bin/sh: can't access tty; job control turned off
/bin/sh: accès à tty échoué; contrôle du service stoppé)
«exit» is proposed. If I do that, a block of texts is coming in English but I find it can continue to stay in English (excepted you will absolute perfection of the translation) else in a French version as the most important words are existing in French!
and after that, the info text ol mount:file system label = EASYOSZRAM
OS-type: Linux
Block size
Fragment size
inodes blocks
block reserved per super user
first data block
maximum file system blocks
block group
blocks per group fragments per group
inodes per group
superblock backups stored on blocks
usage: mount [OPTIONS ...
(all the paragraph of usage comes in English)
continue was not possible, easyOS did start but not continue any more.there are filesystem-specific no flags
(from img on memory card on USB-adapter)
the unique USB port (*2 is USB3 (but has to be compatible with the used USB hardware for USB2)
(*2 they are only 2 USB port on that laptop and the other one, real USB2, is in use
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Although the ISO file is a "hybrid" type, that can be written to either a USB-stick or optical media, booting fails with the former. I have reported on this here:
http://bkhome.org/news/201907/fail-boot ... stick.html
Anyway, to boot from a USB-stick you should write the easy-*.img.gz file to it, using Etcher, EasyDD or in a terminal.
@oui
I am unclear from your post in another thread. Did you write the ISO file to a USB drive? You should write it to the optical drive, which will be sr0 or sr1 -- in Puppy, use pBurn or burniso2cd to burn to the CD/DVD
http://bkhome.org/news/201907/fail-boot ... stick.html
Anyway, to boot from a USB-stick you should write the easy-*.img.gz file to it, using Etcher, EasyDD or in a terminal.
@oui
I am unclear from your post in another thread. Did you write the ISO file to a USB drive? You should write it to the optical drive, which will be sr0 or sr1 -- in Puppy, use pBurn or burniso2cd to burn to the CD/DVD
[url]https://bkhome.org/news/[/url]
You might be interested in this Barry http://murga-linux.com/puppy/viewtopic. ... 03#1032203
What I've done is to set fatdog initrd's init to /bin/sh if a baseshell kernel boot parameter is included, that /bin/sh occurs just before work otherwise starts on preparing/loading the main sfs (fd64.sfs). Fatdog includes the option to be net (hard wired or wireless) connected early i.e. by that point in the init process. So its nice having wireless net connected cli (for instance that can be used to ssh/scp the main sfs from elsewhere if you so desire).
The main point of this post however is that I've also recently dropped dosbox into initrd, so that's also available. And using dosbox to run a gui program (I've included a version of the game 'Mario') you can run graphical stuff seemingly OK.
Many many moons ago I used to use Turbo Pascal under DOS to write graphical programs. IIRC that was relatively easy to do. Perhaps a alternative option to your other ventures into having a early (initrd) graphical setup (or of course any other DOS based graphical programming tool). Initrd with the kernel modules sfs is now at 84MB, most of which is the firmware and modules.
That initrd.xz partners with the Fatdog 4.19.44 vmlinux
What I've done is to set fatdog initrd's init to /bin/sh if a baseshell kernel boot parameter is included, that /bin/sh occurs just before work otherwise starts on preparing/loading the main sfs (fd64.sfs). Fatdog includes the option to be net (hard wired or wireless) connected early i.e. by that point in the init process. So its nice having wireless net connected cli (for instance that can be used to ssh/scp the main sfs from elsewhere if you so desire).
The main point of this post however is that I've also recently dropped dosbox into initrd, so that's also available. And using dosbox to run a gui program (I've included a version of the game 'Mario') you can run graphical stuff seemingly OK.
Many many moons ago I used to use Turbo Pascal under DOS to write graphical programs. IIRC that was relatively easy to do. Perhaps a alternative option to your other ventures into having a early (initrd) graphical setup (or of course any other DOS based graphical programming tool). Initrd with the kernel modules sfs is now at 84MB, most of which is the firmware and modules.
That initrd.xz partners with the Fatdog 4.19.44 vmlinux
[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]
[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]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
@rufwoof,
Yes, there are many ways to obtain a gui in the initrd. My current method, settings up aufs with easy.sfs within the initrd, seems to be working ok, but haven't had much feedback about it yet, running on other PCs. The initrd of the latest French Edition is 1.4MB, and that is uncompressed.
Yes, there are many ways to obtain a gui in the initrd. My current method, settings up aufs with easy.sfs within the initrd, seems to be working ok, but haven't had much feedback about it yet, running on other PCs. The initrd of the latest French Edition is 1.4MB, and that is uncompressed.
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Here it is, version 1.0.92, 1.1RC:
http://bkhome.org/news/201907/easyos-ve ... -11rc.html
@foxpup, @blgs,
I have not yet tackled some of the issues that you posted about.
http://bkhome.org/news/201907/easyos-ve ... -11rc.html
@foxpup, @blgs,
I have not yet tackled some of the issues that you posted about.
[url]https://bkhome.org/news/[/url]
1.0.92 1.1RC
Loadsa problems with .img>USB. Much as I dislike USB booting and laptops, decided to test these first. {CQ71, which does have its own idiosyncrasies, known to me!}. Found several issue, some trivial, some not. Firstly, there are still blank screen pauses on booting, some long on first boot, shorter on subsequent, which, ideally, could be filled with some sort of screen activity even if just a line of **** rather than prior text to that effect.
There were serious difficulties getting setup initially as tapping is not activated by default (not a new problem!) and was unable to get the touchpad buttons to activate either. Addition of a USB mouse aggravated matters. Swapped back to a desktop machine to get setup which was mostly successful although there were very long rather than just some delays in getting Seamonkey started and more than one attempt to activate wifi was required, also accompanied by long delays in connecting {NOT a router/line issue in this household!}.
Swapping back to laptop, with or without an USB mouse didn't help - never could connect wifi nor get to tapping menu and touchpad buttons unstable but 'active' now.
Gave up - back to the .iso and a proper box! Later...
Later: Predictably, .iso ran fast, first time - no issues! Many thanks. Minor issues: CNTRL-ALT-BKSPCE not working (both machines, both media). SR0 has habit of disappearing (this is old problem now reappearing after solving several versions ago).
PS. Are all those warnings about running in RAM really necessary? It's the main advantage of using a CD or closed CD-RW: scammers and hackers can't write anything to it! LiveCD has to be a more secure way of running for the minor inconvenience of re-writing a few parameters at each new boot?
{and a thousands curses on uefi, laptops and .img}
Loadsa problems with .img>USB. Much as I dislike USB booting and laptops, decided to test these first. {CQ71, which does have its own idiosyncrasies, known to me!}. Found several issue, some trivial, some not. Firstly, there are still blank screen pauses on booting, some long on first boot, shorter on subsequent, which, ideally, could be filled with some sort of screen activity even if just a line of **** rather than prior text to that effect.
There were serious difficulties getting setup initially as tapping is not activated by default (not a new problem!) and was unable to get the touchpad buttons to activate either. Addition of a USB mouse aggravated matters. Swapped back to a desktop machine to get setup which was mostly successful although there were very long rather than just some delays in getting Seamonkey started and more than one attempt to activate wifi was required, also accompanied by long delays in connecting {NOT a router/line issue in this household!}.
Swapping back to laptop, with or without an USB mouse didn't help - never could connect wifi nor get to tapping menu and touchpad buttons unstable but 'active' now.
Gave up - back to the .iso and a proper box! Later...
Later: Predictably, .iso ran fast, first time - no issues! Many thanks. Minor issues: CNTRL-ALT-BKSPCE not working (both machines, both media). SR0 has habit of disappearing (this is old problem now reappearing after solving several versions ago).
PS. Are all those warnings about running in RAM really necessary? It's the main advantage of using a CD or closed CD-RW: scammers and hackers can't write anything to it! LiveCD has to be a more secure way of running for the minor inconvenience of re-writing a few parameters at each new boot?
{and a thousands curses on uefi, laptops and .img}