Should I switch to Dev Mode?

[JustinM]

I haven't made the switch. The question is, should I? Are the dev
builds better, or are the outside builds solving problems with more
efficiency?

I use the computer for school-related things: taking notes, research,
etc etc etc. So I guess my question boils down to whether there is a
convincing argument for or against dev mode for me.

-Justin

[William Mosier]

If you dont know...then don't do it. The beta channel is stable and if all you are using it for is school related stuff, you should be fine.

--
From the "Cr-48 Test Pilots" Google Group.
To unsubscribe, send mail to:
cr-48-test-pil...@googlegroups.com
On the Web: https://groups.google.com/group/cr-48-test-pilots

--
|| William Mosier

|-| mos...@gmail.com

[Todd Vierling]

On Wed, Feb 9, 2011 at 3:35 PM, JustinM <jam...@gmail.com> wrote:

Hm. Seems it's time for a FAQ on this word. ;)

"Developer", unfortunately, has three meanings to Chrome OS:

1. "Developer Mode" is flipping the switch behind the battery, as
opposed to "Normal Mode". By itself, it gives you access to a Linux
shell and more CLI tools, but shows a warning message on each cold
boot because Verified Boot is disabled.

2. "Developer channel" is switching to the newer official builds with
the software switch in "About Chrome OS", as opposed to "Beta
channel". This does not require Developer Mode, but both can be
enabled at the same time.

3. "Developer build" is a build of Chromium OS that is unofficial.
Running in Developer Mode is a prerequisite for using developer
builds.

That said, you're referring to the last one, developer builds. I
publish some of these myself, but I don't recommend using them to
anyone who wants a known stable environment* for everyday usage.
Normal Mode on the Beta (default) channel is probably good enough for
what you need right now.

(* audio weirdness in the early public updates of Beta channel notwithstanding)

[CqN]

A couple of more points.  Developer channel releases are official releases.  They are pre-beta, so less testing has taken place, potential for more deal breaking bugs.  On  the positive side, these are built and availale more often than beta releases, perhaps about 3x the frequency so far, and bugs when fixed, will have the fixed version available earlier thru the Dev channel.

You can go back and forth between the current Dev Channel or Beta Channel versions, with a bit of work by forcing to download the correct version.  Your synced settings get carried between then in tact, when you switch.

Cordially, CqN

[John Mora]

@Todd - thanks for including the FAQ. I think there's a lot of confusion out there as to how some of this stuff operates.

@JustinM - Flipping the "Developer Mode" switch gives you the ability to modify the filesystem and run unofficial images. The Cr-48 was meant to be modified - and that's why Google provides recovery images. If you're curious about running a Developer Build (an unofficial build put together by a third party), I'd recommend just doing it. Keep in mind this is different from "switching channels" in your ChromeOS preferences.

[Gareth]

@Justin and CqN - your also able to use "sudo cgpt show" and "sudo
cgpt add " (note, both require A. the DevSwitch switched to the Dev,
or Root position, and B. You's a Good reader.) because when you
download a new Dev Channel Build it installs too either ROOT-A/KERN-A
or ROOT-B/KERN-B, you should note, that Developer Builds usually
Install specifically too ROOT-C. That being said, it's really quite
easy too switch between the Beta, DevChannel and Developer Builds of
ChromeOS/ChromiumOS.. that is.. until the DevChannel updates again!
but theres a way too force install to a specific ROOT/KERN set I
believe Todd can help with that, as I'm not too sure how too do it.
but for a while I was running ChromeOS Beta and Dev, and ChromiumOS.
Hope this helps!

[CqN]

Gareth,

Are you saying it is possible to have 3 valid images stay on the system at the same time???  I thought there were only two.  I had understood that the next image downloaded (auto, possibly even the manual  recovery from a usb stick) depending on the current setting is for beta channel or dev channel, would go to A if B is the current image in use, or to B if A is currently in use.  Please clarify.

Cordially, CqN

[Todd Vierling]

On Wed, Feb 9, 2011 at 4:32 PM, CqN <chacko...@gmail.com> wrote:
> Are you saying it is possible to have 3 valid images stay on the system at
> the same time???  I thought there were only two.

There are KERN-C and ROOT-C partitions that default to being empty.
The article on www.chromium.org about installing Ubuntu on a Cr-48
describes how to repartition the device to reallocate some stateful
partition space to the -C partitions.

The Chrome OS autoupdater only swaps between the -A and -B partitions
automatically; to boot from -C, you have to run "cgpt" manually. (This
is also described on that Ubuntu page.) Of course, when an autoupdate
is run, one of either -A or -B gets replaced with the update image.

[Gareth]

Todd did a better clarification than I could. I'm sorry I confused
you!

On Feb 9, 7:56 pm, Todd Vierling <t...@duh.org> wrote:

> On Wed, Feb 9, 2011 at 4:32 PM, CqN <chackoner...@gmail.com> wrote:
> > Are you saying it is possible to have 3 valid images stay on the system at
> > the same time???  I thought there were only two.
>
> There are KERN-C and ROOT-C partitions that default to being empty.

> The article onwww.chromium.orgabout installing Ubuntu on a Cr-48