No comments I had two old blogs, set to read-only, at barryk.org/blog and barryk.org/blog2, however, had to remove them as my host hostgator.com complained of too much traffic.
I was meaning to convert them to static HTML pages, and finally have done it. Found a great tool for the job, Httrack. It has a browser interface, by running "webhttrack".
I re-enabled the online blogs and used webhttrack to download one of them. Oh, it downloaded heaps of files from other sites, mostly linked images.
After some online searching, found the trick to restrain download to only inside the blog.
There are "Scan Rules". Delete them, replace with:
-* +*arryk.org/blog/* -*/?delete=*
The "-*" removes everything, then "+*arryk.org/blog/*" will restrain downloads to have that text in the URL.
Httrack follows every link that it can find on the blog, which takes a very long time. I did not see the point of it following the Delete button, so added that fine filter item.
The old blogs are now here:
This blog, barryk.org/news, is also there, converted to static pages, as I am planning to move to a new blog script (and website) in the next day or two.
Another item of news: bkhome.org is now on a new host, omnis.com
1 Comment I wrote about redesigning the local help files in Easy:
Now I am thinking of dumping all of that.
Various reasons, one of which is that HelpSurfer is too unstable. Also too slow.
jamesbond's mdview is soooo fast, and help files in Fatdog are now based on markdown. Wrote about mdview here:
L18L wrote a custom converter to convert one of the Fatdog md files to html:
I wondered what is out there, to convert md to html. There are many converters that require an Internet connection, but I want one that works offline.
Written in C:
No comments I have been swapping between using Quirky and Easy, and one thing has become very obvious: Easy is much faster.
No quantitative measurements, just eyeballing, noticing a significant difference in app startup times and general responsiveness. Compiling times are also remarkably faster.
Fundamentally, the reason is that Quirky is a full installation, and in my case on a magnetic platter mechanical hard drive. Whereas, Easy is a layered filesystem, where, if there is enough RAM, 'q.sfs' (which is all of Easy) gets loaded into RAM at bootup.
So, you pay the price of a slightly slower bootup, but faster running.
One extra point: q.sfs is xz-compressed, however, after download and at first bootup, there is the option to recompress it gzip-compressed. This can make a small but noticeable difference to the responsiveness.
Another point: aufs is configured without support for writing directly to the lower layers. This makes aufs faster.
In all, it is a pleasant experience using Easy. So, the title is hinting something!
No comments I wrote about this mini-PC recently:
Decided to buy it. Another system is needed for testing. Unfortunately, the Alpha Litebook has fatal problems with using Flash drives, so not using it. I posted about it here:
Also, a system with Windows 10 will be useful for testing dual installations with Easy OS.
Like the passive cooling too!
1 Comment In Quirky, and all pups, there is a "Help" entry in the menu, clicking on which launches the web browser and brings up a local web page, /usr/share/doc/index.html
index.html is now removed, and clicking "Help" in the menu runs /usr/share/doc/easy/help.sh, which launches a language-translated file 'help.htm' in HelpSurfer.
This has to work without being online, so there are translations of major languages for help.htm, in /usr/share/doc/easy.
This replaces 'welcome1stboot' and launches a translated 'welcome.htm'. Again, has to work offline.
help.htm has a link to launch doc-launcher.
There has been a major cleanup of /usr/share/doc, old help files thrown out. Much of it is better suited to be online.
Pages: ...       ...