Menu
▾
▴
colinux-devel — Cooperative Linux development mailing list
You can subscribe to this list here.
| 2004 |
Jan
(64) |
Feb
(530) |
Mar
(266) |
Apr
(580) |
May
(360) |
Jun
(161) |
Jul
(185) |
Aug
(164) |
Sep
(123) |
Oct
(160) |
Nov
(59) |
Dec
(84) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(156) |
Feb
(95) |
Mar
(124) |
Apr
(81) |
May
(79) |
Jun
(179) |
Jul
(35) |
Aug
(64) |
Sep
(56) |
Oct
(57) |
Nov
(18) |
Dec
(41) |
| 2006 |
Jan
(65) |
Feb
(37) |
Mar
(59) |
Apr
(73) |
May
(65) |
Jun
(27) |
Jul
(54) |
Aug
(76) |
Sep
(103) |
Oct
(23) |
Nov
(45) |
Dec
(29) |
| 2007 |
Jan
(41) |
Feb
(47) |
Mar
(61) |
Apr
(24) |
May
(14) |
Jun
(6) |
Jul
(23) |
Aug
(30) |
Sep
(16) |
Oct
(9) |
Nov
(53) |
Dec
(36) |
| 2008 |
Jan
(19) |
Feb
(49) |
Mar
(74) |
Apr
(21) |
May
(24) |
Jun
(5) |
Jul
(9) |
Aug
(53) |
Sep
(26) |
Oct
(23) |
Nov
(32) |
Dec
(19) |
| 2009 |
Jan
(47) |
Feb
(49) |
Mar
(39) |
Apr
(61) |
May
(28) |
Jun
(19) |
Jul
(12) |
Aug
(10) |
Sep
(31) |
Oct
(16) |
Nov
(60) |
Dec
(26) |
| 2010 |
Jan
(17) |
Feb
(9) |
Mar
(32) |
Apr
(11) |
May
(24) |
Jun
(33) |
Jul
(5) |
Aug
(2) |
Sep
(7) |
Oct
(8) |
Nov
(17) |
Dec
(7) |
| 2011 |
Jan
(12) |
Feb
(16) |
Mar
(2) |
Apr
(12) |
May
(5) |
Jun
(10) |
Jul
(3) |
Aug
(3) |
Sep
(2) |
Oct
(1) |
Nov
(17) |
Dec
(1) |
| 2012 |
Jan
(9) |
Feb
(9) |
Mar
(8) |
Apr
(4) |
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(8) |
Sep
(11) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
| 2013 |
Jan
|
Feb
(7) |
Mar
(4) |
Apr
(10) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(3) |
| 2016 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: Ballard J. <sac...@ho...> - 2004-02-18 02:14:14
|
Index: COLINUX_0/src/colinux/user/config.c=0A=
diff -u COLINUX_0/src/colinux/user/config.c:1.1.1.2 =
COLINUX_0/src/colinux/user/config.c:1.2=0A=
--- COLINUX_0/src/colinux/user/config.c:1.1.1.2 Sat Feb 14 18:55:37 2004=0A=
+++ COLINUX_0/src/colinux/user/config.c Tue Feb 17 17:51:01 2004=0A=
@@ -118,24 +118,40 @@=0A=
=0A=
co_rc_t co_load_config_memory(co_config_t *out_config, mxml_element_t =
*element)=0A=
{=0A=
- int i;=0A=
- char *size =3D "";=0A=
+ int i ;=0A=
+ char *s =3D "" ;=0A=
+ unsigned long x ;=0A=
+ unsigned long l ;=0A=
=0A=
for (i=3D0; i < element->num_attrs; i++) {=0A=
mxml_attr_t *attr =3D &element->attrs[i];=0A=
=0A=
if (strcmp(attr->name, "size") =3D=3D 0)=0A=
- size =3D attr->value;=0A=
+ s =3D attr->value;=0A=
}=0A=
=0A=
- if (size =3D=3D NULL) {=0A=
- co_debug("Invalid memory element: bad size\n");=0A=
+ if ( s =3D=3D NULL ) {=0A=
+ printf("Invalid memory element: bad memory specification\n") ;=0A=
return CO_RC(ERROR);=0A=
}=0A=
=0A=
- out_config->ram_size =3D atoi(size);=0A=
+ if( *s < '0' || *s > '9' )=0A=
+ goto co_load_config_memory_invalid_size_format ;=0A=
+ x =3D (unsigned char)( *s - '0' ) ;=0A=
+ while( *(++s) ) {=0A=
+ if( *s < '0' || *s > '9' )=0A=
+ goto co_load_config_memory_invalid_size_format ;=0A=
+ if( ( x =3D ( l =3D x ) * 10 + (unsigned char)( *s - '0' ) ) < l )=0A=
+ goto co_load_config_memory_invalid_size_format ;=0A=
+ }=0A=
+=0A=
+ out_config->ram_size =3D x ;=0A=
=0A=
return CO_RC(OK);=0A=
+=0A=
+ co_load_config_memory_invalid_size_format:=0A=
+ printf( "Invalid memory element: invalid size format\n" ) ;=0A=
+ return CO_RC(ERROR) ;=0A=
}=0A=
=0A=
co_rc_t co_load_config(char *text, co_config_t *out_config)=0A=
|
|
From: Sean B. <sea...@so...> - 2004-02-17 23:05:26
|
DQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIlBhdCBFcmxleSIgPHBhdGVy bGV5QG1haWwuZHJ1bmtlbmNvZGVwb2V0cy5jb20+DQpUbzogIlNlYW4gQnJvb2siIDxzZWFuX2Jy b29rQHNvZnRob21lLm5ldD4NCkNjOiA8bmlycEBlbWJsYXplc2VtaS5jb20+OyA8cGF0ZXJsZXlA ZHJ1bmtlbmNvZGVwb2V0cy5zZXJ2ZWJlZXIuY29tPjsgPGNvbGludXgtZGV2ZWxAbGlzdHMuc291 cmNlZm9yZ2UubmV0Pg0KU2VudDogVHVlc2RheSwgRmVicnVhcnkgMTcsIDIwMDQgMTA6MTIgUE0N ClN1YmplY3Q6IFJlOiBbY29MaW51eC1kZXZlbF0gSW5zdGFsbGluZyByZWd1bGFyIGRpc3RyaWJ1 dGlvbiBDRHMNCg0KDQp8IE9uIEZyaSwgMTMgRmViIDIwMDQgMTg6NDA6NDYgLTAwMDANCnwgPiBJ IHdhcyBqdXN0IGVzdGFibGlzaGluZyBhIHNpbWlsYXIgY29uY2x1c2lvbi4gSSBidWlsdCBteSBv d24ga2VybmVsIHdpdGggdGhhdCBwYXRjaCBhbmQgdHJpZWQgYm9vdGluZyBQYXQncyBnZW50b28g aW1hZ2UuIEkgZ2V0ICdhdHRlbXB0IHRvIGFjY2VzcyBkYXRhIGJleW9uZCBlbmQgb2YgZGV2aWNl JyBhcyBiZWZvcmUuIEJvb3RpbmcgZnJvbSB0aGUgZGViaWFuIGltYWdlIGlzIG5vIHByb2JsZW0u IEkgZGFyZSBub3QgdHJ5IG15IHJlYWwgcGFydGl0aW9uIGFnYWluLiBJIHRoZW4gZGVjaWRlZCB0 byB0cnkgcmVzaXppbmcgdGhlIGRlYmlhbiBpbWFnZSBhbmQgaGVyZSBpcyB3aGF0IEkgZGlkIChp ZiBhbnlvbmUgaGFzIHRoZSB0aW1lIHBsZWFzZSBnaXZlIGl0IGEgZ28gZm9yIGEgc2FuaXR5IGNo ZWNrKToNCnwgDQp8IG9rLEkgYXBvbG9naXplIGZvciB0aGF0IGltYWdlLg0KfCANCnwgSSBoYWQg aXQgcnVubmluZyBvbiBhIHZtd2FyZSBzeXN0ZW0gdGhhdCBzZWVtcyB0byBoYW5kbGUgc29tZSB0 aGluZ3MgbW9yZSBncmFjZWZ1bGx5LiAgVGhhdCBzeXN0ZW0gaXMgaTU4NiBvcHRpbWl6ZWQsIHdo aWNoIGltcGxpZXMgbW14LCB3aGljaCBpcyBkaXNhYmxlZCBieSBjb0xpbnV4LiAgeW91J2xsIGV4 cGVyaWVuY2UgcmFuZG9tIGxvY2t1cCwgcmVzZXRzLCBhbmQgb3RoZXIgcHJvYmxlbXMuDQpUaGFu a3MgZm9yIHBhc3NpbmcgdGhhdCBvbi4gVGhhdCBjbGVhcnMgdXAgYWxvdCBvZiB0aGluZ3MgZm9y IG1lLiBJIGhhZCBhbHJlYWR5IGJlZW4gd29ya2luZyBvbiBhIGdlbnRvbyBpbWFnZSAoZ2VudG9v IGlzIG15IHByZWZlcnJlZCBkaXN0cm8pIGFuZCBoYWQgYmVlbiBoYXZpbmcgdGhvc2Ugc3ltcHRv bXMuIEkgdG9vIGhhdmUgYmVlbiB1c2luZyB2bXdhcmUgYXMgb2J2aW91c2x5IGl0IGlzIGEgZ3Jl YXQgc2FuZGJveC4gQSBjb3VwbGUgb2YgcXVlc3Rpb25zIGlmIEkgbWF5Og0KQXJlIHlvdSBuYXQn dGluZyB5b3VyIHZpcnR1YWwgaG9zdCBpbnNpZGUgdm13YXJlIHRvIGFsbG93IGNvTGludXggb3V0 IG9yIGhvdyBhcmUgeW91IGdldHRpbmcgb3V0IHRvIHRoZSBuZXQ/DQpIYXZlIHlvdSBwZXJzb25h bGx5IHRyaWVkIHVzaW5nIGxhcmdlciBwYXJ0aXRpb25zICgyZ2IrKSwgcGh5c2ljYWwgb3IgbG9v cGJhY2s/DQoNCnwgDQp8IEFzIGZvciB0aGUgc2l6ZSwgdGhhdCB3YXMganVzdCBhICdmb3Jnb3Qg dG8gcmVuYW1lIGltYWdlJyBpc3N1ZS4NCnwgDQp8IEkgd2FzIHdvcmtpbmcgb24gMyBkaWZmZXJl bnQgaW1hZ2VzLCBhbmQgdGhvdWdodCB0aGUgb25lIEkgd2FzIHppcHBpbmcgd2FzIGEgZGlmZmVy ZW50IG9uZS4gIElmIHlvdSdyZSBpbnRlcmVzdGVkIGluIHRyeWluZyBhICd3b3JraW5nJyAoaTU4 NiBubyBtbXggb3B0aW1pemF0aW9ucykgaW1hZ2UsIGZpbmQgbWUgb24gaXJjIChzMGJlKS4NCkhh dmluZyBqdXN0IHJlYWxpc2VkIG15IHN0dXBpZGl0eSBpbiBidWlsZGluZyBhbiBpNjg2IGltYWdl IChkdWgpIEkgd2lsbCBiZSB0cmFja2luZyB5b3UgZG93bi4gTWF5YmUgd2UgY2FuIGRvIGEgJ3N3 YXAnLiBXb3VsZCB5b3UgYmUgb24gZnJlZW5vZGU/DQoNCnwgDQp8IFBhdCBFcmxleQ0KfCANCnwg DQp8IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0NCnwgU0YuTmV0IGlzIHNwb25zb3JlZCBieTogU3BlZWQgU3RhcnQgWW91ciBMaW51eCBBcHBz IE5vdy4NCnwgQnVpbGQgYW5kIGRlcGxveSBhcHBzICYgV2ViIHNlcnZpY2VzIGZvciBMaW51eCB3 aXRoDQp8IGEgZnJlZSBEVkQgc29mdHdhcmUga2l0IGZyb20gSUJNLiBDbGljayBOb3chDQp8IGh0 dHA6Ly9hZHMub3Nkbi5jb20vP2FkX2lkPTEzNTYmYWxsb2NfaWQ9MzQzOCZvcD1jbGljaw0KfCBf X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KfCBjb0xpbnV4 LWRldmVsIG1haWxpbmcgbGlzdA0KfCBjb0xpbnV4LWRldmVsQGxpc3RzLnNvdXJjZWZvcmdlLm5l dA0KfCBodHRwczovL2xpc3RzLnNvdXJjZWZvcmdlLm5ldC9saXN0cy9saXN0aW5mby9jb2xpbnV4 LWRldmVs |
|
From: Dan A. <da...@gm...> - 2004-02-17 22:27:19
|
Hello, I've temporarily hidden away the Gentoo image that Pat released last week from the sourceforge page due to instabilities of that image running under the latest coLinux version. The image itself is not to blame. Currently, both Linux kernel and userspace code compiled with -march=i686 that runs under coLinux may cause the host machine to spontaneously reboot. I was anticipating this problem quite ahead and I am glad it occured with easy reproducibility. The cause of the problem resides in the code which handles the switches between Linux and Windows. It doesn't preserve the entire the state of the processor. There are FPU, MMX, 3Dnow!, SSE, SSE2, and sysenter registers (plus non maskable interrupts that need to be disabled during this switch and in the coLinux context). This problem goes to the top of priorities regarding development, along with any instability issue that could arise. I am going to dedicate time for solving this, any i386 expert's help would be appreciated. -- Dan Aloni da...@gm... |
|
From: Pat E. <pat...@ma...> - 2004-02-17 22:16:35
|
On Fri, 13 Feb 2004 18:40:46 -0000 > I was just establishing a similar conclusion. I built my own kernel with that patch and tried booting Pat's gentoo image. I get 'attempt to access data beyond end of device' as before. Booting from the debian image is no problem. I dare not try my real partition again. I then decided to try resizing the debian image and here is what I did (if anyone has the time please give it a go for a sanity check): ok,I apologize for that image. I had it running on a vmware system that seems to handle some things more gracefully. That system is i586 optimized, which implies mmx, which is disabled by coLinux. you'll experience random lockup, resets, and other problems. As for the size, that was just a 'forgot to rename image' issue. I was working on 3 different images, and thought the one I was zipping was a different one. If you're interested in trying a 'working' (i586 no mmx optimizations) image, find me on irc (s0be). Pat Erley |
|
From: Sean B. <sea...@so...> - 2004-02-17 18:48:15
|
UkU6IFtjb0xpbnV4LWRldmVsXSBJbnN0YWxsaW5nIHJlZ3VsYXIgZGlzdHJpYnV0aW9uIENEcw0K LS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206IE5pciBQZXJyeSANClRvOiAnUGF0 IEVybGV5JyANCkNjOiBjb2xpbnV4LWRldmVsQGxpc3RzLnNvdXJjZWZvcmdlLm5ldCANClNlbnQ6 IFR1ZXNkYXksIEZlYnJ1YXJ5IDE3LCAyMDA0IDQ6NTUgUE0NClN1YmplY3Q6IFJFOiBbY29MaW51 eC1kZXZlbF0gSW5zdGFsbGluZyByZWd1bGFyIGRpc3RyaWJ1dGlvbiBDRHMNCg0KDQpIaSwgDQo+ IFdlbGwsIGlmIHlvdSBtZWFudCB0aGUgcGF0Y2ggZnJvbSB0aGUgbWFpbCB0aXRsZWQgIkludmFs aWQgYXJndW1lbnQgemVyb2luZyBibG9jaz8iLCBpdCBkb2VzIE5PVCBzb2x2ZSA+dGhlIHByb2Js ZW0uIA0KSSB3YXMganVzdCBlc3RhYmxpc2hpbmcgYSBzaW1pbGFyIGNvbmNsdXNpb24uIEkgYnVp bHQgbXkgb3duIGtlcm5lbCB3aXRoIHRoYXQgcGF0Y2ggYW5kIHRyaWVkIGJvb3RpbmcgUGF0J3Mg Z2VudG9vIGltYWdlLiBJIGdldCAnYXR0ZW1wdCB0byBhY2Nlc3MgZGF0YSBiZXlvbmQgZW5kIG9m IGRldmljZScgYXMgYmVmb3JlLiBCb290aW5nIGZyb20gdGhlIGRlYmlhbiBpbWFnZSBpcyBubyBw cm9ibGVtLiBJIGRhcmUgbm90IHRyeSBteSByZWFsIHBhcnRpdGlvbiBhZ2Fpbi4gSSB0aGVuIGRl Y2lkZWQgdG8gdHJ5IHJlc2l6aW5nIHRoZSBkZWJpYW4gaW1hZ2UgYW5kIGhlcmUgaXMgd2hhdCBJ IGRpZCAoaWYgYW55b25lIGhhcyB0aGUgdGltZSBwbGVhc2UgZ2l2ZSBpdCBhIGdvIGZvciBhIHNh bml0eSBjaGVjayk6DQpNYWtlIGEgY29weSBvZiB0aGUgZGViaWFuIGltYWdlDQpGcm9tIGN5Z3dp biBvciBhIHJlYWwgTGludXgNCiMgZHUgRGViaWFuLTMuMHIwLmV4dDMuMWdiDQoxMDQ4NTc2DQoj IEluY3JlYXNlIHRoZSBzaXplIG9mIHRoZSBpbWFnZSBieSB0aGUgc2FtZSBzaXplIGFnYWluLiBp ZSB0byAyZ2IgDQojIGRkIGlmPS9kZXYvemVybyBvZj1EZWJpYW4tMy4wcjAuZXh0My4yZ2IgYnM9 MTAyNCBzZWVrPTEwNDg1NzYgY291bnQ9MTA0ODU3Ng0KMTA0ODU3NiswIHJlY29yZHMgaW4NCjEw NDg1NzYrMCByZWNvcmRzIG91dA0KQWRkIHRoaXMgbmV3IGltYWdlIHRvIHhtbCBmaWxlIGFzIGEg bmV3IGRldmljZSwgc3RpbGwgYm9vdCBmcm9tIHRoZSAxZ2IgYXMgcm9vdCBmcw0KYm9vdCBjb0xp bnV4DQpOb3cgdHJ5IA0KIyBlMmZzY2sgL2Rldi9jb2JkPw0KV2hhdCBkbyB5b3UgZ2V0IGhlcmU/ IEkgZ2V0IHNlZyBmYXVsdHMNCk15IG5leHQgc3RlcCB3b3VsZCBiZSB0byByZXNpemUgdGhlIGZp bGUgc3lzdGVtOg0KRnJvbSBkZWJpYW46DQphcHQtZ2V0IGluc3RhbGwgZXh0MnJlc2l6ZQ0KZXh0 MnJlc2l6ZSAvZGV2L2NvYmQ/DQpUaGlzIGJhaWxzIG91dC4gSXQgbG9va3MgbGlrZSB0aGUgaW1h Z2Ugd2FzIHJlc2l6ZWQgdGhvdWdoLg0KSnVzdCB3aGVuIHlvdSBjaGFuZ2UgZXZlcnl0aGluZyBh cm91bmQgYW5kIGJvb3QgZnJvbQ0KaXQgeW91IHdvbnQgZ2V0IGFueXdoZXJlLCBhdCBsZWFzdCBJ IGRpZG50Lg0KDQotIFRoZSBhYm92ZSBwcm9jZWR1cmUgaXMgdGhlIHdheSB0aGF0IGxvb3BiYWNr IGZpbGVzeXN0ZW1zDQphcmUgcmVzaXplZC4gSSBkb250IHdhbnQgdG8gY29weSBpbWFnZXMgdG9n ZXRoZXIgd2l0aCBjb3B5IC9iIGFzDQppKSB0aGUgYWJvdmUgcHJvY2VkdXJlIHNob3VsZCB3b3Jr DQppaSkgaXRzIHdpbmRvd3MNCmlpaSkgbmVlZCBzb21ldGhpbmcgdGhhdCBpcyBwb3J0YWJsZQ0K DQoNCk5pciANCi0gQ2FuIHlvdSBwbGVhc2Ugc2V0IHlvdXIgbWFpbCBjbGVhbiB0byB1c2UgcGxh aW4gdGV4dCBhcyBodG1sIGlzDQpyZWFsbHkgdWdseSB0aG91Z2ggSSBoYXZlIGp1c3QgdXNlZCBv dXRsb29rIGV4cHJlc3NvIHRvIHBvc3QgdGhpcyA6Lw0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut LS0tLSANCkZyb206IFBhdCBFcmxleSBbbWFpbHRvOnBhdGVybGV5QGRydW5rZW5jb2RlcG9ldHMu c2VydmViZWVyLmNvbV0gDQpTZW50OiBUdWVzZGF5LCBGZWJydWFyeSAxNywgMjAwNCAxMjozMiAN ClRvOiBOaXIgUGVycnkgDQpDYzogY29saW51eC1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQg DQpTdWJqZWN0OiBSZTogW2NvTGludXgtZGV2ZWxdIEluc3RhbGxpbmcgcmVndWxhciBkaXN0cmli dXRpb24gQ0RzIA0KDQoNCk9uIFR1ZSwgMTcgRmViIDIwMDQgMTI6MDE6MzUgKzAyMDAgDQpOaXIg UGVycnkgPG5pcnBAZW1ibGF6ZXNlbWkuY29tPiB3cm90ZTogDQo+ICoqKiBmZGlzayB3b24ndCB3 b3JrIA0KPiBmZGlzayBjYW4ndCBnZXQgYW5kL29yIG1vZGlmeSBhIHBhcnRpdGlvbiB0YWJsZS4g U2luY2Ugd2UgZG9uJ3QgcmVhbGx5IGhhdmUgDQo+IGEgcmVhbCBkaXNrLCB3ZSBkb24ndCBoYXZl IGEgcGFydGl0aW9uIHRhYmxlIGZkaXNrIGNhbiB1c2UuIEkgdGhpbmsgdGhpcyANCj4gd2lsbCBj YXVzZSB0aGUgaW5zdGFsbGVyIG9mIG1vc3QgZGlzdHJpYnV0aW9ucyB0byBmYWlsLiBOb3Qgc3Vy ZSB5ZXQgaG93IA0KPiBjb0xpbnV4IGNhbiBiZSBleHRlbmRlZCB0byBzdXBwb3J0IHRoaXMuLi4g DQpJIGJlbGlldmUgdGhpcyB3YXMgZml4ZWQgaW4gYSBwYXRjaCByZWNlbnRseSBwb3N0ZWQuLi4g DQogIA0KPiAqKiogL3Byb2MvcGFydGl0aW9ucyBpcyBlbXB0eSANCj4gUHJvYmFibHkgY2F1c2Vk IGJ5IHRoZSBzYW1lIHBvaW50IG9mIGxhY2stb2Ytc3VwcG9ydCBhcyB0aGUgcHJldmlvdXMgaXRl bSANCj4gKGZkaXNrKS4gDQo+IFRoZSBpbnN0YWxsZXIgdHJpZXMgdG8gY2hlY2sgd2hpY2ggcGFy dGl0aW9ucyBvZiB0eXBlICJMaW51eCIgKDgzKSBhcmUgDQo+IGF2YWlsYWJsZSBmb3IgaW5zdGFs bGF0aW9uLiBOb3JtYWxseSwgc3VjaCBhIHBhcnRpdGlvbiBpcyBjcmVhdGVkIGJ5IHRoZSANCj4g ImZkaXNrIiBzdGFnZS4gDQpwcm9iYWJseSBmaXhlZCBieSBhYm92ZSBwYXRjaC4gDQo+ICoqKiBJ U08gdW5zdXBwb3J0ZWQgDQo+IEFzIG5vdGVkIGJlZm9yZSwgd2UgY2FuJ3QgYm9vdCBmcm9tIENE LiBUaGlzIGlzIGFubm95aW5nLCBhcyB3ZSBoYXZlIHRvIGNvcHkgDQo+IHRoZSBjb250ZW50IHRv IGEgZGlzayBpbWFnZSwgYW5kIGJvb3QgaXQgdXNpbmcgc29tZSBzb3J0IG9mIGEgInJvb3QtZGlz ayIgDQo+IChmbG9wcHkgaW5zdGFsbGVyLCBldGMuKS4gDQo+IEJlaW5nIGFibGUgdG8gYm9vdCBm cm9tIENEIGlzIGEgbXVzdCBpZiB3ZSB3YW50IGNvTGludXggdG8gc3VwcG9ydCANCj4gaW5zdGFs bGF0aW9uIENEcyBhcyB0aGV5IGFyZSB3aXRob3V0IG1vZGlmaWNhdGlvbi4gDQp5b3UnbGwgaGF2 ZSB0byBnZXQgdGhlIHBlb3BsZSB3aG8gd3JpdGUgdGhvc2UgQ0RzIHRvIGFkZCBjb0xpbnV4IHN1 cHBvcnQgdG8gdGhlIGtlcm5lbHMgb24gdGhlIENEcyBmaXJzdC4gKHRoZSBrZXJuZWwgaW5jbHVk ZWQgd2l0aCBjb2xpbnV4IGhhcyBzcGVjaWFsIHBhdGNoZXMgaW5jbHVkZWQgdG8gZW5hYmxlIHRo ZSBmYWtlIG5ldHdvcmssIHRoZSBmYWtlIFBJQywgZXRjLg0KPiAqKiogL2Rldi9jb2JkMCBpcyBu b3Qgc3VwcG9ydGVkIGFzIGFuIGluc3RhbGxhdGlvbiB0YXJnZXQgDQo+IEl0IGlzIHBvc3NpYmxl IHRoYXQgbW9zdCBpbnN0YWxsZXJzIHdvdWxkIGFncmVlIHRvIGluc3RhbGwgb24gL2Rldi9oZFhY IG9yIA0KPiAvZGV2L3NkWFggKG9yIHNpbWlsYXIpLCBidXQgd291bGQgbm90IGFncmVlIHRvIHVz ZSAvZGV2L2NvYmRYLiBDYW4ndCByZWFsbHkgDQo+IGJsYW1lIHRoZW0gYXMgaXQgaXMgbm90IGEg c3RhbmRhcmQgZGV2aWNlIG5hbWUuIA0KPiBJJ20gbm90IHN1cmUgd2hhdCBpcyB0aGUgYmVzdCB3 YXkgdG8gc29sdmUgdGhpcywgYnV0IG1heWJlIGlmIHdlIGNvdWxkIGZha2UgDQo+IGEgIi9kZXYv aGRhMSIgaXQgd291bGQgYmUgZWFzaWVzdC4gDQpzYW1lIGFzIGFib3ZlIChjb2JkIGRyaXZlciB0 aGlzIHRpbWUpIG9yIHBlcmhhcHMgeW91IGNvdWxkIGNyZWF0ZSBhIHN5bSBsaW5rLiAgYWxzbywg cGVyaGFwcyBhIGRldmZzIGxheWVyIHNvbHV0aW9uIHdvdWxkIHdvcmsuDQo+ICoqKiBVbmF2YWls YWJsZSBrZXJuZWwgbW9kdWxlcyANCj4gTW9zdCBpbnN0YWxsYXRpb25zIGNvbWUgd2l0aCBhIGtl cm5lbCttb2R1bGVzIG9mIGl0cyBvd24uIE5vdyB3ZSB1c2UgYSANCj4gZGlmZmVyZW50IGtlcm5l bCwgc28gdGhlIGRpc3RyaWJ1dGlvbiBjYW4ndCB1c2UgaXRzIG93biBtb2R1bGVzLiBVc3VhbGx5 IGl0IA0KPiB3aWxsIGp1c3QgZ2l2ZSBzb21lIGVycm9ycyB0aGF0IHdlIGNhbiBpZ25vcmUsIGJ1 dCBtYXliZSB3ZSBjYW4gcHV0IHRoZSANCj4gY29MaW51eCBjb21waWxlZCBtb2R1bGVzIG9uIHRo ZSBpbnN0YWxsZWQgc3lzdGVtIGFmdGVyIGluc3RhbGxhdGlvbi4gDQpwdXR0aW5nIHRoZSBtb2R1 bGVzIG9uIHRoZSBzeXN0ZW0gaXNuJ3QgdG9vIHVucmVhc29uYWJsZS4gIEkgY291bGQgYnVuZGxl IGEgemlwIG9mIHRoZW0gd2l0aCBhbnkga2VybmVsIEkgY29tcGlsZS4gDQogIA0KPiAqKiogY29M aW51eCBjb25zb2xlIA0KPiBUaGUgY29uc29sZSBuZWVkcyBzb21lIGltcHJvdmVtZW50IHRvIG1h a2UgaW5zdGFsbGF0aW9uIGVhc2llci4gV2hpbGUgDQo+IHRlc3RpbmcgaXQsIEkgc2F3IHRoYXQg dGhlIHRleHQgZGlhbG9ncyBhcmUgbm90IHBhaW50ZWQgZnVsbHkgKHdoZXJlIGl0IGlzIA0KPiBq dXN0IHBsYWluIGNvbG9yLCB5b3UgY291bGQgc2VlIHRoZSBvbGRlciB0ZXh0KSwgYW5kIHRoZSBk aXJlY3Rpb24ga2V5cyANCj4gZGlkbid0IHdvcmsgKGxlZnQsIHJpZ2h0LC4uLikuIFNob3VsZCBi ZSBhbiBlYXN5IG9uZS4gTm90ZSB0aGF0IGl0IGlzIG5vdCBhIA0KPiB2ZXJ5IGJpZyBwcm9ibGVt IC0geW91IGNhbiBpbnN0YWxsIHdpdGggaXQsIGJ1dCBpdCBpcyB2aXN1YWxseSBtZXNzeS4gDQo+ IEJ0dywgaGF2aW5nIGEgZnJhbWUtYnVmZmVyIHN1cHBvcnQgZm9yIHRoZSBjb25zb2xlIChtYXli ZSB2ZXNhIGNvbXBhdGlibGUpIA0KPiBjb3VsZCBiZSBncmVhdCAtIGZvciBncmFwaGljIGluc3Rh bGxlcnMsIGJ1dCB0aGF0IHdvdWxkIGJlIHRvbyBtdWNoIHdvcmsuIA0Kd29yZHMgaGF2ZSBiZWVu IG1lbnRpb25lZCBmb3IgYSB2ZXNhZmIgc3R5bGUgZHJpdmVyIGJ1dCB1bnRpbCBvdGhlciAnYmln Z2VyJyBwcm9ibGVtcyBhcmUgc29sdmVkLCB0aGF0IHNlZW1zIHByZXR0eSBsb3cgb24gdGhlIHBv bGUuDQpvaywgbmV3IG15IHR1cm4gZm9yIGEgc2FuaXR5IGNoZWNrIGFuc3dlci4gDQpUaGUgbWFq b3IgcHJvYmxlbSBjdXJyZW50bHkgd2l0aCB0cnlpbmcgdG8gaW5zdGFsbCBhbm90aGVyIGRpc3Ry byBpbnNpZGUgb2YgY29saW51eCAobGVzcyBvZiBhIGhhY2suLi4pIGlzIHRoYXQgY29saW51eCBp cyBub3QgbmF0aXZlbHkgc3VwcG9ydGVkIGJ5IHRoZSBrZXJuZWwsIGFuZCBmcm9tIHdoYXQgSSd2 ZSBzZWVuLCBhIGtlcm5lbCB0cmVlIHBhdGNoZWQgZm9yIGNvbGludXggbWF5IG9yIG1heSBub3Qg YmUgc2FmZSBmb3IgYSBub24tY29saW51eCBrZXJuZWwuICANClRoaXMgbWVhbnMgdGhhdCBzeXN0 ZW1zIHdpbGwgZWl0aGVyIGhhdmUgdG8gaW5jbHVkZSBzb21lIHdheSB0byBkZXRlY3QgY29saW51 eCAobm90IHRvbyBkaWZpY3VsdCwgZnJvbSB3aGF0IEkndmUgc2VlbikgYW5kIGJvb3QgdGhlIGtl cm5lbCBhcyBzdWNoLCBvciBwcm92aWRlIGEgYm9vdCBmbG9wcHkgaW1hZ2UgdG8gc2V0dXAgYW4g ZW52aXJvbm1lbnQgZm9yIHRoZWlyIGlzby4NCk5vdywgYXNraW5nIHNheSwgcmVkaGF0LCB0byBz dXBwb3J0IGl0IG5vdywgd2hpbGUgaXQncyBub3Qgc3RhYmxlaXplZCBpcyBqdXN0IG5vdCByYXRp b25hbC4gIHRoaXMgaXMgd2h5IGlzb3MgYXJlIHByb3ZpZGVkIHRoYXQgYXJlIHByZWluc3RhbGxl ZCBmb3IgeW91ciBleHBlcmllbmNlcyAodGhlIGdlbnRvbyBvbmUgaXMgYnJva2VuLCBleHBlY3Qg YSBmaXhlZCBvbmUgaW4gdGhlIG5leHQgZGF5IG9yIHR3bykuICBJdCBhbGxvd3MgdGhlIGV4cGVy aWVuY2Ugd2l0aG91dCBzb21lIG9mIHRoZSBiaWcgcHJvYmxlbXMgY3VycmVudGx5IGVuY291bnRl cmVkLg0KSG9wZSBUaGlzIEhlbHBzLiANClBhdCBFcmxleSANCihzb21lIG9mIHRoaXMgbWlnaHQg bm90IGJlIDEwMCUgcGVyZmVjdCwgYnV0IGl0J3MgYWxsIGNsb3NlIGVub3VnaCkg |
|
From: Benoit M. <ben...@cg...> - 2004-02-17 17:26:46
|
Hi Your existing install doesn't have any compiled modules for the cL kernel... try recompile the modules within cL, gonna try this tonight And I've the same problem with fsck what i've done : used windows disk manager to create a partition without fs declared it in the xml file as a cobd device ;) used mkfs.ext3 on it inside cL with errors on some blocks tried to use it but fsch complain every time.... any idea? Benoit ----- Original Message ----- From: "Leon Commandeur" <leo...@ho...> To: <col...@li...> Sent: Friday, February 13, 2004 5:17 PM Subject: [coLinux-devel] Using existing install > Hi, i've been trying to get a existing (and working) debian install booting > through colinux. I've managed to get it booting thanks to the other thread > with the same name, but now it hangs on the fscheck. It appears to be unable > to find the swap memory and can't find the modules directory. > > Any suggestions on how to fix this? Should i add a line for the swap > partition as well? > > Thanks, > > Leon. > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel |
|
From: Nir P. <ni...@em...> - 2004-02-17 16:57:49
|
Hi, Well, if you meant the patch from the mail titled "Invalid argument zeroing block?", it does NOT solve the problem. Nir -----Original Message----- From: Pat Erley [mailto:pat...@dr...] Sent: Tuesday, February 17, 2004 12:32 To: Nir Perry Cc: col...@li... Subject: Re: [coLinux-devel] Installing regular distribution CDs On Tue, 17 Feb 2004 12:01:35 +0200 Nir Perry <ni...@em...> wrote: > *** fdisk won't work > fdisk can't get and/or modify a partition table. Since we don't really have > a real disk, we don't have a partition table fdisk can use. I think this > will cause the installer of most distributions to fail. Not sure yet how > coLinux can be extended to support this... I believe this was fixed in a patch recently posted... > *** /proc/partitions is empty > Probably caused by the same point of lack-of-support as the previous item > (fdisk). > The installer tries to check which partitions of type "Linux" (83) are > available for installation. Normally, such a partition is created by the > "fdisk" stage. probably fixed by above patch. > *** ISO unsupported > As noted before, we can't boot from CD. This is annoying, as we have to copy > the content to a disk image, and boot it using some sort of a "root-disk" > (floppy installer, etc.). > Being able to boot from CD is a must if we want coLinux to support > installation CDs as they are without modification. you'll have to get the people who write those CDs to add coLinux support to the kernels on the CDs first. (the kernel included with colinux has special patches included to enable the fake network, the fake PIC, etc. > *** /dev/cobd0 is not supported as an installation target > It is possible that most installers would agree to install on /dev/hdXX or > /dev/sdXX (or similar), but would not agree to use /dev/cobdX. Can't really > blame them as it is not a standard device name. > I'm not sure what is the best way to solve this, but maybe if we could fake > a "/dev/hda1" it would be easiest. same as above (cobd driver this time) or perhaps you could create a sym link. also, perhaps a devfs layer solution would work. > *** Unavailable kernel modules > Most installations come with a kernel+modules of its own. Now we use a > different kernel, so the distribution can't use its own modules. Usually it > will just give some errors that we can ignore, but maybe we can put the > coLinux compiled modules on the installed system after installation. putting the modules on the system isn't too unreasonable. I could bundle a zip of them with any kernel I compile. > *** coLinux console > The console needs some improvement to make installation easier. While > testing it, I saw that the text dialogs are not painted fully (where it is > just plain color, you could see the older text), and the direction keys > didn't work (left, right,...). Should be an easy one. Note that it is not a > very big problem - you can install with it, but it is visually messy. > Btw, having a frame-buffer support for the console (maybe vesa compatible) > could be great - for graphic installers, but that would be too much work. words have been mentioned for a vesafb style driver but until other 'bigger' problems are solved, that seems pretty low on the pole. ok, new my turn for a sanity check answer. The major problem currently with trying to install another distro inside of colinux (less of a hack...) is that colinux is not natively supported by the kernel, and from what I've seen, a kernel tree patched for colinux may or may not be safe for a non-colinux kernel. This means that systems will either have to include some way to detect colinux (not too dificult, from what I've seen) and boot the kernel as such, or provide a boot floppy image to setup an environment for their iso. Now, asking say, redhat, to support it now, while it's not stableized is just not rational. this is why isos are provided that are preinstalled for your experiences (the gentoo one is broken, expect a fixed one in the next day or two). It allows the experience without some of the big problems currently encountered. Hope This Helps. Pat Erley (some of this might not be 100% perfect, but it's all close enough) |
|
From: Leon C. <leo...@ho...> - 2004-02-17 16:23:03
|
Hi, i've been trying to get a existing (and working) debian install booting through colinux. I've managed to get it booting thanks to the other thread with the same name, but now it hangs on the fscheck. It appears to be unable to find the swap memory and can't find the modules directory. Any suggestions on how to fix this? Should i add a line for the swap partition as well? Thanks, Leon. |
|
From: Benoit M. <ben...@cg...> - 2004-02-17 13:26:34
|
just to say...... the correct syntax is : \Device\HarddiskVolumeX X depending on which drive/partition you want to access for ex : - 2 disks, 1 partition on each first : \Device\HarddiskVolume1 second : \Device\HarddiskVolume2 - 1 disk, 2 partitions on it first : \Device\HarddiskVolume1 second : \Device\HarddiskVolume2 if windows works as usual, primary partitions might be firsts listed then extended (doens't care on wich disks they are) Benoit ----- Original Message ----- From: "Benoit MICHEL" <ben...@cg...> To: "Regis NEBOR" <re...@ho...>; "Benoit MICHEL" <bem...@ca...>; <col...@li...> Sent: Monday, February 16, 2004 5:01 PM Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > ok > thx > ----- Original Message ----- > From: "Regis NEBOR" <re...@ho...> > To: "Benoit MICHEL" <bem...@ca...>; > <col...@li...> > Sent: Monday, February 16, 2004 4:55 PM > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > Do a little search in regedit, you'll prolly find the name of each current > > devices of your config > > > > Regis > > ----- Original Message ----- > > From: "Benoit MICHEL" <ben...@cg...> > > To: <col...@li...> > > Sent: Monday, February 16, 2004 7:43 AM > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > this is logic ;-) > > > Does windows name scsi drives like this?? > > > for ex, two IDE disks and one scsi one, will windows name the scsi drive > > > \\Device\harddisk3\VolumeX ? > > > and, what about cdrom drives? \\Device\cdromX ? is that right? > > > thx > > > Benoit > > > > > > ----- Original Message ----- > > > From: "Richard Goodwin" <ric...@ri...> > > > To: <col...@li...> > > > Sent: Monday, February 16, 2004 4:30 PM > > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > Well you must also ask yourself "how many hard drives, and how many > > > > partitions on each?" If you have only one hard drive, and the target > > > > partition is the 4th one on there, then of course you need to modify > the > > > > device name :-) > > > > > > > > ----- Original Message ----- > > > > From: "Benoit MICHEL" <ben...@cg...> > > > > To: <col...@li...> > > > > Sent: Monday, February 16, 2004 9:03 AM > > > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > ok thx, it runs now > > > > > > > > > > I'm trying to boot using debian file as cobd0 and > > > > \\Device\harddisk2\Volume2 > > > > > as cobd1 (this is just a partition without any fs on it, want to > > format > > > it > > > > > with mkfs.ext3 to begin my own install ;) ) > > > > > but anytime, it returns can't open device...... > > > > > I gonna look further tonight, till i'm at work now ;) > > > > > Benoit > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > From: "Richard Goodwin" <ric...@ri...> > > > > > To: <col...@li...> > > > > > Sent: Monday, February 16, 2004 3:35 PM > > > > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > > > \\Device\harddisk2\Volume2 is Window's internal object name for > that > > > > > > partition. If it is set at Index 0 in the XML file, then it > becomes > > > > > > presented by the Linux kernel as cobd0 once inside the partition. > > Thus > > > > > some > > > > > > manual hacking may be required (fstab, etc) I believe to make your > > > > > existing > > > > > > Linux partition boot properly. (cobd0 = coLinux block device 0 > > IIRC) > > > > > > > > > > > > By the way, my in-laws are named Benoit :-) > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "Benoit MICHEL" <ben...@cg...> > > > > > > To: <col...@li...> > > > > > > Sent: Monday, February 16, 2004 7:53 AM > > > > > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > > > > > > hi > > > > > > > > > > > > > > what about /dev/hdc2 ?? > > > > > > > \Device\Harddisk2\Volume2? > > > > > > > i'm not able to fully boot with others devices declared as > enabled > > > in > > > > > the > > > > > > > config file. > > > > > > > seems to freeze on co-net > > > > > > > Benoit > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > From: "Regis NEBOR" <re...@ho...> > > > > > > > To: <col...@li...> > > > > > > > Sent: Monday, February 16, 2004 1:48 PM > > > > > > > Subject: Fw: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > From: "Regis NEBOR" <re...@ho...> > > > > > > > > To: "Chakat Sandwalker" <san...@e3...> > > > > > > > > Sent: Monday, February 16, 2004 2:43 AM > > > > > > > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > > > > > > > > > > > > Hi > > > > > > > > > > > > > > > > > > This config file allowed me to boot on my /dev/hda2 : > > > > > > > > > > > > > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > > > > > > > <colinux> > > > > > > > > > <block_device index="0" path="\Device\HarddiskVolume2" > > > > > > > enabled="true"> > > > > > > > > > </block_device> > > > > > > > > > <bootparams>root=/dev/cobd0</bootparams> > > > > > > > > > <image path="vmlinux"></image> > > > > > > > > > </colinux> > > > > > > > > > > > > > > > > > > But the kernel will remain colinux's one. You'll have to > > change > > > > some > > > > > > > > setting > > > > > > > > > in the previous setup too. > > > > > > > > > I would say getting an image made with colinux in mind is > > easier > > > > at > > > > > > the > > > > > > > > > moment. > > > > > > > > > > > > > > > > > > Regis > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > From: "Chakat Sandwalker" <san...@e3...> > > > > > > > > > To: <col...@li...> > > > > > > > > > Sent: Monday, February 16, 2004 1:56 AM > > > > > > > > > Subject: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > > > > > > > > > > > > > > > I was told that I could save myself an 18MB download (and > a > > > gig > > > > of > > > > > > > space > > > > > > > > > > on a small C:) by using my installation of Mandrake 9.1 > > > instead. > > > > > > > > > > However, I can't figure out how to edit the XML file to > > point > > > to > > > > > the > > > > > > > > > > Linux partitions in order for it to boot. I'm running a > > dual > > > > boot > > > > > > > > > > system (XP and Mandrake), and I don't know too much about > > > Linux > > > > to > > > > > > go > > > > > > > > > > mucking about with it. Can anyone help? > > > > > > > > > > > > > > > > > > > > Sandy > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > > > > > > Build and deploy apps & Web services for Linux with > > > > > > > > > > a free DVD software kit from IBM. Click Now! > > > > > > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > > > > > > _______________________________________________ > > > > > > > > > > coLinux-devel mailing list > > > > > > > > > > coL...@li... > > > > > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > > > > Build and deploy apps & Web services for Linux with > > > > > > > > a free DVD software kit from IBM. Click Now! > > > > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > > > > _______________________________________________ > > > > > > > > coLinux-devel mailing list > > > > > > > > coL...@li... > > > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > > > Build and deploy apps & Web services for Linux with > > > > > > > a free DVD software kit from IBM. Click Now! > > > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > > > _______________________________________________ > > > > > > > coLinux-devel mailing list > > > > > > > coL...@li... > > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > > Build and deploy apps & Web services for Linux with > > > > > > a free DVD software kit from IBM. Click Now! > > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > > _______________________________________________ > > > > > > coLinux-devel mailing list > > > > > > coL...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > Build and deploy apps & Web services for Linux with > > > > > a free DVD software kit from IBM. Click Now! > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > _______________________________________________ > > > > > coLinux-devel mailing list > > > > > coL...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > Build and deploy apps & Web services for Linux with > > > > a free DVD software kit from IBM. Click Now! > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > _______________________________________________ > > > > coLinux-devel mailing list > > > > coL...@li... > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > ------------------------------------------------------- > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > Build and deploy apps & Web services for Linux with > > > a free DVD software kit from IBM. Click Now! > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > _______________________________________________ > > > coLinux-devel mailing list > > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > |
|
From: Pat E. <pat...@ma...> - 2004-02-17 11:23:10
|
On Tue, 17 Feb 2004 12:56:22 +0200 Nir Perry <ni...@em...> wrote: > Hi, > > Regarding the patch (fdisk) - could be true, I didn't check that... anyone > can add on this one ? > > Regarding the CDs - I don't think the distribution makers have to change > anything - all the fake hardware works as is. All but that "cobd0" device > driver, as mentioned. > > Regarding the kernel - I think most distributions would work just fine with > the colinux as a kernel (based on the original kernel.org version, and not > the one of the distribution). In the past, I have used the generic kernel on > several distributions without any problem. > We could also precompile some kernels with the colinux patch, and some of > the patches used by specific distributions, and make those available instead > of full disk images. > > I think it is better to make colinux work out-of-the-box on available > distributions, without a need to modify them. There are way too many of > them. Best way is to be as close as possible to the "generic" kernel in > behavior. > > Nir > if it got to the point that no patches were needed to the kernel, I believe that we could boot any os that supports the host arch. Pat Erley (not saying that this is a bad thing, but I believe it's 'signifigantly harder' than what we're working with now) |
|
From: Nir P. <ni...@em...> - 2004-02-17 10:58:57
|
Hi, Regarding the patch (fdisk) - could be true, I didn't check that... anyone can add on this one ? Regarding the CDs - I don't think the distribution makers have to change anything - all the fake hardware works as is. All but that "cobd0" device driver, as mentioned. Regarding the kernel - I think most distributions would work just fine with the colinux as a kernel (based on the original kernel.org version, and not the one of the distribution). In the past, I have used the generic kernel on several distributions without any problem. We could also precompile some kernels with the colinux patch, and some of the patches used by specific distributions, and make those available instead of full disk images. I think it is better to make colinux work out-of-the-box on available distributions, without a need to modify them. There are way too many of them. Best way is to be as close as possible to the "generic" kernel in behavior. Nir -----Original Message----- From: Pat Erley [mailto:pat...@dr...] Sent: Tuesday, February 17, 2004 12:32 To: Nir Perry Cc: col...@li... Subject: Re: [coLinux-devel] Installing regular distribution CDs On Tue, 17 Feb 2004 12:01:35 +0200 Nir Perry <ni...@em...> wrote: > *** fdisk won't work > fdisk can't get and/or modify a partition table. Since we don't really have > a real disk, we don't have a partition table fdisk can use. I think this > will cause the installer of most distributions to fail. Not sure yet how > coLinux can be extended to support this... I believe this was fixed in a patch recently posted... > *** /proc/partitions is empty > Probably caused by the same point of lack-of-support as the previous item > (fdisk). > The installer tries to check which partitions of type "Linux" (83) are > available for installation. Normally, such a partition is created by the > "fdisk" stage. probably fixed by above patch. > *** ISO unsupported > As noted before, we can't boot from CD. This is annoying, as we have to copy > the content to a disk image, and boot it using some sort of a "root-disk" > (floppy installer, etc.). > Being able to boot from CD is a must if we want coLinux to support > installation CDs as they are without modification. you'll have to get the people who write those CDs to add coLinux support to the kernels on the CDs first. (the kernel included with colinux has special patches included to enable the fake network, the fake PIC, etc. > *** /dev/cobd0 is not supported as an installation target > It is possible that most installers would agree to install on /dev/hdXX or > /dev/sdXX (or similar), but would not agree to use /dev/cobdX. Can't really > blame them as it is not a standard device name. > I'm not sure what is the best way to solve this, but maybe if we could fake > a "/dev/hda1" it would be easiest. same as above (cobd driver this time) or perhaps you could create a sym link. also, perhaps a devfs layer solution would work. > *** Unavailable kernel modules > Most installations come with a kernel+modules of its own. Now we use a > different kernel, so the distribution can't use its own modules. Usually it > will just give some errors that we can ignore, but maybe we can put the > coLinux compiled modules on the installed system after installation. putting the modules on the system isn't too unreasonable. I could bundle a zip of them with any kernel I compile. > *** coLinux console > The console needs some improvement to make installation easier. While > testing it, I saw that the text dialogs are not painted fully (where it is > just plain color, you could see the older text), and the direction keys > didn't work (left, right,...). Should be an easy one. Note that it is not a > very big problem - you can install with it, but it is visually messy. > Btw, having a frame-buffer support for the console (maybe vesa compatible) > could be great - for graphic installers, but that would be too much work. words have been mentioned for a vesafb style driver but until other 'bigger' problems are solved, that seems pretty low on the pole. ok, new my turn for a sanity check answer. The major problem currently with trying to install another distro inside of colinux (less of a hack...) is that colinux is not natively supported by the kernel, and from what I've seen, a kernel tree patched for colinux may or may not be safe for a non-colinux kernel. This means that systems will either have to include some way to detect colinux (not too dificult, from what I've seen) and boot the kernel as such, or provide a boot floppy image to setup an environment for their iso. Now, asking say, redhat, to support it now, while it's not stableized is just not rational. this is why isos are provided that are preinstalled for your experiences (the gentoo one is broken, expect a fixed one in the next day or two). It allows the experience without some of the big problems currently encountered. Hope This Helps. Pat Erley (some of this might not be 100% perfect, but it's all close enough) |
|
From: Pat E. <pat...@ma...> - 2004-02-17 10:38:51
|
On Tue, 17 Feb 2004 12:01:35 +0200 Nir Perry <ni...@em...> wrote: > *** fdisk won't work > fdisk can't get and/or modify a partition table. Since we don't really have > a real disk, we don't have a partition table fdisk can use. I think this > will cause the installer of most distributions to fail. Not sure yet how > coLinux can be extended to support this... I believe this was fixed in a patch recently posted... > *** /proc/partitions is empty > Probably caused by the same point of lack-of-support as the previous item > (fdisk). > The installer tries to check which partitions of type "Linux" (83) are > available for installation. Normally, such a partition is created by the > "fdisk" stage. probably fixed by above patch. > *** ISO unsupported > As noted before, we can't boot from CD. This is annoying, as we have to copy > the content to a disk image, and boot it using some sort of a "root-disk" > (floppy installer, etc.). > Being able to boot from CD is a must if we want coLinux to support > installation CDs as they are without modification. you'll have to get the people who write those CDs to add coLinux support to the kernels on the CDs first. (the kernel included with colinux has special patches included to enable the fake network, the fake PIC, etc. > *** /dev/cobd0 is not supported as an installation target > It is possible that most installers would agree to install on /dev/hdXX or > /dev/sdXX (or similar), but would not agree to use /dev/cobdX. Can't really > blame them as it is not a standard device name. > I'm not sure what is the best way to solve this, but maybe if we could fake > a "/dev/hda1" it would be easiest. same as above (cobd driver this time) or perhaps you could create a sym link. also, perhaps a devfs layer solution would work. > *** Unavailable kernel modules > Most installations come with a kernel+modules of its own. Now we use a > different kernel, so the distribution can't use its own modules. Usually it > will just give some errors that we can ignore, but maybe we can put the > coLinux compiled modules on the installed system after installation. putting the modules on the system isn't too unreasonable. I could bundle a zip of them with any kernel I compile. > *** coLinux console > The console needs some improvement to make installation easier. While > testing it, I saw that the text dialogs are not painted fully (where it is > just plain color, you could see the older text), and the direction keys > didn't work (left, right,...). Should be an easy one. Note that it is not a > very big problem - you can install with it, but it is visually messy. > Btw, having a frame-buffer support for the console (maybe vesa compatible) > could be great - for graphic installers, but that would be too much work. words have been mentioned for a vesafb style driver but until other 'bigger' problems are solved, that seems pretty low on the pole. ok, new my turn for a sanity check answer. The major problem currently with trying to install another distro inside of colinux (less of a hack...) is that colinux is not natively supported by the kernel, and from what I've seen, a kernel tree patched for colinux may or may not be safe for a non-colinux kernel. This means that systems will either have to include some way to detect colinux (not too dificult, from what I've seen) and boot the kernel as such, or provide a boot floppy image to setup an environment for their iso. Now, asking say, redhat, to support it now, while it's not stableized is just not rational. this is why isos are provided that are preinstalled for your experiences (the gentoo one is broken, expect a fixed one in the next day or two). It allows the experience without some of the big problems currently encountered. Hope This Helps. Pat Erley (some of this might not be 100% perfect, but it's all close enough) |
|
From: Pavel K. <pav...@at...> - 2004-02-17 10:12:01
|
Hello, First I'd like to thank for a very interesting project! Keep good working! I've tried it for some days and it look very usefull. Now to my question: I have a problem to run KDE environment. I've installed Cygwin X and permit host 192.168.0.40 (xhost +192.168.0.40) which is colinux virtual machine on my Windows XP box. On colinux machine I've installed KDE (apt-get install kde), set DISPLAY (export DISPLAY="192.168.0.1:0") and tried to start kde (startkde). Starting KDE screen have appeared, but it has taken a VERY long time before KDE really started. There were also dialog boxes with messages like "Sound server fatal error: cpu overload, aborting" and "device /dev/dsp can't be opened" (the second is usual, when I don't have a rigth module in kernel for my sound card, I know, but I don't know yet, what to do with this in colinux). Am I doing anything wrong? Should I kill (someway) arts daemon (or disable it, while starting KDE)? Thank in advance for any help. Sorry for poor english. Fastek |
|
From: Nir P. <ni...@em...> - 2004-02-17 10:04:11
|
Hi y'all, After installing a regular distribution on coLinux, here are the few things that were in the way, and could be improved in the future (note, the full report was posted here yesterday): *** fdisk won't work fdisk can't get and/or modify a partition table. Since we don't really have a real disk, we don't have a partition table fdisk can use. I think this will cause the installer of most distributions to fail. Not sure yet how coLinux can be extended to support this... *** /proc/partitions is empty Probably caused by the same point of lack-of-support as the previous item (fdisk). The installer tries to check which partitions of type "Linux" (83) are available for installation. Normally, such a partition is created by the "fdisk" stage. *** ISO unsupported As noted before, we can't boot from CD. This is annoying, as we have to copy the content to a disk image, and boot it using some sort of a "root-disk" (floppy installer, etc.). Being able to boot from CD is a must if we want coLinux to support installation CDs as they are without modification. *** /dev/cobd0 is not supported as an installation target It is possible that most installers would agree to install on /dev/hdXX or /dev/sdXX (or similar), but would not agree to use /dev/cobdX. Can't really blame them as it is not a standard device name. I'm not sure what is the best way to solve this, but maybe if we could fake a "/dev/hda1" it would be easiest. *** Unavailable kernel modules Most installations come with a kernel+modules of its own. Now we use a different kernel, so the distribution can't use its own modules. Usually it will just give some errors that we can ignore, but maybe we can put the coLinux compiled modules on the installed system after installation. *** coLinux console The console needs some improvement to make installation easier. While testing it, I saw that the text dialogs are not painted fully (where it is just plain color, you could see the older text), and the direction keys didn't work (left, right,...). Should be an easy one. Note that it is not a very big problem - you can install with it, but it is visually messy. Btw, having a frame-buffer support for the console (maybe vesa compatible) could be great - for graphic installers, but that would be too much work. Nir |
|
From: Ian L. <Ian...@mq...> - 2004-02-17 08:48:09
|
> > > >parameters in the default xml file such that "init=/bin/sh". > > > > > > > I tried that. It didn't work. It just went ahead and ran init anyway > > > and booted up all the way. > > > > If this is the case then you may have the wrong version of coLinux -- > > Dan said that he was going to fix that up -- I dunno if he did (hadn't > > retested that yet). > > I did implement it, but somehow it takes only the first paramter. Will > be fixed for the next version. Thanks for letting me know .. -- Ian Latter Internet and Networking Security Officer Macquarie University Meet me at the Australian Unix and open systems User Group (AUUG) Security Symposium; 2004 http://www.auug.org.au/events/2004/security/ |
|
From: Jason A. P. <pat...@pc...> - 2004-02-16 22:02:40
|
It seems that no matter what I do, I can't get "heavy" apps to work properly. I've tried under both Cygwin's X server running in -multiwindow and not, along with vncserver with the TightVNC viewer on Win2K to view the desktop. Examples of "heavy" apps are kmail (running the Kroupware extensions) and xchat. These are the only two I've tested so far that I really need working. When connecting to cygwin X, the apps end up just crashing the X server and XWin.exe dumps core and reports an Exception: STATUS_ACCESS_VIOLATION error message. I did some Google'ing but didn't find a solution. I was pointed to running the startxwin.bat script instead of just launching XWin.exe, but that didn't work either. When using the VNC server/client to access the apps, I couldn't get a full instance of KDE desktop up and running in order to launch kmail. It would stop at different times, but usually leaving the splash screen up and not getting to the full desktop (although it made it there once, but then kandalf's tips were hung on the screen and I couldn't close the app). I switched to using icewm, and that came up completely and was going to let me launch apps. So, I attempted to start konsole, which got all the way to bringing up the window and the menus but not a prompt. The block cursor just stayed in the top left of the window, but no prompt showed up. I couldn't even close the window or interact with it after that. Even killing it from the console didn't remove it from the screen. The disconcerting thing, though, is that the VNC viewer will just lock up and stop responding. I click the 'X' to close it and a dialog pops up from Windows telling me that this program is not responding, do you want to end it now. I've noticed some of these kinds of issues before with exporting X apps from other Linux servers on the network to cygwin's X server under Windows. However, the cygwin compiled versions of KDE apps/desktop seem to work fine (albeit, very slowly). Don't know where to go from here. My goal was to get the Kolab groupware server installed and running (which I was successful at doing and that seems to be working) and also the KDE PIM apps that have the modifications to work with the Kolab server. It seems the KDE PIM apps may have problems interfacing with X/VNC or something. But then, why would xchat crash cygwin X, too? Thanks for any help (and for the previous help; I was able to get back into the filesystem after the updates that fixed the bootparams bug). -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. |
|
From: Dan A. <da...@gm...> - 2004-02-16 19:07:40
|
On Mon, Feb 16, 2004 at 12:08:14PM -0000, Thomas Fritzsche wrote: > I tested the current "Valentine release" + cobd.c patch. I wrote that I > get the time from the host system (only one hour diffenrence because I > didn't have setup the timezone). What I'm wondering is the fact that I > have not the same date. On colinux I have 12. Feb 2004 in Windows I have > 16. Feb. 2004 and I could not explain this 4 days by not setting the > timezone. The problem resides in the conversion between Windows' KeQuerySystemTime and the UNIX time returned to Linux. It returns the number of seconds since January 1, 1601 (should look at the history books to find out why Microsoft picked up this date). When calculating the difference I forgot to subtract the extra days of the 3 non existing leap years of 1700, 1800, and 1900. The last day is an off-by-one :). Fixed in the next release. -- Dan Aloni da...@gm... |
|
From: Benoit M. <ben...@cg...> - 2004-02-16 16:06:35
|
ok thx ----- Original Message ----- From: "Regis NEBOR" <re...@ho...> To: "Benoit MICHEL" <bem...@ca...>; <col...@li...> Sent: Monday, February 16, 2004 4:55 PM Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > Do a little search in regedit, you'll prolly find the name of each current > devices of your config > > Regis > ----- Original Message ----- > From: "Benoit MICHEL" <ben...@cg...> > To: <col...@li...> > Sent: Monday, February 16, 2004 7:43 AM > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > this is logic ;-) > > Does windows name scsi drives like this?? > > for ex, two IDE disks and one scsi one, will windows name the scsi drive > > \\Device\harddisk3\VolumeX ? > > and, what about cdrom drives? \\Device\cdromX ? is that right? > > thx > > Benoit > > > > ----- Original Message ----- > > From: "Richard Goodwin" <ric...@ri...> > > To: <col...@li...> > > Sent: Monday, February 16, 2004 4:30 PM > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > Well you must also ask yourself "how many hard drives, and how many > > > partitions on each?" If you have only one hard drive, and the target > > > partition is the 4th one on there, then of course you need to modify the > > > device name :-) > > > > > > ----- Original Message ----- > > > From: "Benoit MICHEL" <ben...@cg...> > > > To: <col...@li...> > > > Sent: Monday, February 16, 2004 9:03 AM > > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > ok thx, it runs now > > > > > > > > I'm trying to boot using debian file as cobd0 and > > > \\Device\harddisk2\Volume2 > > > > as cobd1 (this is just a partition without any fs on it, want to > format > > it > > > > with mkfs.ext3 to begin my own install ;) ) > > > > but anytime, it returns can't open device...... > > > > I gonna look further tonight, till i'm at work now ;) > > > > Benoit > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > From: "Richard Goodwin" <ric...@ri...> > > > > To: <col...@li...> > > > > Sent: Monday, February 16, 2004 3:35 PM > > > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > \\Device\harddisk2\Volume2 is Window's internal object name for that > > > > > partition. If it is set at Index 0 in the XML file, then it becomes > > > > > presented by the Linux kernel as cobd0 once inside the partition. > Thus > > > > some > > > > > manual hacking may be required (fstab, etc) I believe to make your > > > > existing > > > > > Linux partition boot properly. (cobd0 = coLinux block device 0 > IIRC) > > > > > > > > > > By the way, my in-laws are named Benoit :-) > > > > > > > > > > ----- Original Message ----- > > > > > From: "Benoit MICHEL" <ben...@cg...> > > > > > To: <col...@li...> > > > > > Sent: Monday, February 16, 2004 7:53 AM > > > > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > > > hi > > > > > > > > > > > > what about /dev/hdc2 ?? > > > > > > \Device\Harddisk2\Volume2? > > > > > > i'm not able to fully boot with others devices declared as enabled > > in > > > > the > > > > > > config file. > > > > > > seems to freeze on co-net > > > > > > Benoit > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "Regis NEBOR" <re...@ho...> > > > > > > To: <col...@li...> > > > > > > Sent: Monday, February 16, 2004 1:48 PM > > > > > > Subject: Fw: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > From: "Regis NEBOR" <re...@ho...> > > > > > > > To: "Chakat Sandwalker" <san...@e3...> > > > > > > > Sent: Monday, February 16, 2004 2:43 AM > > > > > > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > > > > > > > > > Hi > > > > > > > > > > > > > > > > This config file allowed me to boot on my /dev/hda2 : > > > > > > > > > > > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > > > > > > <colinux> > > > > > > > > <block_device index="0" path="\Device\HarddiskVolume2" > > > > > > enabled="true"> > > > > > > > > </block_device> > > > > > > > > <bootparams>root=/dev/cobd0</bootparams> > > > > > > > > <image path="vmlinux"></image> > > > > > > > > </colinux> > > > > > > > > > > > > > > > > But the kernel will remain colinux's one. You'll have to > change > > > some > > > > > > > setting > > > > > > > > in the previous setup too. > > > > > > > > I would say getting an image made with colinux in mind is > easier > > > at > > > > > the > > > > > > > > moment. > > > > > > > > > > > > > > > > Regis > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > From: "Chakat Sandwalker" <san...@e3...> > > > > > > > > To: <col...@li...> > > > > > > > > Sent: Monday, February 16, 2004 1:56 AM > > > > > > > > Subject: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > > > > > > > > > > > > I was told that I could save myself an 18MB download (and a > > gig > > > of > > > > > > space > > > > > > > > > on a small C:) by using my installation of Mandrake 9.1 > > instead. > > > > > > > > > However, I can't figure out how to edit the XML file to > point > > to > > > > the > > > > > > > > > Linux partitions in order for it to boot. I'm running a > dual > > > boot > > > > > > > > > system (XP and Mandrake), and I don't know too much about > > Linux > > > to > > > > > go > > > > > > > > > mucking about with it. Can anyone help? > > > > > > > > > > > > > > > > > > Sandy > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > > > > > Build and deploy apps & Web services for Linux with > > > > > > > > > a free DVD software kit from IBM. Click Now! > > > > > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > > > > > _______________________________________________ > > > > > > > > > coLinux-devel mailing list > > > > > > > > > coL...@li... > > > > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > > > Build and deploy apps & Web services for Linux with > > > > > > > a free DVD software kit from IBM. Click Now! > > > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > > > _______________________________________________ > > > > > > > coLinux-devel mailing list > > > > > > > coL...@li... > > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > > Build and deploy apps & Web services for Linux with > > > > > > a free DVD software kit from IBM. Click Now! > > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > > _______________________________________________ > > > > > > coLinux-devel mailing list > > > > > > coL...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > Build and deploy apps & Web services for Linux with > > > > > a free DVD software kit from IBM. Click Now! > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > _______________________________________________ > > > > > coLinux-devel mailing list > > > > > coL...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > Build and deploy apps & Web services for Linux with > > > > a free DVD software kit from IBM. Click Now! > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > _______________________________________________ > > > > coLinux-devel mailing list > > > > coL...@li... > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > Build and deploy apps & Web services for Linux with > > > a free DVD software kit from IBM. Click Now! > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > _______________________________________________ > > > coLinux-devel mailing list > > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > ------------------------------------------------------- > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > Build and deploy apps & Web services for Linux with > > a free DVD software kit from IBM. Click Now! > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > _______________________________________________ > > coLinux-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > |
|
From: Regis N. <re...@ho...> - 2004-02-16 15:58:55
|
Do a little search in regedit, you'll prolly find the name of each current devices of your config Regis ----- Original Message ----- From: "Benoit MICHEL" <ben...@cg...> To: <col...@li...> Sent: Monday, February 16, 2004 7:43 AM Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > this is logic ;-) > Does windows name scsi drives like this?? > for ex, two IDE disks and one scsi one, will windows name the scsi drive > \\Device\harddisk3\VolumeX ? > and, what about cdrom drives? \\Device\cdromX ? is that right? > thx > Benoit > > ----- Original Message ----- > From: "Richard Goodwin" <ric...@ri...> > To: <col...@li...> > Sent: Monday, February 16, 2004 4:30 PM > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > Well you must also ask yourself "how many hard drives, and how many > > partitions on each?" If you have only one hard drive, and the target > > partition is the 4th one on there, then of course you need to modify the > > device name :-) > > > > ----- Original Message ----- > > From: "Benoit MICHEL" <ben...@cg...> > > To: <col...@li...> > > Sent: Monday, February 16, 2004 9:03 AM > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > ok thx, it runs now > > > > > > I'm trying to boot using debian file as cobd0 and > > \\Device\harddisk2\Volume2 > > > as cobd1 (this is just a partition without any fs on it, want to format > it > > > with mkfs.ext3 to begin my own install ;) ) > > > but anytime, it returns can't open device...... > > > I gonna look further tonight, till i'm at work now ;) > > > Benoit > > > > > > > > > > > > > > > ----- Original Message ----- > > > From: "Richard Goodwin" <ric...@ri...> > > > To: <col...@li...> > > > Sent: Monday, February 16, 2004 3:35 PM > > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > \\Device\harddisk2\Volume2 is Window's internal object name for that > > > > partition. If it is set at Index 0 in the XML file, then it becomes > > > > presented by the Linux kernel as cobd0 once inside the partition. Thus > > > some > > > > manual hacking may be required (fstab, etc) I believe to make your > > > existing > > > > Linux partition boot properly. (cobd0 = coLinux block device 0 IIRC) > > > > > > > > By the way, my in-laws are named Benoit :-) > > > > > > > > ----- Original Message ----- > > > > From: "Benoit MICHEL" <ben...@cg...> > > > > To: <col...@li...> > > > > Sent: Monday, February 16, 2004 7:53 AM > > > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > hi > > > > > > > > > > what about /dev/hdc2 ?? > > > > > \Device\Harddisk2\Volume2? > > > > > i'm not able to fully boot with others devices declared as enabled > in > > > the > > > > > config file. > > > > > seems to freeze on co-net > > > > > Benoit > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > From: "Regis NEBOR" <re...@ho...> > > > > > To: <col...@li...> > > > > > Sent: Monday, February 16, 2004 1:48 PM > > > > > Subject: Fw: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "Regis NEBOR" <re...@ho...> > > > > > > To: "Chakat Sandwalker" <san...@e3...> > > > > > > Sent: Monday, February 16, 2004 2:43 AM > > > > > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > > > > > > Hi > > > > > > > > > > > > > > This config file allowed me to boot on my /dev/hda2 : > > > > > > > > > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > > > > > <colinux> > > > > > > > <block_device index="0" path="\Device\HarddiskVolume2" > > > > > enabled="true"> > > > > > > > </block_device> > > > > > > > <bootparams>root=/dev/cobd0</bootparams> > > > > > > > <image path="vmlinux"></image> > > > > > > > </colinux> > > > > > > > > > > > > > > But the kernel will remain colinux's one. You'll have to change > > some > > > > > > setting > > > > > > > in the previous setup too. > > > > > > > I would say getting an image made with colinux in mind is easier > > at > > > > the > > > > > > > moment. > > > > > > > > > > > > > > Regis > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > From: "Chakat Sandwalker" <san...@e3...> > > > > > > > To: <col...@li...> > > > > > > > Sent: Monday, February 16, 2004 1:56 AM > > > > > > > Subject: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > > > > > > > > > I was told that I could save myself an 18MB download (and a > gig > > of > > > > > space > > > > > > > > on a small C:) by using my installation of Mandrake 9.1 > instead. > > > > > > > > However, I can't figure out how to edit the XML file to point > to > > > the > > > > > > > > Linux partitions in order for it to boot. I'm running a dual > > boot > > > > > > > > system (XP and Mandrake), and I don't know too much about > Linux > > to > > > > go > > > > > > > > mucking about with it. Can anyone help? > > > > > > > > > > > > > > > > Sandy > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > > > > Build and deploy apps & Web services for Linux with > > > > > > > > a free DVD software kit from IBM. Click Now! > > > > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > > > > _______________________________________________ > > > > > > > > coLinux-devel mailing list > > > > > > > > coL...@li... > > > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > > Build and deploy apps & Web services for Linux with > > > > > > a free DVD software kit from IBM. Click Now! > > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > > _______________________________________________ > > > > > > coLinux-devel mailing list > > > > > > coL...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > Build and deploy apps & Web services for Linux with > > > > > a free DVD software kit from IBM. Click Now! > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > _______________________________________________ > > > > > coLinux-devel mailing list > > > > > coL...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > Build and deploy apps & Web services for Linux with > > > > a free DVD software kit from IBM. Click Now! > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > _______________________________________________ > > > > coLinux-devel mailing list > > > > coL...@li... > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > ------------------------------------------------------- > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > Build and deploy apps & Web services for Linux with > > > a free DVD software kit from IBM. Click Now! > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > _______________________________________________ > > > coLinux-devel mailing list > > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > ------------------------------------------------------- > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > Build and deploy apps & Web services for Linux with > > a free DVD software kit from IBM. Click Now! > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > _______________________________________________ > > coLinux-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
|
From: Benoit M. <ben...@cg...> - 2004-02-16 15:48:59
|
this is logic ;-) Does windows name scsi drives like this?? for ex, two IDE disks and one scsi one, will windows name the scsi drive \\Device\harddisk3\VolumeX ? and, what about cdrom drives? \\Device\cdromX ? is that right? thx Benoit ----- Original Message ----- From: "Richard Goodwin" <ric...@ri...> To: <col...@li...> Sent: Monday, February 16, 2004 4:30 PM Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > Well you must also ask yourself "how many hard drives, and how many > partitions on each?" If you have only one hard drive, and the target > partition is the 4th one on there, then of course you need to modify the > device name :-) > > ----- Original Message ----- > From: "Benoit MICHEL" <ben...@cg...> > To: <col...@li...> > Sent: Monday, February 16, 2004 9:03 AM > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > ok thx, it runs now > > > > I'm trying to boot using debian file as cobd0 and > \\Device\harddisk2\Volume2 > > as cobd1 (this is just a partition without any fs on it, want to format it > > with mkfs.ext3 to begin my own install ;) ) > > but anytime, it returns can't open device...... > > I gonna look further tonight, till i'm at work now ;) > > Benoit > > > > > > > > > > ----- Original Message ----- > > From: "Richard Goodwin" <ric...@ri...> > > To: <col...@li...> > > Sent: Monday, February 16, 2004 3:35 PM > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > \\Device\harddisk2\Volume2 is Window's internal object name for that > > > partition. If it is set at Index 0 in the XML file, then it becomes > > > presented by the Linux kernel as cobd0 once inside the partition. Thus > > some > > > manual hacking may be required (fstab, etc) I believe to make your > > existing > > > Linux partition boot properly. (cobd0 = coLinux block device 0 IIRC) > > > > > > By the way, my in-laws are named Benoit :-) > > > > > > ----- Original Message ----- > > > From: "Benoit MICHEL" <ben...@cg...> > > > To: <col...@li...> > > > Sent: Monday, February 16, 2004 7:53 AM > > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > hi > > > > > > > > what about /dev/hdc2 ?? > > > > \Device\Harddisk2\Volume2? > > > > i'm not able to fully boot with others devices declared as enabled in > > the > > > > config file. > > > > seems to freeze on co-net > > > > Benoit > > > > > > > > > > > > ----- Original Message ----- > > > > From: "Regis NEBOR" <re...@ho...> > > > > To: <col...@li...> > > > > Sent: Monday, February 16, 2004 1:48 PM > > > > Subject: Fw: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > From: "Regis NEBOR" <re...@ho...> > > > > > To: "Chakat Sandwalker" <san...@e3...> > > > > > Sent: Monday, February 16, 2004 2:43 AM > > > > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > > > Hi > > > > > > > > > > > > This config file allowed me to boot on my /dev/hda2 : > > > > > > > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > > > > <colinux> > > > > > > <block_device index="0" path="\Device\HarddiskVolume2" > > > > enabled="true"> > > > > > > </block_device> > > > > > > <bootparams>root=/dev/cobd0</bootparams> > > > > > > <image path="vmlinux"></image> > > > > > > </colinux> > > > > > > > > > > > > But the kernel will remain colinux's one. You'll have to change > some > > > > > setting > > > > > > in the previous setup too. > > > > > > I would say getting an image made with colinux in mind is easier > at > > > the > > > > > > moment. > > > > > > > > > > > > Regis > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "Chakat Sandwalker" <san...@e3...> > > > > > > To: <col...@li...> > > > > > > Sent: Monday, February 16, 2004 1:56 AM > > > > > > Subject: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > > > > > > I was told that I could save myself an 18MB download (and a gig > of > > > > space > > > > > > > on a small C:) by using my installation of Mandrake 9.1 instead. > > > > > > > However, I can't figure out how to edit the XML file to point to > > the > > > > > > > Linux partitions in order for it to boot. I'm running a dual > boot > > > > > > > system (XP and Mandrake), and I don't know too much about Linux > to > > > go > > > > > > > mucking about with it. Can anyone help? > > > > > > > > > > > > > > Sandy > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > > > Build and deploy apps & Web services for Linux with > > > > > > > a free DVD software kit from IBM. Click Now! > > > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > > > _______________________________________________ > > > > > > > coLinux-devel mailing list > > > > > > > coL...@li... > > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > Build and deploy apps & Web services for Linux with > > > > > a free DVD software kit from IBM. Click Now! > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > _______________________________________________ > > > > > coLinux-devel mailing list > > > > > coL...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > Build and deploy apps & Web services for Linux with > > > > a free DVD software kit from IBM. Click Now! > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > _______________________________________________ > > > > coLinux-devel mailing list > > > > coL...@li... > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > Build and deploy apps & Web services for Linux with > > > a free DVD software kit from IBM. Click Now! > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > _______________________________________________ > > > coLinux-devel mailing list > > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > ------------------------------------------------------- > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > Build and deploy apps & Web services for Linux with > > a free DVD software kit from IBM. Click Now! > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > _______________________________________________ > > coLinux-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel |
|
From: Nir P. <ni...@em...> - 2004-02-16 15:45:37
|
Hi y'all, Here's how I installed slackware on coLinux. After you read it all (sorry - it is long), you may apply the same tricks to other distributions. For now it is just the installation notes - tomorrow I hope to post again with detailed files/patches/etc., after I compare some things to my real native slackware (I don't have it near me). Also, to do the required little tweaks, you'll probably need a Linux box. I used coLinux itself with the 1GB debian image available for download (as I was far from my box). And to the process itself: *** Copying ISO to hard-disk As noted before, you can't just boot the CD. I just copied the entire CD to the hard-disk. You can do it many ways. I guess best one is to "wget" it from one of the slackware mirrors. *** Extract the rootdisk I took the rootdisk from slackware: rootdisk/install.1 is a gzipped ext2 filesystem. "gzip -cd" it to some image file, then loop-mount it somewhere. rootdisk/install.2 is a gzipped tar file. go to the root of the previous loop mounted image, and "tar zvxf" it. We will now tweak the root image a little, and later pack it back. *** Add the /dev/cobdX nodes I used 3 images to install (3 for: where the CD content was, the target disk, and the installation root disk), so I created 3 nodes: mknod /dev/cobd0 b 117 0 mknod /dev/cobd1 b 117 1 mknod /dev/cobd2 b 117 2 *** Patch the setup script A while ago I posted here about installing linux from normal CDs. I commented that you would probably need to change some scripts... well, here's an example of one... Slackware installer is trying to guess which partitions you have. It uses "/proc/partitions". coLinux doesn't list anything there (maybe we should add some dummies to allow easier installations in the future...). The installer builds a list of partitions available for installations. In that place of the setup script I commented out the "probe -l ...", and put explicitly "/dev/cobd0" into "$TMP/SeTplist". I will probably post tomorrow a real patch here (I need to compare that to a native installation). *** Start coLinux with the 3 image files After unmounting the root image (where we changed the setup script), I changed the coLinux XML config file to include 3 image files: cobd0) The target to be installed (you can just use a copy of the 1gb debian image for this one - just "format" it in the installer) cobd1) Here you should have the copy of the installation CD - you'll need it for the packages cobd2) This is the modified installer root image <== this should be the root (we'd like to boot this one) Now you can just install whatever packages you'd like. Slackware's simplicity helps here - for other distributions you might need more tweaking... console notes: the installer looks bad in the colinux console. also the arrows didn't really work so I used "+" and "-" to move up and down in the lists. Now you have your own slackware. To use it, you just have to change the root in the XML config to be /dev/cobd0 (you can remove the extra two disk images now). Once running, you will get some errors - First, slackware is not too happy the filesystem is already mounted read/write. It should be mounted read-only at first, so "fsck" can check it. Just hitting ENTER here would get you pass this one for now (I haven't tried yet to make coLinux mount the root read-only). Then of course, it can't open dependencies file (modules.dep) - well, we did just take the kernel without any module... Other than that, I got myself a working slackware, network capable out of the box. I installed large amount of the packages, so I can't really post this ~800MB image file anywhere... I do plan on uploading the modified root-image and config file required... stay tuned. Well, that was long. And one might ask - "what does this help me? I don't want slackware...". Sorry, I use slackware, so that's what I can test. But the basic idea should be the same for other distributions - you'll have to make a root-disk. Any installation that's easy to install from floppies, should be easy to support with this procedure. All we need at the end are the root-disks. P.S. I didn't spend much time editing the text here, so forgive me if I made some mistakes... Nir |
|
From: Richard G. <ric...@ri...> - 2004-02-16 15:36:55
|
Well you must also ask yourself "how many hard drives, and how many partitions on each?" If you have only one hard drive, and the target partition is the 4th one on there, then of course you need to modify the device name :-) ----- Original Message ----- From: "Benoit MICHEL" <ben...@cg...> To: <col...@li...> Sent: Monday, February 16, 2004 9:03 AM Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > ok thx, it runs now > > I'm trying to boot using debian file as cobd0 and \\Device\harddisk2\Volume2 > as cobd1 (this is just a partition without any fs on it, want to format it > with mkfs.ext3 to begin my own install ;) ) > but anytime, it returns can't open device...... > I gonna look further tonight, till i'm at work now ;) > Benoit > > > > > ----- Original Message ----- > From: "Richard Goodwin" <ric...@ri...> > To: <col...@li...> > Sent: Monday, February 16, 2004 3:35 PM > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > \\Device\harddisk2\Volume2 is Window's internal object name for that > > partition. If it is set at Index 0 in the XML file, then it becomes > > presented by the Linux kernel as cobd0 once inside the partition. Thus > some > > manual hacking may be required (fstab, etc) I believe to make your > existing > > Linux partition boot properly. (cobd0 = coLinux block device 0 IIRC) > > > > By the way, my in-laws are named Benoit :-) > > > > ----- Original Message ----- > > From: "Benoit MICHEL" <ben...@cg...> > > To: <col...@li...> > > Sent: Monday, February 16, 2004 7:53 AM > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > hi > > > > > > what about /dev/hdc2 ?? > > > \Device\Harddisk2\Volume2? > > > i'm not able to fully boot with others devices declared as enabled in > the > > > config file. > > > seems to freeze on co-net > > > Benoit > > > > > > > > > ----- Original Message ----- > > > From: "Regis NEBOR" <re...@ho...> > > > To: <col...@li...> > > > Sent: Monday, February 16, 2004 1:48 PM > > > Subject: Fw: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > ----- Original Message ----- > > > > From: "Regis NEBOR" <re...@ho...> > > > > To: "Chakat Sandwalker" <san...@e3...> > > > > Sent: Monday, February 16, 2004 2:43 AM > > > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > Hi > > > > > > > > > > This config file allowed me to boot on my /dev/hda2 : > > > > > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > > > <colinux> > > > > > <block_device index="0" path="\Device\HarddiskVolume2" > > > enabled="true"> > > > > > </block_device> > > > > > <bootparams>root=/dev/cobd0</bootparams> > > > > > <image path="vmlinux"></image> > > > > > </colinux> > > > > > > > > > > But the kernel will remain colinux's one. You'll have to change some > > > > setting > > > > > in the previous setup too. > > > > > I would say getting an image made with colinux in mind is easier at > > the > > > > > moment. > > > > > > > > > > Regis > > > > > > > > > > ----- Original Message ----- > > > > > From: "Chakat Sandwalker" <san...@e3...> > > > > > To: <col...@li...> > > > > > Sent: Monday, February 16, 2004 1:56 AM > > > > > Subject: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > > > > I was told that I could save myself an 18MB download (and a gig of > > > space > > > > > > on a small C:) by using my installation of Mandrake 9.1 instead. > > > > > > However, I can't figure out how to edit the XML file to point to > the > > > > > > Linux partitions in order for it to boot. I'm running a dual boot > > > > > > system (XP and Mandrake), and I don't know too much about Linux to > > go > > > > > > mucking about with it. Can anyone help? > > > > > > > > > > > > Sandy > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > > Build and deploy apps & Web services for Linux with > > > > > > a free DVD software kit from IBM. Click Now! > > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > > _______________________________________________ > > > > > > coLinux-devel mailing list > > > > > > coL...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > Build and deploy apps & Web services for Linux with > > > > a free DVD software kit from IBM. Click Now! > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > _______________________________________________ > > > > coLinux-devel mailing list > > > > coL...@li... > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > ------------------------------------------------------- > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > Build and deploy apps & Web services for Linux with > > > a free DVD software kit from IBM. Click Now! > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > _______________________________________________ > > > coLinux-devel mailing list > > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > ------------------------------------------------------- > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > Build and deploy apps & Web services for Linux with > > a free DVD software kit from IBM. Click Now! > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > _______________________________________________ > > coLinux-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > |
|
From: Benoit M. <ben...@cg...> - 2004-02-16 15:08:44
|
ok thx, it runs now I'm trying to boot using debian file as cobd0 and \\Device\harddisk2\Volume2 as cobd1 (this is just a partition without any fs on it, want to format it with mkfs.ext3 to begin my own install ;) ) but anytime, it returns can't open device...... I gonna look further tonight, till i'm at work now ;) Benoit ----- Original Message ----- From: "Richard Goodwin" <ric...@ri...> To: <col...@li...> Sent: Monday, February 16, 2004 3:35 PM Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > \\Device\harddisk2\Volume2 is Window's internal object name for that > partition. If it is set at Index 0 in the XML file, then it becomes > presented by the Linux kernel as cobd0 once inside the partition. Thus some > manual hacking may be required (fstab, etc) I believe to make your existing > Linux partition boot properly. (cobd0 = coLinux block device 0 IIRC) > > By the way, my in-laws are named Benoit :-) > > ----- Original Message ----- > From: "Benoit MICHEL" <ben...@cg...> > To: <col...@li...> > Sent: Monday, February 16, 2004 7:53 AM > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > hi > > > > what about /dev/hdc2 ?? > > \Device\Harddisk2\Volume2? > > i'm not able to fully boot with others devices declared as enabled in the > > config file. > > seems to freeze on co-net > > Benoit > > > > > > ----- Original Message ----- > > From: "Regis NEBOR" <re...@ho...> > > To: <col...@li...> > > Sent: Monday, February 16, 2004 1:48 PM > > Subject: Fw: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > ----- Original Message ----- > > > From: "Regis NEBOR" <re...@ho...> > > > To: "Chakat Sandwalker" <san...@e3...> > > > Sent: Monday, February 16, 2004 2:43 AM > > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > Hi > > > > > > > > This config file allowed me to boot on my /dev/hda2 : > > > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > > <colinux> > > > > <block_device index="0" path="\Device\HarddiskVolume2" > > enabled="true"> > > > > </block_device> > > > > <bootparams>root=/dev/cobd0</bootparams> > > > > <image path="vmlinux"></image> > > > > </colinux> > > > > > > > > But the kernel will remain colinux's one. You'll have to change some > > > setting > > > > in the previous setup too. > > > > I would say getting an image made with colinux in mind is easier at > the > > > > moment. > > > > > > > > Regis > > > > > > > > ----- Original Message ----- > > > > From: "Chakat Sandwalker" <san...@e3...> > > > > To: <col...@li...> > > > > Sent: Monday, February 16, 2004 1:56 AM > > > > Subject: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > > > > I was told that I could save myself an 18MB download (and a gig of > > space > > > > > on a small C:) by using my installation of Mandrake 9.1 instead. > > > > > However, I can't figure out how to edit the XML file to point to the > > > > > Linux partitions in order for it to boot. I'm running a dual boot > > > > > system (XP and Mandrake), and I don't know too much about Linux to > go > > > > > mucking about with it. Can anyone help? > > > > > > > > > > Sandy > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > Build and deploy apps & Web services for Linux with > > > > > a free DVD software kit from IBM. Click Now! > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > _______________________________________________ > > > > > coLinux-devel mailing list > > > > > coL...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > Build and deploy apps & Web services for Linux with > > > a free DVD software kit from IBM. Click Now! > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > _______________________________________________ > > > coLinux-devel mailing list > > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > ------------------------------------------------------- > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > Build and deploy apps & Web services for Linux with > > a free DVD software kit from IBM. Click Now! > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > _______________________________________________ > > coLinux-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel |
|
From: Richard G. <ric...@ri...> - 2004-02-16 14:42:07
|
\\Device\harddisk2\Volume2 is Window's internal object name for that partition. If it is set at Index 0 in the XML file, then it becomes presented by the Linux kernel as cobd0 once inside the partition. Thus some manual hacking may be required (fstab, etc) I believe to make your existing Linux partition boot properly. (cobd0 = coLinux block device 0 IIRC) By the way, my in-laws are named Benoit :-) ----- Original Message ----- From: "Benoit MICHEL" <ben...@cg...> To: <col...@li...> Sent: Monday, February 16, 2004 7:53 AM Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > hi > > what about /dev/hdc2 ?? > \Device\Harddisk2\Volume2? > i'm not able to fully boot with others devices declared as enabled in the > config file. > seems to freeze on co-net > Benoit > > > ----- Original Message ----- > From: "Regis NEBOR" <re...@ho...> > To: <col...@li...> > Sent: Monday, February 16, 2004 1:48 PM > Subject: Fw: [coLinux-devel] Utilising pre-installed Linux... > > > > > > ----- Original Message ----- > > From: "Regis NEBOR" <re...@ho...> > > To: "Chakat Sandwalker" <san...@e3...> > > Sent: Monday, February 16, 2004 2:43 AM > > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > Hi > > > > > > This config file allowed me to boot on my /dev/hda2 : > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > > <colinux> > > > <block_device index="0" path="\Device\HarddiskVolume2" > enabled="true"> > > > </block_device> > > > <bootparams>root=/dev/cobd0</bootparams> > > > <image path="vmlinux"></image> > > > </colinux> > > > > > > But the kernel will remain colinux's one. You'll have to change some > > setting > > > in the previous setup too. > > > I would say getting an image made with colinux in mind is easier at the > > > moment. > > > > > > Regis > > > > > > ----- Original Message ----- > > > From: "Chakat Sandwalker" <san...@e3...> > > > To: <col...@li...> > > > Sent: Monday, February 16, 2004 1:56 AM > > > Subject: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > > > > I was told that I could save myself an 18MB download (and a gig of > space > > > > on a small C:) by using my installation of Mandrake 9.1 instead. > > > > However, I can't figure out how to edit the XML file to point to the > > > > Linux partitions in order for it to boot. I'm running a dual boot > > > > system (XP and Mandrake), and I don't know too much about Linux to go > > > > mucking about with it. Can anyone help? > > > > > > > > Sandy > > > > > > > > > > > > ------------------------------------------------------- > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > Build and deploy apps & Web services for Linux with > > > > a free DVD software kit from IBM. Click Now! > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > _______________________________________________ > > > > coLinux-devel mailing list > > > > coL...@li... > > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > > > > > > ------------------------------------------------------- > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > Build and deploy apps & Web services for Linux with > > a free DVD software kit from IBM. Click Now! > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > _______________________________________________ > > coLinux-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > |
|
From: Benoit M. <ben...@cg...> - 2004-02-16 13:58:05
|
hi what about /dev/hdc2 ?? \Device\Harddisk2\Volume2? i'm not able to fully boot with others devices declared as enabled in the config file. seems to freeze on co-net Benoit ----- Original Message ----- From: "Regis NEBOR" <re...@ho...> To: <col...@li...> Sent: Monday, February 16, 2004 1:48 PM Subject: Fw: [coLinux-devel] Utilising pre-installed Linux... > > ----- Original Message ----- > From: "Regis NEBOR" <re...@ho...> > To: "Chakat Sandwalker" <san...@e3...> > Sent: Monday, February 16, 2004 2:43 AM > Subject: Re: [coLinux-devel] Utilising pre-installed Linux... > > > > Hi > > > > This config file allowed me to boot on my /dev/hda2 : > > > > <?xml version="1.0" encoding="UTF-8"?> > > <colinux> > > <block_device index="0" path="\Device\HarddiskVolume2" enabled="true"> > > </block_device> > > <bootparams>root=/dev/cobd0</bootparams> > > <image path="vmlinux"></image> > > </colinux> > > > > But the kernel will remain colinux's one. You'll have to change some > setting > > in the previous setup too. > > I would say getting an image made with colinux in mind is easier at the > > moment. > > > > Regis > > > > ----- Original Message ----- > > From: "Chakat Sandwalker" <san...@e3...> > > To: <col...@li...> > > Sent: Monday, February 16, 2004 1:56 AM > > Subject: [coLinux-devel] Utilising pre-installed Linux... > > > > > > > I was told that I could save myself an 18MB download (and a gig of space > > > on a small C:) by using my installation of Mandrake 9.1 instead. > > > However, I can't figure out how to edit the XML file to point to the > > > Linux partitions in order for it to boot. I'm running a dual boot > > > system (XP and Mandrake), and I don't know too much about Linux to go > > > mucking about with it. Can anyone help? > > > > > > Sandy > > > > > > > > > ------------------------------------------------------- > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > Build and deploy apps & Web services for Linux with > > > a free DVD software kit from IBM. Click Now! > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > _______________________________________________ > > > coLinux-devel mailing list > > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel |
81 messages has been excluded from this view by a project administrator.
