I've been checking out your github site for this rockedge. Rest assured I remain keen and determined to get your zoneminder version running on some other machine I have. In fact that was my priority but in a brief experiment with creating first Arch WeeDog I had quick success so ended up concentrating on polishing that up for desktop use. Whilst that Arch config work is fresh in my brain I'll likely concentrate on any bug-fixing required prior to stable version 2.0.8 release. As I mentioned to you in PM there does seem to be some problem with registering on main WeeDog forum, at least as far as email confirmation is concerned (a bit like here on murga forum, which is surprising since WeeDog forum certainly has nice uptodate phpBB version).rockedge wrote:To report I've just run a successful build of a WeeDog64-Voidhttps://github.com/techrockedge/weedog-ZMCode: Select all
./build_firstrib_rootfs_104.sh void rolling amd64 firstrib00-64-auto.plug ./build_weedog_initramfs05_s207.sh void
The plug file I used is not quite refined and could use some improvements but is still a good example of a plug file. The build was error free.
This WeeDogLinux Void version is running so well. Very good results of CPU loads at idle and CPU temps remain in the lower ranges and RAM usage at start up was 148 megs used.
Now that WeeDogLinux Arch64 rc2 is in nice running order, I will also spend some time on trying to produce a Void Linux version of same desktop config, since much of the work already done via that Arch development. But I have practical wish to have zoneminder system running, so not sure where my priorities will end up or if I'll try both tasks in parallel...
@TerryH: glad managed to sort out your wifi issues and thanks for your feedback more generally. Will try and get some better documentation prepared at some stage in terms of how weedog can be configured in different ways (e.g. the various optional boot scerios including copy2ram; having upper_changes persistence directory in RAM or in alternative directory or hard disk. How previous upper_changes folders can be made into a separate numbered sfs, which are then auto-loaded in layers and so on).
As I've said earlier, I'll leave main discussions to posts on weedoglinux.rockedge.org since best, I feel, to collect all feedback on main forum site, but many of the details of how weedog work (including interesting contributions/ideas from both rockedge and rufwood in particular are to be found in the earlier posts of this thread. A lot to read though, so will hopefully get that better documented eventually... Having said that, the latest WeeDogLinux Arch64 basically just works so technical details aren't particularly required by anyone just wanting to try it out, and no real reason for anyone to bother about underlying functionality unless they have an interest in that kind of stuff - will try to make it as user-friendly as possible anyway.
wiak