mtreavis

quick update, Rich Hall, one of our support guys has put this script together that may help. Big caveat: it's definitely not a supported RM product & it's very much beta.. in fact here's Rich's post: If you want to try it you'll need to edit so that it matches your own server names (search for and replace sal-dc01 and sal-dc02) To make it run copy it onto a mini book and then from a terminal (ctrl-alt-t) enter the command sudo chmod a+x cc3\ connection.sh This will make it executable. you can then launch it by entering the command : ./cc3\ connection.sh Things to note: 1) If you run it twice in one session it tries to unmount any existing shares. If the unmount fails it will delete the contents of the shared folders 2) It stores usernames and passwords in plain text files. It deletes them as soon as it's used them 3) Ideally it needs to be encrypted before being left on a station. So, I wouldn't be passing it on to end users without some updates (and a safe backup of user data) Please feel free to give it a try & let us know what you think, and if you make any changes that are really useful please share them. cc3_connection.txt

Hi, some answers to some of your questions.. Re: RM Repositories - interesting idea, in the short term it is possible to install downloaded .deb packages with dpkg, otherwise I have connected one to the debian repositories and installed apps from there (I don't have the links handy atm, a quick Google should dig them out.) - I did this through synaptic ('sudo synaptic' from a console) Re: CC3 connectivity - as mentioned, our software guys are looking at this sort of thing, more detail as soon as we can. In the meantime, has anyone tried a scripted method for connecting to cc3 user shares / shared areas? - happy to provide any help I can.. Finally, Ubuntu... I installed Ubuntu on one of our test systems a couple of weeks ago (mostly from instructions here: http://forum.eeeuser.com/viewtopic.php?id=1285) Acpi caused the biggest grumbles but as the sources are now available I would imagine those issues are resolvable. I had to use ndiswrapper to get wifi working. If you are going to try any hacks it's well worth making a recovery usb stick from the included CD, it takes less than 5 mins to restore, and is great in an emergency..

Thanks for the replies so far, keep them coming! Webman, our softwere dev & test teams have been doing loads of work around RM's software products to make sure that there is out of the box - check TEC article TEC1050864 on rm.com/support - I think it covers what you're looking for. Grumbledook, from reading your post am I right in thinking that you're looking to the infrastructure to provide an insecure low service hotspot environment next to a secured enterprise environment? If I've got that right, what support would you need built into the minibook to work in the secured environment?

I'm Matt Treavis & I work in the engineering group at RM that has just released the miniBook / eeePC. I've spoken to Russell & he's ok'd me posting - as long as I don't advertise... :? miniBook has opened us to new concept (well new for RM) in that we're selling a mainstream linux device. Our linux expertise is growing, but we have very experience of it in a desktop education environment. So I'm interested to get some feedback from you on how we can better support the miniBook? I'd like to hear about about any bright ideas, but as a starter for 10 what are your thoughts on wireless capability? Currently the miniBook supports WEP & WPA out of the box, but using wpa_supplicant stronger security should be possible - has anyone tried this in their network? also, how important is enterprise level security for a product like this? any thoughts? Cheers, Matt