BionicDog (updated: 2018-06-04)
Hi stemsee, It's in the DEVX (to be precise, the .config is in usr/src/linux-headers-4.15.0-22-generic/)
32-bit:
https://github.com/fredx181/bionicdog/r ... 6.squashfs
64-bit:
https://github.com/fredx181/bionicdog/r ... 4.squashfs
EDIT: kernel config is also in /boot, so no need for DEVX then, I guess.
Fred
32-bit:
https://github.com/fredx181/bionicdog/r ... 6.squashfs
64-bit:
https://github.com/fredx181/bionicdog/r ... 4.squashfs
EDIT: kernel config is also in /boot, so no need for DEVX then, I guess.
Fred
BionicDog live64 K 4.15.0.22-generic
Testing:
Hi Fred,
Thanks for the above which I have been testing over the past month.
It is great to have a rolling release, running entirely in RAM with the option to save or not at the end of the session.
That is a wicked combination not found in traditional Pups. It opens up the easy possibility of installing an image file to
a stick and that is job finished.
Initial install from the ISO files was to a ext4 partition (sdb3) on a Samsung SSD-850.
Boot was via an additional vesamenu entry on my normal 4GB SD boot card:
That continues to update using Synaptic.
Over the last week I have also installed to an 8GB Nano USB2 stick with two partitions - fat32 & ext4
The syslinux.cfg for that contained a single active line.
That also worked fine on an old 2012 Samsung Atom net-book with 2 GB of DDR2 RAM and I had been hoping to install it next
to a USB3 stick with a 2 partition (fat32/f2fs) layout but found that the current initramfs lacks support for system boot from f2fs.
It appears that "f2fs" needs to be added to the end of /etc/initramfs-tools/modules before updating the initramfs.
I held off so doing for fear of unintended consequences. In addition to the earlier load of the f2fs kernel module,
f2fs-tools loaded via Synaptic, would also be needed.
Perhaps it is something to consider for the next version.
Full sized screen-shot here: (Press F11 to toggle into full screen then click on link)
https://drive.google.com/uc?export=view ... DAyw6uTWTP
Thanks once again.
Hi Fred,
Thanks for the above which I have been testing over the past month.
It is great to have a rolling release, running entirely in RAM with the option to save or not at the end of the session.
That is a wicked combination not found in traditional Pups. It opens up the easy possibility of installing an image file to
a stick and that is job finished.
Initial install from the ISO files was to a ext4 partition (sdb3) on a Samsung SSD-850.
Boot was via an additional vesamenu entry on my normal 4GB SD boot card:
Code: Select all
MENU SEPARATOR
LABEL bionicdog
MENU LABEL BionicDog64 sdb3 24/06/18
KERNEL /bionicdog/vmlinuz
# APPEND initrd=/bionicdog/initrd1.xz noauto from=/dev/sdb3/bionicdog/ copy2ram changes=EXIT:/dev/sdb3/bionicdog/casper/
APPEND initrd=/bionicdog/initrd1.xz noauto from=UUID:1a56b14c-c465-4487-b899-f92f572dea8e/bionicdog/ copy2ram changes=EXIT:UUID:1a56b14c-c465-4487-b899-f92f572dea8e/bionicdog/casper/
Over the last week I have also installed to an 8GB Nano USB2 stick with two partitions - fat32 & ext4
The syslinux.cfg for that contained a single active line.
Code: Select all
default /bionicdog/vmlinuz initrd=/bionicdog/initrd1.xz noauto from=UUID:abcfb1d3-af3a-47a7-b353-379ceccb5ad9/bionicdog/ copy2ram changes=EXIT:UUID:abcfb1d3-af3a-47a7-b353-379ceccb5ad9/bionicdog/casper/
to a USB3 stick with a 2 partition (fat32/f2fs) layout but found that the current initramfs lacks support for system boot from f2fs.
It appears that "f2fs" needs to be added to the end of /etc/initramfs-tools/modules before updating the initramfs.
I held off so doing for fear of unintended consequences. In addition to the earlier load of the f2fs kernel module,
f2fs-tools loaded via Synaptic, would also be needed.
Perhaps it is something to consider for the next version.
Full sized screen-shot here: (Press F11 to toggle into full screen then click on link)
https://drive.google.com/uc?export=view ... DAyw6uTWTP
Thanks once again.
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
Thanks for testing !!ETP wrote:Testing:
About f2fs support, I could make it work for 32-bit but not for 64-bit, don't know why, very frustrating !!
Nice (looking at your screenshot), what you've done with it.
@ITSMERSH, I think I can make a "package" for a realtime kernel from a Debian Sid version (seems like Ubunu doesn't provide it, only option "low latency" kernel). Is it for 32-bit what you need ?
Fred
Hi ITSMERSH, here's real time kernel 4.16.0-0.bpo.2-rt-686-pae for BionicDog 32-bit
https://dl.dropboxusercontent.com/s/2p8 ... ar.gz?dl=1 It's from Debian Backports.
Extract in "casper" folder, should overwrite initrd1.xz and vmlinuz.
(better backup these files first)
Reboot
Hopefully it works as you would expect.
One small problem I had sometimes that starting X took very long.
I found that holding a key (e.g. Alt) for a few seconds triggered it and X started for me.
(no idea why, btw)
Fred
https://dl.dropboxusercontent.com/s/2p8 ... ar.gz?dl=1 It's from Debian Backports.
Extract in "casper" folder, should overwrite initrd1.xz and vmlinuz.
(better backup these files first)
Reboot
Hopefully it works as you would expect.
One small problem I had sometimes that starting X took very long.
I found that holding a key (e.g. Alt) for a few seconds triggered it and X started for me.
(no idea why, btw)
Fred
Hi Fred,
I finally finished my frontend for git (program name wiagit). I needed it cos my memory is too short these days to remember all the git commands on my own.
Developed and tested on XenialDog64 but should work fine on any recent system that has gtkwialog (required).
Find wiagit deb package at below link (I put depends on gtkdialog in Debian control since I noted your gtkdialog deb from XenialDog64 repo contains gtkwialog - hope that works for you):
http://www.murga-linux.com/puppy/viewto ... ?p=1000715
wiak
I finally finished my frontend for git (program name wiagit). I needed it cos my memory is too short these days to remember all the git commands on my own.
Developed and tested on XenialDog64 but should work fine on any recent system that has gtkwialog (required).
Find wiagit deb package at below link (I put depends on gtkdialog in Debian control since I noted your gtkdialog deb from XenialDog64 repo contains gtkwialog - hope that works for you):
http://www.murga-linux.com/puppy/viewto ... ?p=1000715
wiak
Thanks wiak !!
Looks very advanced your wiagit program, I guess you learned much more about git usage.
I added it to Xenial and Bionic 'Dog' repos, also added new "gtkdialog_0.8.5-wiak-B-1" package to Bionicdog repos now.
(this assumes to have latest "gtkdialog" (0.8.5-wiak-B) installed, but that will be automatically done if a package depending on gtkdialog will be installed or upgraded)
Fred
Looks very advanced your wiagit program, I guess you learned much more about git usage.
I added it to Xenial and Bionic 'Dog' repos, also added new "gtkdialog_0.8.5-wiak-B-1" package to Bionicdog repos now.
Yes, should work fine that way, I wanted to avoid having both gtkdialog and gtkwialog in repos, so in control file "Depends: gtkdialog" is the best IMHO.(I put depends on gtkdialog in Debian control since I noted your gtkdialog deb from XenialDog64 repo contains gtkwialog - hope that works for you):
(this assumes to have latest "gtkdialog" (0.8.5-wiak-B) installed, but that will be automatically done if a package depending on gtkdialog will be installed or upgraded)
Fred
Yes, I understand it all better now... When I earlier uploaded the source code for gtkwialog repo I had no idea what I was doing so just made a brand new repo with my new sources because I didn't know how to merge in my changes to legacy gtkdialog code. Drawback, which I recognised, is that the previous gtkdialog tracking history gets lost doing things so crudely. I'll fix/redo that later. i.e. re-fork legacy gtkdialog again and then correctly merge in my additions on the DebianDog gtkwialog repo. I'm taking a rest for now though.fredx181 wrote:Thanks wiak !!
Looks very advanced your wiagit program, I guess you learned much more about git usage.
wiak
Sorry, Fred, I updated wialog slightly (just cosmetic alteration that was annoying me). Kept same version number because too lazy to change it:fredx181 wrote:Thanks wiak !!
Looks very advanced your wiagit program, I guess you learned much more about git usage.
I added it to Xenial and Bionic 'Dog' repos, also added new "gtkdialog_0.8.5-wiak-B-1" package to Bionicdog repos now.
http://www.murga-linux.com/puppy/viewto ... 10#1000810
I am unlikely to alter it so quickly again...
wiak
Hi Fred.
I made some testings on the 64bit kernel.
Boots fine so far, though there seems to be a short delay when loading swap / executing pup_volume_monitor. No need to hit a key somewhere at boot up so far. All programs tested seems to work as expected.
Meanwhile I collected lots of audio programs and made .squashfs modules from that programs. I'm almost finished to be prepared to start recording a video about the use of BionicDog for Audio/MIDI Recordings.
Though I would like to include another part that would need to have the ffado drivers available. Is there something to download, or would you like to create such ffado package, if there's nothing existing to download by now?
Thanks.
I made some testings on the 64bit kernel.
Boots fine so far, though there seems to be a short delay when loading swap / executing pup_volume_monitor. No need to hit a key somewhere at boot up so far. All programs tested seems to work as expected.
Meanwhile I collected lots of audio programs and made .squashfs modules from that programs. I'm almost finished to be prepared to start recording a video about the use of BionicDog for Audio/MIDI Recordings.
Though I would like to include another part that would need to have the ffado drivers available. Is there something to download, or would you like to create such ffado package, if there's nothing existing to download by now?
Thanks.
Typo? I thought you used 32-bit.ITSMERSH wrote: I made some testings on the 64bit kernel..
You see perhaps here what you need?Though I would like to include another part that would need to have the ffado drivers available. Is there something to download, or would you like to create such ffado package, if there's nothing existing to download by now?
https://packages.ubuntu.com/search?keywords=ffado
If so, these can be installed with Synaptic or apt-get.
Fred
Sorry, Fred, updated wiagit to version 0.0.2 already. In using previous version I had a problem with terminal positioning and size (not enough screen space) and once I got used to git I didn't want to have to jump between so many tabs. Hence new version includes a mini-gui version (button on main wiagit first screen or can start mini-gui with command wiagitm).
NOTE WELL that it is important to manually delete previous $HOME/.wiagit before installation of the new version since apt purge doesn't do that I notice.
Much more user-friendly for more experienced git users now in my opinion.
More details on extra terminal handling given on main thread post.
I'm afraid, being early days, quick updates likely after all...
http://www.murga-linux.com/puppy/viewto ... 44#1000944
wiak
NOTE WELL that it is important to manually delete previous $HOME/.wiagit before installation of the new version since apt purge doesn't do that I notice.
Much more user-friendly for more experienced git users now in my opinion.
More details on extra terminal handling given on main thread post.
I'm afraid, being early days, quick updates likely after all...
http://www.murga-linux.com/puppy/viewto ... 44#1000944
wiak
Re-uploaded wiagit version 0.0.2 since I had made a minor mistake... oops
Hope you are not the person who downloaded previous 0.0.2 Fred - best to wait a day maybe before committing to repos (just in case...)...
wiak
Hope you are not the person who downloaded previous 0.0.2 Fred - best to wait a day maybe before committing to repos (just in case...)...
wiak
Last edited by wiak on Sun 05 Aug 2018, 01:55, edited 2 times in total.
deb package for wiagit 0.0.3 uploaded (includes wiagit-mini: wiagitm).
Changelog here:
http://www.murga-linux.com/puppy/viewto ... 41#1001241
I would be grateful if you could check if the Git_icon appears in the Dog Start->Development menu and on the wiagit application gui.
EDIT: Note that tcl/tk is installed as dependencies for gitk visualiser. The main wiagit/wiagitm programs don't themselves need that, so if you don't want tcl/tk included just remove gitk as a dependency (only the otherwise optional gitk visualiser button wouldn't do anything then of course).
wiak
Changelog here:
http://www.murga-linux.com/puppy/viewto ... 41#1001241
I would be grateful if you could check if the Git_icon appears in the Dog Start->Development menu and on the wiagit application gui.
EDIT: Note that tcl/tk is installed as dependencies for gitk visualiser. The main wiagit/wiagitm programs don't themselves need that, so if you don't want tcl/tk included just remove gitk as a dependency (only the otherwise optional gitk visualiser button wouldn't do anything then of course).
wiak
New gtkwialog version 0.8.6 debs and details of changes here:
http://www.murga-linux.com/puppy/viewto ... 37#1001837
Didn't effect any apps I've tested previously, but as above link details document, FatDog's findnrun app had a problem with junk appearing in its initial input entry box (I discovered that it was caused by findnrun using uninitialised startup variable resulting in echo of empty string - legacy gtkdialog ignored empty strings for input, gtkwialog didn't but I added if statement so that it does now).
wiak
http://www.murga-linux.com/puppy/viewto ... 37#1001837
Didn't effect any apps I've tested previously, but as above link details document, FatDog's findnrun app had a problem with junk appearing in its initial input entry box (I discovered that it was caused by findnrun using uninitialised startup variable resulting in echo of empty string - legacy gtkdialog ignored empty strings for input, gtkwialog didn't but I added if statement so that it does now).
wiak