Bash: Add languages to Chromium

Is it possibe to use Bash to add languages to Chromium? That is, do the equivalent of going to Settings – Advanced – Languages in the Chromium GUI, activate the languages you want, and then activate spell-checking for the same languages? Had a look at this, but there doesn’t seem to be anything that fits the bill.

Creating file using crosh from Chrome extension [terminalPrivate.sendInput]

I’m attempting to interface with the Chrome OS “crosh” terminal through a Chrome extension. I’m using Secure Shell’s dev-id to get access to chrome.terminalPrivate. From my initial attempt, I’m able to start a crosh process and bash shell. However, I’m trying to create a file in the ~/Downloads directory and that doesn’t seem to be working. The file is never created as far as I can tell.

Here is the code that I’ve put together so far (I used this code from the Chromium developers as a starting point):

// Copyright (c) 2012 The Chromium Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

var shellCommand = 'shelln';
var croshName = 'crosh';

window.onload = function() {

function Crosh(argv) {
  this.argv_ = argv; = null;
  this.keyboard_ = false;
  this.pid_ = -1;

function commandTest() {

  chrome.terminalPrivate.openTerminalProcess(croshName, (pid) => {
    if (pid < 0) {

    this.pid_ = pid;

    var cmd1 = 'shelln';
    var cmd2 = 'touch ~/Downloads/test.txtn';

    chrome.terminalPrivate.sendInput(pid, cmd1,
      function (r1) {

    chrome.terminalPrivate.sendInput(pid, cmd2,
      function (r2) {

      function(result) {

function processListener(pid, type, text){

Thanks for your help!

What’s the best way to keep awake a network disk

I’m looking for the best way to keep awake the connexion between a PC and a network disk.

A webite is hosted on the network disk and during the night, the connection between those two “died” and a “error 403 forbidden access” appearing. A simple manual refresh of the webpage is enought to make it works again.

What’s the best way to counter that?

  • a exchange of file every x minutes?

  • an extension which detect the “error 403” screen a make a hard refresh everytime it’s appearing?

  • just a script with a ping xxx:xxx:xxx:xxx all day long?

  • something else I don’t even think about?