ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
1

Automating Workstation Setup

asked 2015-08-23 13:47:06 -0500

ruffsl gravatar image

updated 2015-08-23 14:45:47 -0500

I've been hacking at my kernel and breaking my system rather frequently lately setting up a USB3 ROS driver for a new 3D sensor. Aside from perhaps better recovery management, or using VMs, I'd like to find an programmatic way of bootstrapping a ROS environment for my workstation after every time I hose it. I've seen some people use chef cookbooks as means to automate a personalized suppresses, so I think that might be one direction to take.

Does anyone have working examples for quickly setting a Linux system?

edit retag flag offensive close merge delete

Comments

Is your question relevant to ROS, Robot Operating System?

130s gravatar image 130s  ( 2015-08-23 14:32:22 -0500 )edit

Pardon my first edit being too general, but my environment setup is ROS specific.

ruffsl gravatar image ruffsl  ( 2015-08-23 14:48:07 -0500 )edit

2 Answers

Sort by ยป oldest newest most voted
1

answered 2015-08-24 15:33:27 -0500

tfoote gravatar image

I've played with using puppet to setup a basic ROS environment.

https://forge.puppetlabs.com/tfoote/ros https://github.com/tfoote/puppet-ros

It was test a few months ago. It may need updating for more recent changes to some of the puppet module dependencies.

It's very basic at the moment and not fully parameterized, but is a good starting point for people.

edit flag offensive delete link more
3

answered 2015-08-24 00:07:18 -0500

ahendrix gravatar image

In general, trying to run a bad kernel shouldn't make your system unbootable or otherwise unusable; assuming you're running grub and you keep a working kernel installed alongside your existing kernel, you should just be able to select a working kernel from the grub menu at startup. Ubuntu will generally set this up automatically for you.

If you're doing more invasive kernel work that does destroy your file system, you should really do that in a VM.

edit flag offensive delete link more

Comments

+1: a borked kernel really shouldn't be an issue. If you trash all kinds of system libs in the process, recovery could be a bit more difficult though.

gvdhoorn gravatar image gvdhoorn  ( 2015-08-24 01:44:24 -0500 )edit

I was working on setting up intel's realsense sensor, some of it's USB3.0 attributes are hard to pipe to the VM software I had (like virtualbox), thus the need to use a real metal system for testing. Not to mention the VM overhead really slows things down when trying to profile performance.

ruffsl gravatar image ruffsl  ( 2015-08-26 16:30:04 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2015-08-23 13:47:06 -0500

Seen: 452 times

Last updated: Aug 24 '15