Open Source

#KapusoRewind: Kung mamalasin ka nga naman oh!
Watch FULL EPISODES of #LunaMystika and other GMA programs here: http://bit.ly/GMAFullEpisodes

I made this bow and arrow using only primitive tools and materials.The bow is 1.25 m (55 inches) long and shoots 60 cm (2 feet) long arrows. I don’t know the draw weight – safe to say greater than 15 kg (35 pounds) perhaps? The stave was made from a tree ,Northern Olive (Chionanthus ramiflora), that was cut with a stone axe and split in half with a stone chisel. One half was used for the bow and was cut to a length of 1.25 m (50 inches). The limbs of the bow were carved with various stone blades so that the limbs tapered in width, and to a lesser extent depth, towards the tips. The middle of the bow was narrowed in width to form a handle about 12.5 cm (5 inches) long.
The string was made from the inner bark of a fibrous tree. It was separated into thin strips and left to dry. Then it was twisted into cordage.
Arrows were made of the same wood as the bow and were 60 cm (2 feet) long. A notch was carved into the back to accept the bow string. They were fletched with bush turkey feathers picked up from the ground (no turkeys were harmed in the making of this video). A feather was split in half and cut into 3 lengths then resin and bark fiber attached the fletching on to the arrows. The tip of the arrow was fire hardened and sharpened to a point. The fletching was trimmed using a hot coal. Each arrow took about an hour to make. A quiver was made of bark to hold the arrows. Importantly, the quiver was worn on the back in the historically accurate style of native American and African archers- not on the hip like medieval European archers (see back quiver: https://en.wikipedia.org/wiki/Quiver ).
I cleared a shooting range with a semi rotten log as a target instead of a hay bale. At 10 meters the accuracy was better than 50 % for this narrow target and the arrows stuck into the wood enough so that they were difficult to pull out. The bow was durable, shooting about 200-300 times with the string breaking only 3 times. I made a back up string and repaired them by splicing the ends back together.
In conclusion this was an easy bow to make. The short design makes it easy to find a straight piece of wood for the stave. A short string is also easy to make and short arrow shafts are easy to find. Short bows shoot fast and are easy to carry in thick forest. The dimensions of the bow were based on those given in the SAS Survival Handbook by john Lofty Wiseman. but instead of carving it from a stave from the start, I split the stave and then carved it. I think this requires less time, effort and skill. It also gives a flat bow design that’s unlikely to break. It does require wood that doesn’t twist much when split though.
Wordpress: https://primitivetechnology.wordpress…
Patreon page: https://www.patreon.com/user?u=294588…
I have no face book page. Beware of fake pages.

Hi everyone,

Dear community

GNU Health 4.2.2 patchset has been released !

Priority: High

Table of Contents

• About GNU Health Patchsets
• Updating your system with the GNU Health control Center
• Installation notes
• List of other issues related to this patchset

About GNU Health Patchsets

We provide “patchsets” to stable releases. Patchsets allow applying bug fixes and updates on production systems. Always try to keep your production system up-to-date with the latest patches.

Patches and Patchsets maximize uptime for production systems, and keep your system updated, without the need to do a whole installation.

NOTE: Patchsets are applied on previously installed systems only. For new, fresh installations, download and install the whole tarball (ie, gnuhealth-4.2.2.tar.gz)

Updating your system with the GNU Health control Center

Starting GNU Health 3.x series, you can do automatic updates on the GNU Health HMIS kernel and modules using the GNU Health control center program.

Please refer to the administration manual section ( https://en.wikibooks.org/wiki/GNU_Health/Control_Center )

The GNU Health control center works on standard installations (those done following the installation manual on wikibooks). Don’t use it if you use an alternative method or if your distribution does not follow the GNU Health packaging guidelines.

Installation Notes

You must apply previous patchsets before installing this patchset. If your patchset level is 4.2.1, then just follow the general instructions. You can find the patchsets at GNU Health main download site at GNU.org (https://ftp.gnu.org/gnu/health/)

In most cases, GNU Health Control center (gnuhealth-control) takes care of applying the patches for you. 

Pre-requisites for upgrade to 4.2.2: None

Now follow the general instructions at

 https://en.wikibooks.org/wiki/GNU_Health/Control_Center

 

After applying the patches, make a full update of your GNU Health database as explained in the documentation.

When running “gnuhealth-control” for the first time, you will see the following message: “Please restart now the update with the new control center” Please do so. Restart the process and the update will continue.

 

• Restart the GNU Health server

List of bugs and tasks related to this patchset

• bug #64269: get_serial function of LabTest class in health_crypto_lab.py need conside add units.name
• bug #64386: Automatically update the appointment sequence when state is confirm
• bug #64432: Gestational weeks show floating point instead of weeks
• bug #64457: Patient automatic critical information entries should be unique
• bug #64530: traceback on evaluation page of life if no institution is given
• bug #64665: Product cost_price needs to be passed as an argument in stock moves

For detailed information about each issue, you can visit :

 https://savannah.gnu.org/bugs/?group=health

 

About each task, you can visit:

 https://savannah.gnu.org/task/?group=health

For detailed information you can read about Patches and Patchsets

• https://en.wikibooks.org/wiki/GNU_Health/Patches_and_Patchsets

If you reach this page, you may be interested into this new category of Linux distributions labeled “immutable”. In this category, one can find by age (oldest → youngest) NixOS, Guix, Endless OS, Fedora Silverblue, OpenSUSE MicroOS, Vanilla OS and many new to come. I will give examples of immutability implementation, then detail my thoughts about immutability, and why I think this naming can be misleading. I spent a few months running all of those distributions on my main computers (NAS, Gaming, laptop, workstation) to be able to write this text. I haven’t given any of these a try just yet, but I feel like this is where the Linux desktop is going. I’m not sure if that’s a good or a bad thing – I need both more experience as well as read more informed opinions about it – but I do like the concept.