About: Lunar Linux   Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

Installed Lunar Linux from the CD image. The only sticky point was getting the destination partition into /dev/discs. I downloaded the latest install .iso (1.4.0) and unbzipped it (cygwin!) Then I set up the config file with the install partition at /dev/cobd0 and the cdrom image at /dev/cobd1. I set bootparms as 'root=/dev/cobd1', memory size=62, and set the network same as my Debian image (type=tap). My install partition is 1GB. When I started up colinux it booted right into the Lunar install. I first went to a shell and typed the following: RSBohn 2004.10.27

AttributesValues
rdfs:label
  • Lunar Linux
rdfs:comment
  • Installed Lunar Linux from the CD image. The only sticky point was getting the destination partition into /dev/discs. I downloaded the latest install .iso (1.4.0) and unbzipped it (cygwin!) Then I set up the config file with the install partition at /dev/cobd0 and the cdrom image at /dev/cobd1. I set bootparms as 'root=/dev/cobd1', memory size=62, and set the network same as my Debian image (type=tap). My install partition is 1GB. When I started up colinux it booted right into the Lunar install. I first went to a shell and typed the following: RSBohn 2004.10.27
sameAs
dcterms:subject
abstract
  • Installed Lunar Linux from the CD image. The only sticky point was getting the destination partition into /dev/discs. I downloaded the latest install .iso (1.4.0) and unbzipped it (cygwin!) Then I set up the config file with the install partition at /dev/cobd0 and the cdrom image at /dev/cobd1. I set bootparms as 'root=/dev/cobd1', memory size=62, and set the network same as my Debian image (type=tap). My install partition is 1GB. When I started up colinux it booted right into the Lunar install. I first went to a shell and typed the following: #mkdir /dev/discs #mkdir /dev/discs/disc0 #ln -s /dev/cobd0 /dev/discs/disc0/part0 Then exited the shell back to install. I skipped the native language support and partition drives section and went straight to 'Mount Filesystems'. I selected the disc0/part0 which I just linked to /dev/cobd0 and formatted it with ext3. I didn't use a swapfile (62M RAM is ok for the install). The next step, 'Transfer Lunar', went just fine. You probably should do the 'Architecture Optimize' if you're into that sort of thing, but don't bother with 'Configure Linux Kernel'. You'll just run the coLinux kernel. Since I'm just re-using the network settings I had working in the Debian coLinux I just copied the IP address etc., although I did choose a different Hostname. With the install completed I shut down coLinux, then changed the .xml file to boot from /dev/cobd0. When you restart coLinux just login as root (no password -- fix that!) and follow the instructions on the screen. To do 'lunar renew' 62M RAM wasn't enough. I added 100MB swap, that helped. 1GB might be a little small for a LunarLinux system. And how can I keep it from trying to rebuild the kernel? RSBohn 2004.10.27 MassTranslated on Sun Apr 23 17:36:28 UTC 2006
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software