I don’t know how to put tags on (using eternity), but this is, in fact, serious.

So, turns out my high school left developer mode accessible on chromebooks. Sick of the restrictions that even make doing schoolwork slow, I wanted to set up dual boot for Linux Mint and Chrome Os.

My main concern, however, is maintaining the original content on my chromebook in order to keep it functional (and still appear somewhat standard to the school) while also giving me the access to the stuff I need.

Entering google’s developer mode claims to “erase all local data”. If this does not include applications, please tell me as that would solve every problem below.

Main concerns:

  • My school uses GoGuardian, and some teachers make use of the remote screen viewing feature. On another school computer, creating an account using my school gmail automatically installed the app, and I’m hoping a separate set-up will still do this.

  • My school has a lot of kiosk apps, some of which I have used, others which I have not. I’ll provide a list if asked, but my main concerns are testnav (ap test), DRC insight, and NWEA secure testing+state solutions.

Inb4 “don’t do this”: I do not care, and this does not help. If the task becomes too much for me, then I’m not doing it. But as of now, I’m deadset on trying to get this to work.

Edit: It’s not a good idea to risk your computer, I realized that as time went on. The challenges and the fact that the easiest options rely on hardware manipulation are just unsafe in general. Vox OS, as suggested by another user who develops the project, worked more than fine and doesn’t risk destruction. Settle for a little less in exchange for little risk.

  • mean_bean279@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    10 months ago

    It wipes data, it’s often not worth it (usually CBs for k12 are 16gb rom). When I managed my admin console I ran Linux on a CB to help resolve an issue we had with Zoom due to device limitations, but Linux at the time was still crippled by no correct access to microphone, which may have since changed. It’s a school device, just leave it be. You’re going to come up on state standardized testing time which means they’ll likely lock down your updates to prevent any further ones from applying. Plus you’ll most likely create a situation where the device will have to be power washed and reset again to comply with secure browsers.

    Most likely developer mode was left open as certain programming classes required it to be open in order to run some interface I can’t remember.