AbeAnd Log

Abe's OSE Google Drive Folder Abe's OSE Google Calendar

Sat Mar 11, 2017

Testing Cubic did not have desired results. I thought it copied files to a folder in root, but they are nowhere to be found in the ISO, squashfs, or upon trial booting. I will try again and I think a combination of the command line methods with cubic might be ideal. The location and user accessability of the files is also important. According to one guide the trial boot user interface is generated at boot time and not editable, but it must be generated from some layout instructions so it is a question of how difficult it is to modify and maintain. All this leads me to reconsidering the method of transfering a installation image to USB without any proprietary drivers would be better for user performance, implementation, and maintenance.

Google has apparently released a new version of hangouts through G Suite enterprise, which costs money.

https://gsuite.google.com/learning-center/products/hangouts/get-started-meet/

Open Source solutions can't be to far behind.

Fri mar 10, 2017

I was about to dive into a long manual command line ISO customization attempt again when I found cubic. I spent to much time trying to organize possible concepts on Talk:OSE_Linux. I need to edit and submit faster and organize early. I am uncertain about creation and implementation options within an ISO/image affecting long-term support capability. There may be difficulty initially aggregating files from the wiki to include in an ISO. The wiki is great with versioning etc., but it would be nice to have a universal synced library folder structure with the latest files as they're edited by dev teams and to have complete archive packages for each version of a machine. Google drive only partly achieves sync with data being spread across users accounts relying on proper public sharing to sync and it isn't technically open source. It could be great if an alternative can be found for the OSE Linux platform, but I don't see the needed features in the common P2P sync apps yet.

Thurs Mar 9, 2017

I've been reading some general info on the functionality of Live boot systems and persistence with casper-rw. From what I can grok the existing ubuntu Live install media and tools like Unetbootin and Rufus are the simplest way for most users to make USB Live boot devices with persistence. While most of the file system is read only some extra space (up to 4GB for FAT32 file size limit more for ext4) can be setup to hold user files and save system state info upon shut down. There are different options for the filesystems like UnionFS, OverlayFS, and aufs (used by Knoppix for greater stability). Another option is distributing a raw image taken from a USB device pre-made using such tools and then having users use other tools to clone the image to a USB device. It would technically eliminate steps, but the tools to copy the image would need to be user friendly and functional on all platforms.

Tues Mar 7, 2017

Continued trying command-line method to edit Linux ISO by making a shell script. I keep making mistakes trying to automate the process, but I am assuming the whole process works. I'd like to find a more automated method to edit, but currently it looks like most apps for this are outdated. I am also curious about different ways of making persistence work for the Live USB mode. While it is possible to do different types of installs even from one USB to another USB that might be confusing to many users. Unetbootin describes different installers/methods of booting. I think the ext4 formatted USB device I'm seems to run better in general and had more options from the bootloader menu, but it could the hardware is better as well. Also, the superiority of ext4 verse FAT32 probably has multiple benefits if users intend to run Live USB only. Again, however, that requires an existing Linux installation or a separate GParted Live USB just to format another Linux Live USB device.

During the ISO edit process, I also realized my concerns about too many packages and size may not be a problem yet because the file system is quite compressed in the ISO. I haven't successfully recompressed a new version with more packages yet so I can't guess at the new size yet. This is probably also a hindrance on performance, except the whole system goes into RAM. Which, in turn could be a performance issue. An installer closer to a USB to USB install would likely have much better performance. I think there are different methods for executing Live USB systems and it will be worth looking at alternatives. There are some specialty Live USB Linux versions like Puppy and mint, but they are mostly stripped down light weights.

Still uncertain where and how extra files CAD library etc. should be placed in the ISO structure other than the maybe the user Documents folder. Maybe that would copy over or maybe it would require some extra modification of the installer. Since I am not a very experienced Linux user more research is necessary, but with Linux that is almost always the case.

Sun Mar 5, 2017

Successful installation of OSE Linux from bootable USB devices made using Unetbootin in VB VM running OSE Linux. Some glitches and oddities, but it worked out.

I did some different tests just to verify likely problem spots for users and get a general idea of how well different devices work. I'm still doing more tests and I'd like to get the ISO and USB process a little more polished.

I read more Ubuntu USB stick install recommendations and there is better documentation for 16.04 than I saw previously. Most of the bugs occur with differing software versions, older boot device creator software and the system BIOS/EFI/UEFI. There are also occasional USB device incompatibilities. Just getting a UEFI system to boot from USB device is not always perfect either. Pressing and tapping frantically at the boot menu key doesn't work and a restart and retry is required. This can be more of an issue on faster modern systems with fast or ultra fast boot settings. Many users may need to adjust BIOS/UEFI settings just to be able to boot an alternative device.

I tested a 16GB USB 2.0 Patriot XT device by using gparted to format ext4 and used Unetbootin to transfer the OSE Linux ISO to it. First, I left the boot flag unset I wanted to verify the EUFI would give a no boot system found error. It did, so I then set the boot flag on in Gparted. It booted fine I ran the try ubuntu option and then the ubuntu installer from there. It went smooth and reasonably quick. I also formatted an 8GB USB 3.0 (unknown brand) to fat32 and set the boot flag in gparted then again used Unetbootin. It was slower and had a few glitches after booting into try ubuntu and during the installation setup it hungup a couple times. So I rebooted it and ran the ubuntu boot menu check disc option to verify the USB installer. It passed verification and the next boot I used the Install option from the boot menu and I was able to partition and complete the install. One oddity that might be due to Unetbootin (frugal installer?) is that after booting into the full installation it still had the installer option on the launcher. So I think it did not do a proper install as much as it copied the executing system to the new disk.

For 16.04 Ubuntu recommended tools are for windows users to use Rufus and for Linux users the latest version of usb-creator-gtk. I am curious if all of these boot device creators set the boot flag or install an MBR boot sector as I recall that being an issue for me in the past, but I've learned it is easiest to use gparted to double check. I plan to test a few more boot software options and if needed edit a new ISO using command-line instructions so I can test and complete a full install with all the up to date software packages and OSE libraries so that it is ready for me to use post install (or off the stick).

Also when I booted into the ubuntu installation on my SSD the first time I saw the installer option still available I assumed I had set the UEFI boot options wrong and it booted off one of my sticks again. I rebooted checked the UEFI tried again got a GRUB minimal BASH twice restarting and checking UEFI. I turned off some boot options, but the GRUB 2 loader is what I installed to the SSD and that is what was glitching. I recall having boot loader issues like that with previous Linux installs. Not sure if the EUFI read something wrong the first time or GRUB 2 adjusted itself somehow, but patience and reboots are often required. One expects the software/hardware to execute correctly every time, but some things about BIOS/UEFI and boot loaders are clearly imperfect. The way the EUFI and GRUB handled the install overall is good, though. The EUFI automatically detected and defaulted to boot the ubuntu SSD first and the GRUB menu detects and allows selection of the other windows boot hard drive. No need to modify the original system disk and I can move the internal SSD when feasible with no software changes too the original system.

Sat Mar 4, 2017

Working on getting OSE Linux installed on new SSD I added yesterday, but in a roundabout way. I'm running the current OSE Linux ISO in a VM, testing putting it on USB sticks to test in other VM's and system UEFI boot testing, while testing Unetbootin and working through the ISO editing terminal instructions I found for 16.04.

Thurs Mar 2, 2017

Dealing with a few annoying local technical difficulties the last few days. Mainly trying to download OSE Linux ISO. Started a direct download from google drive then it failed to resume after a low bandwidth interruption. Then I decided to use the drive sync. Went back to work in my existing Virtual Box VM and it was inaccessible/corrupt for no apparent reason. My past experience with VirtualBox and Linux has been much better I am surprised how beta this supposedly non-beta software is behaving. Then Power outage. Everything was back on the next day then grid repairs sent surge spikes and brownouts and WISP was down most of the day. It will great to get off grid some day, but in this case, it wouldn't have helped much. Finally, realized I needed to uncap google drive sync a bit. Now it tells me failure to sync. I restarted it, but Bit Torrent has got to be the faster more stable solution. So I think I can remote to a faster stable connection download it then seed a torrent I can download. Be nice to get it on http://linuxtracker.org/ and get more seeds too.

Thankfully, I had some offline FreeCAD tutorials to work on during all this so, progress. The nature of the work benches is an interesting way to break workflow down, but some of the inconsistencies and copy limitations are making it hard for me to see the optimal order of operations for mirroring symmetry and reducing repetition. Many tutorials how a lot of repetition, which is good for learning, but not optimal for productivity. However, the OSE distribution methods, small simple parts in libraries and assembly make these issues less critical. Also, the software is still beta. So next I think I'll do something with a focus on the assembly work benches.

While the FreeCAD Developer Test doesn't look too hard, I think the broader point is to delve deeper into all the OSE Linux software so anyone can complete a series of. I was thinking about the software development side of things more lately, but the open source software community is already huge and often willing to mobilize on good projects quickly so perhaps an if we build it they will come approach might work out. It is currently the open source hardware side of things that needs more development and growth. While it has to be a team effort there are many good existing software dev teams capable of joining if they see a capacity for steady hardware production for them to write software for.

Sat Feb 25, 2017

I've had a few glitches creating a stable Linux VM install. A VM isn't ideal, but I don't have my personal machine or an extra disk to install to, yet, otherwise I personally have no use for windows. Many people may need or prefer to use a VM since it can make it easier to use Linux on any machine, though. And with advances in hardware running a Live OSE Linux USB stick or SSD should be feasible soon. I think I've gotten past the install problems( and just realized what caused some), which were mostly caused by my attempts to install the VM on a big 128GB fast USB3 stick.

I also noticed some ubuntu system apps seemed less functional than in previous versions. I am still having some graphics issues, which I attribute to the VM and maybe my settings. But, I do not recall having such issues before with VM's so I will try some different versions and settings of the software to find stability. I did choose the latest ubuntu-16.10-desktop-amd64.iso.torrent out of curiosity. I think I'll test the LTS next since that is probably easier to support for an official OSE Linux.

A good place to start for standardizing an OSE Linux distro might be package scripts. Synaptic eases the creation of install scripts for use on other machines. So keeping an updated package list and install script for OSE Linux may be useful for Support and creating custom ISO/USB installations.

I found some guides to try following to create custom Linux ISO/USB installs. Talk:OSE Linux

Thurs Feb 23, 2017

Still working on my Linux install. I hit a few snags with current hardware setup. Hopefully, I can make a trip to get my desktop soon, which will solve most of my issues. In the meantime, a Virtual Box install will have to do. I Looked over the OSE roadmap and milestone charts again in more detail to get a better idea of how I might align some of my plans to coincide with projects that overlap with my current skills and local projects I'd like to work on. My two main focuses are the critical FreeCAD app and the box of Arduino and related hardware ( and relevant software development ) I have sitting on my desk, which I have yet to put to really great use.

Wed Feb 22, 2017

Doing a fresh install of Ubuntu and OSE Linux apps into a VM since I don't have my personal desktop. Getting everything configured and tested should make for some interesting experience.

I ran across an old article on powerpoint abuse when there was a big revolt against them years ago. It reminded of some of the wonderful works of modern art in OSE google presentations. http://www.techrepublic.com/article/10-things-you-should-know-about-powerpoint-abuse/ and more http://fortune.com/2012/06/12/powerpoint-abuse-how-to-kick-the-habit/ While very dense and technically concise and likely to more visual learners like myself I am not always sure they convey information in the most efficient manner. I'd like to make more use of their versatility, but I don't want to fall into any traps.

I was working back over some code and ideas for my long term arduino projects and while working on a FRAM storage library I figured out a number of bugs and made good strides in understanding better classes and arduino style libraries. However, I also found other FRAM libs I had not before and some other information about possible hardware issues. While I am interested in the FRAM storage for potential future projects where small fast resilient memory is needed I have given in to the idea of using micro SD card for my larger weather and climate control needs. With respect to classes and Arduino libraries, I think I have a clearer idea of how code should be broken into small simple parts so it can be reused or adapted to many projects. I also see significant benefits to agile scrum for coding practices. I do think balancing the priority of product delivery over documentation is difficult for open source development especially for an organization like OSE trying to on board more new devs and contributors who need transparency to see the what, how, and why of everything in order to learn the collaborative work style. Or even for end users and new contributors trying to get up to speed using old documentation that may be lacking. I am considering the bigger picture of many small easy to use Arduino libs for many projects. Following the ideas of delivering basic functionality first making the most critical libs for immediate projects and the most broadly useable seem like the top two priorities. I have been slow in attaining my custom green house controller because of not breaking it down enough. Finding overlap with existing libraries and projects is critical for not repeating unnecessary work. Completing small chunks of code features one at a time should lead to a complete functional package faster. Focusing on nonessentials and rare extra code possibilities has left the hardware collecting dust on my desk. I have also been distracted by uncertainties in how to package the equipment into a safe enclosure so I need to drop these concerns and not go back to square one, but re-evaluate piece by piece. Learning to apply scrum should lead to better methodical decisions.

Tues Feb 21, 2017

Reviewing Logs, cleanup, re-evaluating. While I have been busier with local farm issues I have been skimming the recent wiki changes usually daily & occasionally watch Marcin's youtube. I did get through FreeCAD basics, but not as advanced & as much experience with it as I wanted this winter. For local projects when help (WWOOFers) it is more productive to concentrate on local projects since otherwise little seems to get done. I have some designs to work on slowly this year (work shop), which I'd like to use FreeCAD or Sweet Home 3D for designing. A decent sized local workshop with office space will help me dedicate more space and time to work on projects.

And of course, I want to contribute to the new CEB Press version and related long term big picture plan for earth construction systems. In working with spreadsheets too do estimates, while I decided the more advanced spreadsheets functions & scripts generally add too much complexity for less experienced users like myself and may get in the way of productivity. I think there is a lot of interesting analysis to do on the cost benefits of earth construction systems. I have even been thinking of comparing stabilized CEB production to local natural CEB's aka rocks. We have a lot of rocks here that could be gathered and glued together with lime/cement. I have some experience with masonry labor and rock work. CEB's are obviously less human time and energy intensive since it is difficult to design machines/robots to gather rocks. However, getting the right mix of clay, sand, silt, & lime seems more machine and energy intensive than I first thought. As an example, the area here has more silt with some sand in most areas and then we have found some spots where we mine clay for making cob and CEB's. It can be difficult to evaluate and estimate quantities ratios of natural earth aggregates and then continuously monitor the mix quality with samples.

I see OSE has a possible brick making facility planned and I am curious how this might develop. Generally, a major advantage of earth building is local materials and minimizing transport of materials. Having all the machines tractor pulverizer, mixer, and press easily mobile and streamlining their use process for any work site seems more in line with long-term goals. I do like the idea of a central spot for brick production since many sites may need to haul in some external aggregate anyway and it could make it easier to use solar PV and electric motors in the future since PV is usually fixed and a PV trailer would not likely be sufficient power to run multiple machines simultaneously.

While I decided making google docs and spreadsheets more complex is not generally worth the cost for benefits I think more discussion and clearer guidelines for standard use practices will benefit collaboration. The many different software tools and web portals used by OSE currently or previously can be confusing and jarring in some cases if integration in the wiki is poor or they are separate websites altogether. I like the looks of the OSE Linux distro. I have installed and looked at most of the apps, but need much more practice with all and Linux in general. While an ISO is a necessary static starting point I think many people will use it in a VM since for many users it is a less compatible addition to other software and platforms they may be currently required to use. I am not an IT or VM expert, but I am aware there may be a number of useful Virtual Machine software platform functions that may be useful for collaborative work environments and this will only expand in the future. Syncing VM's in a distributed P2P cloud fashion could be very useful for sharing OSE working data. The other side could be central servers with users logged into VM's remotely so all work is in the cloud from the start. Or ideally some combo of the two models.

I have also recently been reviewing agile scrum because I still don't think I am familiar enough with the working process. Getting more Human Resources always seems to be the issue for OSE so while having simple processes and protocols may not be possible good thorough training information seems most critical so that interested contributors can gradually move up the chain to teams etc. Also having more contributors than team members seems the most likely case this early in the development of distributed open source hardware as well as the most likely case when it is more popular. Many small contributions by non-experts may do more than teams eventually, but the software and management of that scale is currently daunting. So right now small teams and as many contributors as possible seems the most likely state of operations. The learning curve even on complex software isn't that hard for most people if it is consistently used and training systems gradually move users up to more advanced tiers making them able to contribute more and get positive feedback. Feedback and discussion seem critical I found a google doc the other day that had a list of good ideas about planning and discussion, but it seems to have been moved somewhere unsearchable now probably do to editing. I am starting to think that using the wiki is more critical than real time tools like google hangouts chat/audio/video. I have noticed the wiki discussion pages don't get used. This is unfortunate as they are ideal for documenting ongoing prototype decision making since they could log and version information that may not be ideal to clutter the main pages with. Often decisions and why they are made are critical to open source development because someone else may need to make changes that better suit their particular environment or usage case and may need to understand the decision chain of why something was done and how it may affect other decisions, parts et cetera. While nice planning software with graphical decision trees might be nice just documenting more discussion on the wiki would be a good start.

• AbeAnd Logs January
• AbeAnd Logs February
• AbeAnd Logs March
• AbeAnd Logs April
• AbeAnd Logs May
• AbeAnd Logs June
• AbeAnd Logs July
• AbeAnd Logs August
• AbeAnd Logs September
• AbeAnd Logs October
• AbeAnd Logs November
• AbeAnd Logs December

• AbeAnd Logs 2017
• AbeAnd Logs 2016