About: Archiveascobd

Description
Metadata
Settings
- owl:sameAs
- Inference Rule:

About: Archiveascobd Sponge Permalink

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

If you want/need to get data into colinux before you have networking setup, you can use an archive file as a cobd and extract it inside colinux. Unfortunately the cobd device works in blocks of 512 bytes and any part of your file after the last block of 512 bytes will be cut off. ok, lets clarify things a little (reformulation) :

Attributes	Values
rdfs:label	Archiveascobd
rdfs:comment	If you want/need to get data into colinux before you have networking setup, you can use an archive file as a cobd and extract it inside colinux. Unfortunately the cobd device works in blocks of 512 bytes and any part of your file after the last block of 512 bytes will be cut off. <Gniarf> ok, lets clarify things a little (reformulation) :
dbkwik:colinux/pro...iPageUsesTemplate	dbkwik:resource/o6dRytwqR7V88YbRHCnYOQ==
abstract	If you want/need to get data into colinux before you have networking setup, you can use an archive file as a cobd and extract it inside colinux. Unfortunately the cobd device works in blocks of 512 bytes and any part of your file after the last block of 512 bytes will be cut off. * tar files are built in 512 byte blocks anyway so it is not an issue with these. * tar.gz and tar.bz2 files should be decompressed (to .tar) on the windows side. Suitable tools are available from (look for bzip2.exe, bunzip2.exe, gzip.exe, gunzip.exe, and tar.exe). * zip files can have padding prepended at the start so that their size is a multiple of 512 bytes. (They were designed this way to allow for self extracts). Plugwash has a tool to do the proper padding available at . To use it, specify the input and output files on the command line in that order and you will get a file suitable to use as a cobd device and unzip inside linux. <Gniarf> ok, lets clarify things a little (reformulation) : * to import and export data (files, mostly) from and to coLinux, you can use the network (ftp, wget, rcp, rsync...), the coserial extension (currently being developped) and raw devices, which are the subject of this page * since we need the network to download new software via apt-get, yum or emerge, and to run PuTTY and X servers or VNC, using the network to transfer data this is rather natural * unfortunately, sometimes the network can be quite hard or even impossible to setup on some Windows configurations, and sometimes the Linux image you are using doesn't support the network either (busybox rescue disks) * /dev/cobd2 as an example is a typical coLinux block device, it usually points to a file as defined in your coLinux .xml configuration file. it can also point to a whole partition, a ISO file, or a CD-ROM (either physical or emulated via DAEMON Tools), but thats not the subject here. * you can use those to transfert data from and to coLinux.

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