About: AccessBrokenImage   Sponge Permalink

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

(info thanks to waltiri on SourceForge) If you break your install (especially by doing something like installing ALL of kde, then restarting and having it lock up your system, you don't need to start from scratch. If you have the HD space, unpack your original root image (to a different name of course), edit the .xml file and make the 0 device your newly unpacked root file, then add a new block device which points to your broken root image e.g. Now run colinux and you can mount your broken image which lives at /dev/cobd1. First create a directory for the image:

AttributesValues
rdfs:label
  • AccessBrokenImage
rdfs:comment
  • (info thanks to waltiri on SourceForge) If you break your install (especially by doing something like installing ALL of kde, then restarting and having it lock up your system, you don't need to start from scratch. If you have the HD space, unpack your original root image (to a different name of course), edit the .xml file and make the 0 device your newly unpacked root file, then add a new block device which points to your broken root image e.g. Now run colinux and you can mount your broken image which lives at /dev/cobd1. First create a directory for the image:
dcterms:subject
abstract
  • (info thanks to waltiri on SourceForge) If you break your install (especially by doing something like installing ALL of kde, then restarting and having it lock up your system, you don't need to start from scratch. If you have the HD space, unpack your original root image (to a different name of course), edit the .xml file and make the 0 device your newly unpacked root file, then add a new block device which points to your broken root image e.g. Now run colinux and you can mount your broken image which lives at /dev/cobd1. First create a directory for the image: mkdir /mnt/disk2 and then: mount /dev/cobd1 /mnt/disk2 You should be able to then access the broken image at /mnt/disk2 Comment: <LarsOlson> Thanks, worked a charm. I think I'm (we're) going to make some small 200-400MB colinux rescue images for this purpose, as the 1GB image gets annoying to unzip when you are in trouble and low on hard drive space! I wonder what the smallest image possible is to make, while still keeping some basic and simple tools. Will have to test and experiment. MassTranslated on 25 Dec 2004. MassTranslated on Sun Apr 23 17:35:29 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