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: Rob M. <ro...@as...> - 2004-02-18 18:32:47
|
Installing a "normal" distribution on coLinux - "The Slackware on coLinux HOWTO"I am very impressed with the power of coLinux. Great work for a 1-month old (public) project. Has anyone attempted or succeeded in getting a recent RedHat install done through coLinux? I've read the threads started by Nir Perry about his experiences with Slackware, but I am not experienced enough with Linux administration to try to duplicate them, much less apply them to RedHat. I've had a lot of luck with the Debian starter image, but some of my programs behave very strangely (crash). The behavior looks like it could be due to incompatibilities between compiler and library versions, or they might be due to coLinux. I really can't tell, and would like to take the distribution differences out of the loop to isolate the problem. I realize that the coLinux developers have lots to do, but fortunately, the images aren't impacted by coLinux development. Is there another source of images out there? (vmware users) Is there enough interest to start a projct compiling a library of images? Or is it just easier to focus effort on getting coLinux to boot generic install CD's, and go from there? Any help would be appretiated. Rob |
From: Sugree P. <su...@hp...> - 2004-02-19 06:57:02
|
I am using coLinux with RedHat 9.0. If you want to try (49 MB): http://amata.cpe.ku.ac.th/~sugree/dload/colinux/redhat-9.0.ext3.1gb.bz2 It contains only based packages. Man is installed but no man pages for APIs at all. Anyway, you can use apt-get to install anythings you want easily. The pre-configured sources are pointing to freshrpms and dag repositories. So the first step is to modify /etc/resolv.conf and run apt-get update to get the packages list. Actually, you can build your own root image by rpm command (like me). For example: dd if=/dev/zero of=redhat-9.0.ext3.1gb bs=1024 count=1048576 mkfs.ext3 redhat-9.0.ext3.1gb mkdir root mount -o loop redhat-9.0.ext3.1gb root rpm --initdb --root=$PWD/root At this point, you can install whatever you want. All rpm commands must be added --root option. That's all and then bzip2 it. umount root bzip2 -k -9 redhat-9.0.ext3.1gb Good luck, > Installing a "normal" distribution on coLinux - "The Slackware on coLinux > HOWTO"I am very impressed with the power of coLinux. Great work for a > 1-month old (public) project. > > Has anyone attempted or succeeded in getting a recent RedHat install done > through coLinux? I've read the threads started by Nir Perry about his > experiences with Slackware, but I am not experienced enough with Linux > administration to try to duplicate them, much less apply them to RedHat. > > I've had a lot of luck with the Debian starter image, but some of my > programs behave very strangely (crash). The behavior looks like it could be > due to incompatibilities between compiler and library versions, or they > might be due to coLinux. I really can't tell, and would like to take the > distribution differences out of the loop to isolate the problem. > > I realize that the coLinux developers have lots to do, but fortunately, the > images aren't impacted by coLinux development. Is there another source of > images out there? (vmware users) Is there enough interest to start a projct > compiling a library of images? Or is it just easier to focus effort on > getting coLinux to boot generic install CD's, and go from there? > > Any help would be appretiated. > > Rob > > > > ------------------------------------------------------- > 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: Rob M. <ro...@as...> - 2004-02-19 15:31:12
|
Thanks for making that image available. It seems to work good for starters, but when I try to do an apt-get update, it downloads the release and pkglist files, and then crashes with an alloc failure while it is trying to read the package lists. I tried adding APT::Cache-Limit "8388608"; to the /etc/apt/apt.conf And I tried removing some of the servers from (to make the package list smaller) /etc/apt/sources.list Did you have this problem? Any ideas for a solution? I am running the latest binary release of coLinux. Thanks again, Rob > I am using coLinux with RedHat 9.0. If you want to try (49 MB): > > http://amata.cpe.ku.ac.th/~sugree/dload/colinux/redhat-9.0.ext3.1gb.bz2 > > It contains only based packages. Man is installed but no man pages for APIs > at all. Anyway, you can use apt-get to install anythings you want easily. > The pre-configured sources are pointing to freshrpms and dag repositories. > So the first step is to modify /etc/resolv.conf and run apt-get update to > get the packages list. > > Actually, you can build your own root image by rpm command (like me). For > example: > > dd if=/dev/zero of=redhat-9.0.ext3.1gb bs=1024 count=1048576 > mkfs.ext3 redhat-9.0.ext3.1gb > mkdir root > mount -o loop redhat-9.0.ext3.1gb root > rpm --initdb --root=$PWD/root > > At this point, you can install whatever you want. All rpm commands must be > added --root option. That's all and then bzip2 it. > > umount root > bzip2 -k -9 redhat-9.0.ext3.1gb > > Good luck, > > > > Installing a "normal" distribution on coLinux - "The Slackware on coLinux > > HOWTO"I am very impressed with the power of coLinux. Great work for a > > 1-month old (public) project. > > > > Has anyone attempted or succeeded in getting a recent RedHat install done > > through coLinux? I've read the threads started by Nir Perry about his > > experiences with Slackware, but I am not experienced enough with Linux > > administration to try to duplicate them, much less apply them to RedHat. > > > > I've had a lot of luck with the Debian starter image, but some of my > > programs behave very strangely (crash). The behavior looks like it could > be > > due to incompatibilities between compiler and library versions, or they > > might be due to coLinux. I really can't tell, and would like to take the > > distribution differences out of the loop to isolate the problem. > > > > I realize that the coLinux developers have lots to do, but fortunately, > the > > images aren't impacted by coLinux development. Is there another source of > > images out there? (vmware users) Is there enough interest to start a > projct > > compiling a library of images? Or is it just easier to focus effort on > > getting coLinux to boot generic install CD's, and go from there? > > > > Any help would be appretiated. > > > > Rob > > > > > > > > ------------------------------------------------------- > > 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: Thomas F. <tf...@no...> - 2004-02-19 16:11:32
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Rob, do use swap space? Memory is very limited in the standard configuration. There was also discussion about a apt-get bug on this list. Thomas > Thanks for making that image available. > > It seems to work good for starters, but when I try to do an apt-get > update, > it downloads the release and pkglist files, and then crashes with an alloc > failure while it is trying to read the package lists. > > I tried adding > > APT::Cache-Limit "8388608"; > > to the /etc/apt/apt.conf > > And I tried removing some of the servers from (to make the package list > smaller) > > /etc/apt/sources.list > > Did you have this problem? Any ideas for a solution? > > I am running the latest binary release of coLinux. > > Thanks again, > > Rob > > >> I am using coLinux with RedHat 9.0. If you want to try (49 MB): >> >> http://amata.cpe.ku.ac.th/~sugree/dload/colinux/redhat-9.0.ext3.1gb.bz2 >> >> It contains only based packages. Man is installed but no man pages for > APIs >> at all. Anyway, you can use apt-get to install anythings you want >> easily. >> The pre-configured sources are pointing to freshrpms and dag >> repositories. >> So the first step is to modify /etc/resolv.conf and run apt-get update >> to >> get the packages list. >> >> Actually, you can build your own root image by rpm command (like me). >> For >> example: >> >> dd if=/dev/zero of=redhat-9.0.ext3.1gb bs=1024 count=1048576 >> mkfs.ext3 redhat-9.0.ext3.1gb >> mkdir root >> mount -o loop redhat-9.0.ext3.1gb root >> rpm --initdb --root=$PWD/root >> >> At this point, you can install whatever you want. All rpm commands must >> be >> added --root option. That's all and then bzip2 it. >> >> umount root >> bzip2 -k -9 redhat-9.0.ext3.1gb >> >> Good luck, >> >> >> > Installing a "normal" distribution on coLinux - "The Slackware on > coLinux >> > HOWTO"I am very impressed with the power of coLinux. Great work for a >> > 1-month old (public) project. >> > >> > Has anyone attempted or succeeded in getting a recent RedHat install > done >> > through coLinux? I've read the threads started by Nir Perry about his >> > experiences with Slackware, but I am not experienced enough with Linux >> > administration to try to duplicate them, much less apply them to >> RedHat. >> > >> > I've had a lot of luck with the Debian starter image, but some of my >> > programs behave very strangely (crash). The behavior looks like it > could >> be >> > due to incompatibilities between compiler and library versions, or >> they >> > might be due to coLinux. I really can't tell, and would like to take > the >> > distribution differences out of the loop to isolate the problem. >> > >> > I realize that the coLinux developers have lots to do, but >> fortunately, >> the >> > images aren't impacted by coLinux development. Is there another >> source > of >> > images out there? (vmware users) Is there enough interest to start a >> projct >> > compiling a library of images? Or is it just easier to focus effort >> on >> > getting coLinux to boot generic install CD's, and go from there? >> > >> > Any help would be appretiated. >> > >> > Rob >> > >> > >> > >> > ------------------------------------------------------- >> > 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 > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFANOArnwJBIFTVIqwRAvAhAJ9fe46AC8++Veq+4322EftPZROj8gCffsF3 hRX8ux9aH0ktscdvMQHyxnM= =HBAy -----END PGP SIGNATURE----- |
From: John L. <jo...@su...> - 2004-02-19 16:55:28
|
This is actually a bug in apt-utils. If you limit your sources.list to one source, then you should be able to upgrade apt-utils(from testing). Then you can have as many sources as needed. John Rob McDonald wrote: >Thanks for making that image available. > >It seems to work good for starters, but when I try to do an apt-get update, >it downloads the release and pkglist files, and then crashes with an alloc >failure while it is trying to read the package lists. > >I tried adding > >APT::Cache-Limit "8388608"; > >to the /etc/apt/apt.conf > >And I tried removing some of the servers from (to make the package list >smaller) > >/etc/apt/sources.list > >Did you have this problem? Any ideas for a solution? > >I am running the latest binary release of coLinux. > >Thanks again, > > Rob > > > > |
From: John L. <jo...@su...> - 2004-02-19 17:25:20
|
Whoops, just realized you're talking about a redhat distro. Well, it still might be the same bug. But maybe not. John John LeSueur wrote: > This is actually a bug in apt-utils. If you limit your sources.list > to one source, then you should be able to upgrade apt-utils(from > testing). Then you can have as many sources as needed. > > John > |
From: Sugree P. <su...@hp...> - 2004-02-19 19:09:24
|
You might need to increase memory size or add more swap. <memory size="32"></memory> Good luck, Sugree Phatanapherom su...@hp... ----- Original Message ----- From: "Rob McDonald" <ro...@as...> To: "Sugree Phatanapherom" <su...@hp...>; <col...@li...> Sent: Thursday, February 19, 2004 10:26 PM Subject: Re: [coLinux-devel] RedHat on coLinux ? > Thanks for making that image available. > > It seems to work good for starters, but when I try to do an apt-get update, > it downloads the release and pkglist files, and then crashes with an alloc > failure while it is trying to read the package lists. > > I tried adding > > APT::Cache-Limit "8388608"; > > to the /etc/apt/apt.conf > > And I tried removing some of the servers from (to make the package list > smaller) > > /etc/apt/sources.list > > Did you have this problem? Any ideas for a solution? > > I am running the latest binary release of coLinux. > > Thanks again, > > Rob > > > > I am using coLinux with RedHat 9.0. If you want to try (49 MB): > > > > http://amata.cpe.ku.ac.th/~sugree/dload/colinux/redhat-9.0.ext3.1gb.bz2 > > > > It contains only based packages. Man is installed but no man pages for > APIs > > at all. Anyway, you can use apt-get to install anythings you want easily. > > The pre-configured sources are pointing to freshrpms and dag repositories. > > So the first step is to modify /etc/resolv.conf and run apt-get update to > > get the packages list. > > > > Actually, you can build your own root image by rpm command (like me). For > > example: > > > > dd if=/dev/zero of=redhat-9.0.ext3.1gb bs=1024 count=1048576 > > mkfs.ext3 redhat-9.0.ext3.1gb > > mkdir root > > mount -o loop redhat-9.0.ext3.1gb root > > rpm --initdb --root=$PWD/root > > > > At this point, you can install whatever you want. All rpm commands must be > > added --root option. That's all and then bzip2 it. > > > > umount root > > bzip2 -k -9 redhat-9.0.ext3.1gb > > > > Good luck, > > > > > > > Installing a "normal" distribution on coLinux - "The Slackware on > coLinux > > > HOWTO"I am very impressed with the power of coLinux. Great work for a > > > 1-month old (public) project. > > > > > > Has anyone attempted or succeeded in getting a recent RedHat install > done > > > through coLinux? I've read the threads started by Nir Perry about his > > > experiences with Slackware, but I am not experienced enough with Linux > > > administration to try to duplicate them, much less apply them to RedHat. > > > > > > I've had a lot of luck with the Debian starter image, but some of my > > > programs behave very strangely (crash). The behavior looks like it > could > > be > > > due to incompatibilities between compiler and library versions, or they > > > might be due to coLinux. I really can't tell, and would like to take > the > > > distribution differences out of the loop to isolate the problem. > > > > > > I realize that the coLinux developers have lots to do, but fortunately, > > the > > > images aren't impacted by coLinux development. Is there another source > of > > > images out there? (vmware users) Is there enough interest to start a > > projct > > > compiling a library of images? Or is it just easier to focus effort on > > > getting coLinux to boot generic install CD's, and go from there? > > > > > > Any help would be appretiated. > > > > > > Rob > > > > > > > > > > > > ------------------------------------------------------- > > > 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 |