~Toughbooktalk~

I downloaded the Cr OS in Rob's link. Burnt a disk and I ran it live on my Macbook. ( I got bored with Toughbooks at the moment)
OSX has been a learning experience. Windows does not look so bad now. That's another thread.

Cr OS does not see the wifi card. I tried the stock Broadcom and an Intel 5100. Well I should say the network setup does not see the card. Yast does. Whatever Yast is?
I am installing Cr OS to the HDD right now.

The Arnoldthebat version looks to have a bit more features, but it seems to require jumping through terminal hoops to install. It downloads as a drive img file. This is not an iso and must be installed via a usb stick. I will mess with it after work.

So far, I like the looks of Cr OS.

Help!!!! What's the deal with the wifi?

I did something wrong...Cr OS won't boot from the Hard drive..ARRRGGGHH

Shawn wrote:Whatever Yast is?

Yet Another Setup Tool.

It says Yast has control of network config. I did not see how to change any settings in Yast. Just viewing them. Maybe because I was on a Live CD version of Cr OS.
I think I may have figured the boot problem. Since it is a Macbook, the HDD has a GPT partition table. I probably need to switch that to a MBR partition table.

Hmm...I guess RTFM applies to me.


Activating the Network Device

If you use the traditional method with ifup, you can configure your device to either start during boot, on cable connection, on card detection, manually or never. To change device start-up, proceed as follows:

In YaST select a card from the list of detected cards in Network Devices > Network Settings and click Edit.

In the General tab, select the desired entry from Device Activation.

Choose At Boot Time to start the device during the system boot. With On Cable Connection, the interface is watched for any existing physical connection. With On Hotplug, the interface is set as soon as available. It is similar to the At Boot Time option, and only differs in the fact that no error occurs if the interface is not present at boot time. Choose Manually to control the interface manually with ifup. Choose Never to not start the device at all. The On NFSroot is similar to At Boot Time, but the interface does not shut down with the rcnetwork stop command. Use this if you use an nfs or iscsi root file system.

Click Next.

To activate the configuration, click OK.

Well this is less than fun... The screen is all doubled and I cannot click on the "Let's Go" button for some reason... I am surprised though that not only did the WIFI work but the 4G LTE for T-Mobile did as well...

I am attempting to make a USB installer for Neverwares version of Chromium.

Definitions:

dd = name of the little program
if = input file
.img = image
of = ouput file
/dev/sd? = path to the usb stick
bs = read and write up to BYTES bytes at a time

And so it means "Use dd to read ChromeOS.img and write it to usb stick in increments of 4M." That is an exact byte by byte image.

FAQ
1. If I write to /dev/sda will it overwrite my hard drive? YES and YES I'm trying to scare you
2. How do I know what /dev/sdX is? I hot-plug a stick and run dmesg in terminal. Normally the first stick is /dev/sdb then /dev/sdc and so on.
3. Can I copy from one usb to another? Yes, change the path. (dd if=/dev/sdX/ChromeOS.img of=/dev/sdX bs=4M) This is an example only. The X is a safety net....otherwise a cut and paste would run dd.

If you follow instructions, making a Neverware Cloudready version of Chromium USB stick is easy.
Installed it...Not really my cup o tea..
Looks nice and professional. Not really an OS in my opinion. Web only and limited.
I will explore Cr OS and arnoldthebat's versions again. I think they may have more substance.

Now if I can figure how to get Cr OS to boot from the HDD.

I really need some 32-64gb SSD's for doing this load and run testing.