Skip to content

saidimu/ninjaduino

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

to deploy:

25 dput local seabeagle3changes 26 rsync -avz ~/archive/oneiric mwotton_ninjadeb@debrepo:

Hi Mark,

I just had a go at these instructions. There were a number of things I found confusing, so I'm writing them here.

# How many groups should ninja be a member of?

First, you say that it runs as ninja user and that it must be a member of the dialout group.

Fine, but many of your instructions involve editing things in /etc and using sudo.

This means ninja must be a sudoer and hence be a member of the admin group. I checked

the groups for the ubuntu user and found that it had many groups: ubuntu adm dialout cdrom floppy audio dip video admin. How many of these are necessary?

Most of the installation instructions are run as 'ubuntu'. The process itself should run as 'ninja'. This is necessary because we don't want to give sudo to ninja unnecessarily. After creating the image, the ubuntu user could even conceivably be deleted from the box.

# Confusing instructions

Also, there are parts of the instructions that I find confusing. When you type

~~~

sudo vim /etc/apt/apt.conf.d/50unattended-upgrades

~~~

are you then supposed to copy in the text that follows? Because when I typed that

command I already had the following in the file. It's what you wrote below but

there's a lot more. Is it all necessary? And on a virgin beagle will this file

even exist? I'd really like to know. My beagle is not virgin. It could have stuff on

there already.

Just the one line about mwotton. The rest was already there and is legit, it's just the default ubuntu bumf.

--------

# More confusion

How do I know this is working? Is a version number updated somewhere? I rebooted

but I really don't know if this thing is working or not.

To really test it, i'd have to release a new version of seabeagle with a trivial change, and check that it upgrades it within a day. If you've got a clean machine installed, let's check that - I'll try to be online all day.

How do I know if an unattended upgrade works? Is there a log of where it checks for stuff

and then downloads it?

a quick google shows: http://linuxcommando.blogspot.com/2008/08/how-to-show-apt-log-history.html

basically /var/log/dpkg.log

Your instructions follow.....


runs as 'ninja' user user must be a member of the 'dialout' group

steps for preparing a ninja:

ubuntu@omap:~$ cat /etc/apt/sources.list
deb http://ports.ubuntu.com/ubuntu-ports/ oneiric main universe multiverse
deb http://ports.ubuntu.com/ubuntu-ports/ oneiric-updates main universe multiverse
deb http://ninjadeb.nfshost.com/ oneiric/
deb-src http://ninjadeb.nfshost.com/ oneiric/

Add Mark's key

$ gpg --keyserver keyserver.ubuntu.com --recv 7A330BF0

Add to trusted keyring

$ gpg --export --armor 7A330BF0 | sudo apt-key add -

Refresh package archive

$ sudo apt-get update
$ sudo apt-get install unattended-upgrades

Configure unattended-upgrades

$ sudo vim /etc/apt/apt.conf.d/50unattended-upgrades 
// Automatically upgrade packages from these (origin, archive) pairs
Unattended-Upgrade::Allowed-Origins {
// releases from ninjablocks repo
        "mwotton oneiric";
        "${distro_id} ${distro_codename}-security";
//      "${distro_id} ${distro_codename}-updates";
//      "${distro_id} ${distro_codename}-proposed";
//      "${distro_id} ${distro_codename}-backports";
};

Configure unattended-upgrades

sudo vim /etc/apt/apt.conf.d/10periodic
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::AutocleanInterval "7";
APT::Periodic::Unattended-Upgrade "1";

Actually install the packages

sudo apt-get install seabeagle

About

The Arduino code that runs on the ninja

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published