Skip to main content

It's 11:45p Should you be switching to Developer Mode

I want my ASUS Chromebox to do a few more things than I can get accomplished in normal mode, however, making that change in a time when we have containers like Docker and Rkt is a shame and a pity. The ChromeOS developers came up with this idea of Recovery Mode, however, from what I can tell it's just a simple chroot jail. But I think I've already made my point.
Getting my Asus Chromebox into recovery mode was as simple as inserting a pin into the recovery hole just above the Kensington lock hole.
I should be able to recover at any time and restore my system to it's original luster if things go terribly  bad. While I have been thinking about this for a while I had not executed. And now that things are progressing I'm having my concerns.

  • many of the screens and popups that are described are incomplete. There are plenty of warnings in the negative but very few in the affirmative.
  • Now that the machine has rebooted twice (automatically) the machine has clearly been power washed and I have to tell it about my network. (could have been worse)
  • Having to put my username and password in the dev mode system is giving me a hickup. I hope my dev mode system does not sync any crud into my google repo. (it's better that my sync password is different from my user password. Thank goodness for small favors)
  • While I'm in developer mode I'm not sure what to do next. I'll have to google the process again and bookmark the steps this time.
I'll try to update this with my next link.

Comments

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

Agile is still dead and has been since 1991

[updated 2011.09.30] yet another response to Agile is good.
When you have so much of you career invested in something like Agile, XP etc... it can be hard to see the forest for the trees. I had a consulting job in The Haag many years ago. IBM was the incumbent contractor at the customer site (a bank) but after 5 years on the job they had not written a single line of functioning code. In the office there were two teams of software people... both behind closed doors. The first team was the Data team and the second team was Functional. They rarely spoke and they never shared information. I was there for a week, introduced the client to OO and we had a functioning prototype. Smart people do smart things, You cannot make an underachiever exceptional by using Agile. Either they get "it" or they don't.
I just commented on a blog. I'm sure there is some validity to his post beyond observing that Agile Scrum is broken. It certainly is not what it was originally intended but for…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…