From: Vargster <var...@gm...> - 2013-03-22 19:13:06
|
Thomas, When you're doing that, you can copy over your code in one hit but I'd recommend getting the basic install running first, then activating your code one bit at time, to make make sure they each run OK before moving onto the next one. Otherwise you can have multiple issues causing chaos. If you spot anything wrong in the wiki, feel free to correct it or email me a list and I'll update it. Lee On Fri, Mar 22, 2013 at 4:29 PM, Thomas Paine <pai...@gm...> wrote: > I am leaving work early today, and plan on heading home and tackling this. > I do like the advice to pick a distro and stick to it. I have been having > more success with ubuntu so I will stick with that. > > I have a fresh 12.04.2 LTS downloaded and ready to install now and will do > a server version with no gui. > > I will report back and let you know how I make out. > > I also thought of something, that might be hanging my install up. I coped > my mh.private.ini and my items.mht from my old machine I had running last > year to the new machine. Maybe a better plan would be to do everything from > scratch including moving in the code directories? I just copied all my code > directories and maybe that has been messing things up as well? > > Thanks. > > > On 22 March 2013 11:10, Vargster <var...@gm...> wrote: > >> >> Thomas, >> Did you install it using the Ubuntu wiki installer? Did it work? >> I take it it did, but there's nothing in the wiki about installing X10, >> one wire etc? >> Jumping from distro to distro just wastes time in my humble opinion. >> Stick to Ubuntu/Debian and google the solutions, it can't be that hard - I >> managed to get it all working the first time without the wiki.... >> If you do make any progress, keep notes and add them to the wiki to help >> those that follow you. >> >> Michael, >> I see what you're saying but, looking at the diffs, the wiki install >> guide has barely been touched since it was written (until I waded in last >> month). It's the best/most up to date guide we have. And covers 90% of the >> installation in detail. It just needs a bit more expansion to cover then >> most used hardware. >> >> I agree it would be nice to have a guide for Ubuntu, another for Debian, >> a three/fourth/etc for Fedora, Red Hat, Centos, Arch, Gentoo, LFS, etc >> realistically we don't have the manpower. >> >> I 'do' Ubuntu, I used the old wiki guide in December when I built my new >> MH install. It was out of date, I made notes, then I updated the wiki. >> I planned on reinstalling a VM from scratch to sanity check it, but >> Thomas go there first and found some holes. >> I still plan on the VM just as soon as I get some time at home. >> Sadly, I no longer use X10, so don't have the kit to play with, but I can >> add some notes from memory. >> One wire I've never used so someone else will have to add that. >> >> Lee >> >> >> >> On Fri, Mar 22, 2013 at 12:35 PM, Michael Stovenour < >> mi...@st...> wrote: >> >>> On Mar 21, 2013 3:44 PM Robert wrote, >>> > >>> > On Thu, Mar 21, 2013 at 2:05 PM, Joel Davidson <jr...@pr...> >>> wrote: >>> > > A good addendum to the linux install instructions might be to include >>> > > the package names of the perl modules we need for mh, >>> > >>> > With the exception that I think it should be in or associated with >>> > the main install instructions and not just those for Linux (IIRC, an >>> > updated version of Strawberry Perl v5.16 for Windows was just >>> > released recently...), I totally agree. >>> >>> There is already a list of required packages here: >>> http://misterhouse.sourceforge.net/install.html. Let's work on >>> amending that list if >>> needed. I find the Ubuntu instructions on the wiki >>> http://misterhouse.wikispaces.com/Install+Packages to be rather >>> complete and well written. >>> However, we need to decide which install instructions will be user >>> contributed (i.e. wiki) >>> and official project documentation (i.e. docs/[*.pod|*.html]). I, for >>> one, do not want to >>> support new users trying out various, ever changing versions of user >>> contributed (i.e. >>> wiki) installation instructions. However I totally agree that the >>> current official >>> install instructions for [Linux|Unix] needs to be updated. We should >>> work on a scheme >>> that separates distribution specific instructions (which might be on the >>> wiki) from the >>> non-distribution specific instructions in the official project >>> documentation. >>> >>> BTW, the package list may be somewhat distribution dependent in that >>> different >>> distributions (Activestate Perl, Strawberry Perl, Debian Perl package, >>> Fedora Perl >>> package, etc.) all have slightly different "default" packages. We could >>> create a superset >>> list but that would likely overwhelm most normal users. For sure the >>> developer >>> documentation should contain a "complete" list for distribution managers. >>> >>> Sincerely, >>> Michael >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Everyone hates slow websites. So do we. >>> Make your web apps faster with AppDynamics >>> Download AppDynamics Lite for free today: >>> http://p.sf.net/sfu/appdyn_d2d_mar >>> ________________________________________________________ >>> To unsubscribe from this list, go to: >>> http://sourceforge.net/mail/?group_id=1365 >>> >>> >> >> >> ------------------------------------------------------------------------------ >> Everyone hates slow websites. So do we. >> Make your web apps faster with AppDynamics >> Download AppDynamics Lite for free today: >> http://p.sf.net/sfu/appdyn_d2d_mar >> ________________________________________________________ >> To unsubscribe from this list, go to: >> http://sourceforge.net/mail/?group_id=1365 >> >> >> > > > -- > -=/>Thom > |