1. Chronos' Acolyte Mac Os Update
2. Chronos' Acolyte Mac Os Update
3. Mac Os Download

I recently got my hands on one of those Google ChromeBooks (Cr-48). Interesting to have an operating system that is just a web browser. But, as anyone likely reading this article already knows, the graphical interface is the web browser and the operating system is still Linux. But what version? Well, let’s go on a journey together.First, you need ChromeOS. If you’ve got a ChromeBook this is a pretty easy thing to get. If not, check http://getchrome.eu/download.php for a USB or optical download that can be run live (or even in a virtual machine). Or, if you know that you’re going to be using a virtual machine, consider a pre-built system from hexxeh at http://chromeos.hexxeh.net/vanilla.php. I have found the VMware builds to be a bit persnickety about the wireless on a Mac, whereas the VirtualBox builds ran perfectly. I split my time between the two anyway, so I’ve just (for now) been rocking VirtualBox for ChromeOS. When you load it for the first time it asks for a Google account. Provide that, select your network adapter, choose from one of the semi-lame account images ( for the record, I like the mad scientist one) and you’re off to the races.Next, we need a shell. When you first log in, you see a web page that shows you all of the Chromium apps you have installed. By default, you’ll see File manager and Web Store. If you’ve used the OS X App Store then the Chrome Web Store is going to look pretty darn familiar. My favorite for now is Chrome Sniffer. But all of these kinda’ get away from where we’re trying to go: get a scripting environment for Chrome OS.Chrome comes with 2 types of shell environments. The first is crosh. To bring up a crosh environment, use Control-Alt-t. This keystroke invokes the crosh shell. Here, type help to see a list of the commands available. Notice that cd, chmod, etc don’t work. Instead, there are a bunch of commands that a basic user environment might need for troubleshooting primarily network connections. “But this is Linux” you ask? Yup.At the help output you’ll notice shell. Type shell and then hit enter. The prompt will change from crosh> to chronos@localhost. Now you can cd and perform other basic commands to your hearts delight. But you’re probably going to need to elevate privileges for the remainder of this exersize. So let’s type sudo bash and just get there for now. If you’re using a ChromeBook, the root password might be root, or if you’re using a downloaded vm from hexxeh then it might be facepunch (great password, btw).Provided the password worked, the prompt should turn red. Now, if you’re using a hexxeh build then the file system is going to be read-only. You won’t be able to change the root password nor build scripts. But otherwise, you should be able to use passwd to change the password:

Click on the Chronos addon, which is the first addon listed, and then click Install. This will download and install the Chronos addon onto your Kodi device You will again receive a notification in the top right of the screen when it has been installed successfully. This page has two sections. First up is a table of commands, and then later in the page, you’ll find a quick and dirty guide (originally posted as its own article) on actually getting into and using the cross environment. Command Purpose exit Exit the crosh Shell help Display the crosh help helpadvanced Show advanced Continue reading Crosh Commands.

passwd chronosOnce you’ve got slightly more secure shell environment (by virtue of not using the default root password), it is time to do a little exploring. Notice that in /bin, you see sh, bash, rbash and the standard fare of Linux commands (chmod, chown, cp, attr, etc. Notice that you don’t see tcsh, csh or ksh. So bash commands from other platforms can come in, but YMMV with tcsh, etc. Running ps will give you some idea of what’s going on process-wise under the hood:ps auxFrom encrypts to crypto to the wpa supplicant, there’s plenty to get lost in exploring here, but as the title of the article suggests, we’re here to write a script. And where better to start than hello world. So let’s mkdir a /scripts directory:mkdir /scriptsThen let’s touch a script in there called helloworld.sh:touch /scripts/helloworld.shThen let’s give it the classic echo by opening it in a text editor (use vi as nano and pico aren’t there) and typing:echo 'Hello Cruel World'Now close, save and then run it:/scripts/helloworld.shAnd you’ve done it. Use the exit command twice to get back to crosh and another time to close the command line screen. You now have a script running on ChromeOS. Next up, it’s time to start looking at deployment. This starts with knowing what you’re looking at. To see the kernel version:uname -rOr better:cat /proc/versionGoogle has been kind enough to build in similar sandboxing to that in Mac OS X, but the concept that you can’t run local applications is a bit mistaken. Sure, the user interface is a web browser, but under the hood you can still do much of what most deployment engineers will need to do.If these devices are to be deployed en masse at companies and schools, scripts that setup users, bind to LDAP (GCC isn’t built-in, so it might be a bit of a pain to get there), join networks and the such will need to be forthcoming. These don’t often come from the vendor of an operating system, but from the community that ends up supporting and owning the support. While the LDAP functionality could come from Google Apps accounts that are integrated with LDAP, the ability to have a “One touch deploy” is a necessity for any OS at scale, and until I start digging around for a few specific commands/frameworks and doing some deployment scripts to use them, right now I’m at about a 6 touch deploy… But all in good time!

Other than the conventionally popular Windows and Mac OS, (and, among developers and geeks, Linux), one of the most popular operating systems for Netbooks and lightweight convertibles today is - Chrome OS. But if you have landed on this page, I am sure you already know that.

Now the problem is, Chrome OS was designed to be used only with certain type of hardware - low powered netbooks, so Google took a certain route, in which Chrome OS officially is available only on Chromebooks - certain types of netbooks that come preloaded with Chrome OS - and have to be certified by Google. Kind of like Mac OSX which you cannot use unless you use an iMac or a Macbook.

But ofcourse, you can use Chrome OS just as well on your own Laptop, if you so wish to, because, Chrome OS is actually based on - Chromium OS - the underlying opensource project.

There happens to be a kind guy arnoldthebat, who makes regular releases of builds of Chromium OS that are pretty much compatible with almost all x86 (i386, or 32 bit) and amd64 (64 bit Intel or AMD) CPU based laptops. Most of your generic hardware like touchpads, speakers should work, and if you're not too unlucky(read have a Broadcomm card), most probably your WiFi will work too. You can catch hold of his builds here - http://chromium.arnoldthebat.co.uk/
I'd recommend using the latest special build as those ones have the widest hardware support.

After you download the .img file, you can create a bootable USB on Linux using this command (given your USB drive is on /dev/sdb) -

You should boot from your USB drive (you'll need to enable legacy support if yours is a post-UEFI era BIOS), and play with the OS to make sure everything works, and if you like it, and want to permanently install it to your laptop, read on.

So, if you want Chromium OS to be the only operating system in your laptop, you can just press Ctrl + AltF2, login with user:chronos password:password and run the command sudo install
This will format your hard drive

But instead if you want to install Chromium OS as an additional OS to your laptop then there is way for that too. Here are some necessary conditions though -

1. You'll need to make 2 partitions, one 2GB and another at least 4GB in size. Your HDD should have that space, or you should create that by shrinking any existing partitions.
2. You need to be using GRUB as your bootloader. If you are running Linux with Windows/Mac I am assuming you already are running GRUB. If not, then you can still install GRUB - a step that you can figure out yourself

First take a look at the bootable USB you made out of the Chromium OS disk. It will have two important partitions called - ROOT_A and STATE.
We need to create corresponding partitions on your hard disk (these can be larger size than the ones on the USB, a larger STATE partition gives you more local storage space. A larger ROOT-A partition is mostly of no use, as this partition's content won't change in the future).

Let's consider we made the following partitions -

• /dev/sda7 - ext2 - 2.15GB
• /dev/sda8 - ext4 - 6GB

Now you should copy the corresponding partitions from your USB drive to your own hard disk using dd

Next step would be to add a corresponding boot entry for Chromium OS to your GRUB. For that edit /etc/grub.d/40_custom and add the following

Chronos' Acolyte Mac Os Update

This is considering your's is a GPT partitioned HDD. If not, remove the insmod part_gpt line, and change the root to (hd0,X) where X = root partition number.
After this run sudo update-grub2 to generate the grub.cfg.

Now there is tiny problem with Chromium OS - It expects the STATE partition to be on /dev/sda1 This is hardcoded into the OS. Usually since your /dev/sda1 would already be occupied by some OS (Windows or Linux), you cannot install the Chromium STATE partition there. For that we need to make Chromium expect STATE somewhere else.
Mount your ROOT-A partition, and edit the file /sbin/chromeos_startup on it.
Change the following line -

Change the 1 at the end to the whatever partition you have put STATE on. If it was on /dev/sda8, change the 1 to 8.

Chronos' Acolyte Mac Os Update

Also in the same file find and comment out this line

Mac Os Download

This is because we have not made an OEM partition, so we can't mount it. We do not need the OEM partition to make Chromium OS work.

Finally you should be ready to reboot into Chromium OS be selecting it from the GRUB boot menu.