Menu
▾
▴
colinux-devel
|
From: Eric S. J. <es...@ha...> - 2004-04-06 21:17:06
|
I am very intrigued by cooperative Linux at and I would like to try it if I can have the same machine dual boot into Linux for Windows and if I am running on windows, run cooperative Linux off of the dual boot partition. it seems to me that in order to do this, you would need two kernels and the boot loaders would be configured to load either one or the other depending a context. I will admit that my original thought was to try and install gentoo on the system via a cooperative Linux installed base. From what I've learned so far, I would say it is possible but not advisable. in any case, the two OS/triple boot model is intriguing for variety of reasons and I'm wondering just how practical is it? ---eric |
|
From: keksov <ke...@gm...> - 2004-04-06 21:48:49
|
IMHO, as soon as you have the same kernel version under real Linux and may= live without device drivers apart bare minimum under coLinux/Windows you'l= l not notice any significant difference under both instances of your Linux's b= oots. From=20technical point of view it's possible, e.g. I have tried exactly the= same configuration and it worked fine. In other words - dual boot of your raw Li= nux installation is possible. The rest depends on your needs. Sure, under coLinux you'll not get native graphical console but there were= some workarounds mentioned here in the list not far from now, just search archiv= e. Regards, Dim Tuesday, April 6, 2004, 11:15:07 PM, you wrote: ESJ> I am very intrigued by cooperative Linux at and I would like to try it= =20 ESJ> if I can have the same machine dual boot into Linux for Windows and if= I=20 ESJ> am running on windows, run cooperative Linux off of the dual boot part= ition. ESJ> it seems to me that in order to do this, you would need two kernels an= d=20 ESJ> the boot loaders would be configured to load either one or the other= =20 ESJ> depending a context. ESJ> I will admit that my original thought was to try and install gentoo on= =20 ESJ> the system via a cooperative Linux installed base. From what I've=20 ESJ> learned so far, I would say it is possible but not advisable. ESJ> in any case, the two OS/triple boot model is intriguing for variety of= =20 ESJ> reasons and I'm wondering just how practical is it? ESJ> ---eric ESJ> ------------------------------------------------------- ESJ> This SF.Net email is sponsored by: IBM Linux Tutorials ESJ> Free Linux tutorial presented by Daniel Robbins, President and CEO of ESJ> GenToo technologies. Learn everything from fundamentals to system ESJ> administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3D= click ESJ> _______________________________________________ ESJ> coLinux-devel mailing list ESJ> coL...@li... ESJ> https://lists.sourceforge.net/lists/listinfo/colinux-devel |
|
From: Eric S. J. <es...@ha...> - 2004-04-07 13:20:26
|
Gregory M. Turner wrote:
> On Tuesday 06 April 2004 05:53 pm, Eric S. Johansson wrote:
>
>>I three-quarters understand what you mean. What I am hearing is that I
>>can run the same kernel both as a guest and native.
>
>
> Maybe, but I am not sure you would want to. "Everything else" but the kernel
> sounds more logical to me... also remember that 2.4 means no NPTL-enabled
> goodies allowed.
that's closer to what I thought was happening. You would have all the
commands and demons be the same and only the kernels would differ. You
would have two sets of kernel files in /boot and /lib/modules<kernel{1,2}>.
> Anyhow, there is no reason you couldn't still do something like you describe:
> follow the standard Gentoo bootstrap instructions, but instead of creating a
> raw filesystem partition, install to a loopback device which points to your
> windows filesystem.
>
> For example, it is possible to use Linux's built in NTFS "write" support
...
> o Point the coLinux XML file at your ext3/gentoo install
>
> It should work just fine.
very cool technique. Trouble is I have a big old partition currently
filled with mepis that I'm going to replace with gentoo.
>>but I will be paying attention. This system has some exciting
>>possibilities for enhancing handicap accessibility for Linux. The big
>>challenge I'm facing is "how do I make speech recognition work on/with
>>Linux". Today, it's pretty primitive and requires two machines or a
>>continuing investment in VMware. Cooperative Linux, holds out the
>>possibility of providing a platform where that is not such a big issue.
>
>
> Wow, I am extremely surprised there is no such software for Linux... can this
> really be true?
there are rather primitive pieces out there like Sphinx and some very
small vocabulary command and control toys. Anyone who has been injured
or has lost hand function to such a degree that they need to speak
instead of type, needs a very large (hundred thousand word) vocabulary
continuous recognition system. Usually they also need the ability to
create their own grammars and actions in order to customize the system
to their way of working. For example, I have a reasonably decent
grammar set for Emacs and Python. It's not as nice as I would like to
because of my inability to extract fine detail information about python
from my development environment.
For example, it would be nice to be able to have available what names
would be appropriate in a given context so that as I am dictating
something like:
Zodiac["top"] = inflatable.toy()["bottom"]
at the beginning of the sentence, the vocabulary should be limited to
all of the known variables, classes, and functions. Once I've stated
one of them, based on the type information (i.e. dictionary, list,
integer etc.) I should have a certain set of choices in this case
"indexed" which would put me between the square brackets and set the
vocabulary to list of known indices for that dictionary. Then the next
thing with the ether something relating to what is placed into the
dictionary or "=" which would reset the grammar to the same as the start
of the line. I will go through the rest of the line but I think you can
see that there's a lot of vocabulary shuffling going on and should be
going on as you dictate the entire line.
this is possible in a primitive way today if only I could get the right
information. but this is way off the beaten path here.
>
>
>>Of course, ideally I should be able to run this crap under wine but the
>>installer problems are quite persistent. So we're focusing on making a
>>bridge so that when speech recognition reaches Linux, the infrastructure
>>will be ready for real and not a system created by people whose hands
>>work and really don't understand the problems we face.
>
>
> Sorry to hear that wine is not working out for you... e-mail me with the
> details of the software that you are using and I might be able to help you.
it's usual kernel 100 type errors. I'm trying to get my other laptop
running gentoo and something is weird with the CD-ROM set up. I just
haven't had enough time to wrestle with it.
>>np, startx works for me.
>
>
> "startx" is probably not going to work in coLinux, which has no framebuffer
> support. You will need to use a native X server like Cygwin X to get your
> gui fix in coLinux.
sorry. I should have said I was comfortable with the text only console
and host resident Xserver. and that when I booted native, I did not
need a graphical console but could type startx all by my lonesome. I'm
a *all* grown up.. ;-) usually..
---eric
|
|
From: <ch...@to...> - 2004-04-07 18:46:11
|
>> follow the standard Gentoo bootstrap instructions, but instead of >> creating a >> raw filesystem partition, install to a loopback device which points to >> your >> windows filesystem. >> >> For example, it is possible to use Linux's built in NTFS "write" support > ... >> o Point the coLinux XML file at your ext3/gentoo install >> be shure to write only inside an already created loopback file and this file should not be a sparce file. Linux can create errors in the filesystem if creating a file or deleting it or changing it's size chris |
|
From: Digital I. Inc. <ok...@di...> - 2004-04-07 23:26:26
|
I have not read whole thread (it is long!),
but if what you focus is about writing a loop back partition,
I already did it on conoppix.
it can write loop back partition on NTFS.
and probably next version of KNOPPIX has "captive",
which loads genie NTFS.dll on Linux from c:/windows/system32,
so you can write real NTFS, if you have real Windows installed on your C:.
and I have a plan to add a function which is writing read-only partion.
there are two techs for it - COW and Union FS.
I dont decided to which tech to use yet, but anyway,
I will add it in the near future.
--- Okajima.
>
>>> follow the standard Gentoo bootstrap instructions, but instead of
>>> creating a
>>> raw filesystem partition, install to a loopback device which points to
>>> your
>>> windows filesystem.
>>>
>>> For example, it is possible to use Linux's built in NTFS "write" support
>> ...
>>> o Point the coLinux XML file at your ext3/gentoo install
>>>
>
>be shure to write only inside an already created loopback file and this
>file should not be a sparce file. Linux can create errors in the
>filesystem if creating a file or deleting it or changing it's size
>
>chris
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IBM Linux Tutorials
>Free Linux tutorial presented by Daniel Robbins, President and CEO of
>GenToo technologies. Learn everything from fundamentals to system
>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>_______________________________________________
>coLinux-devel mailing list
>coL...@li...
>https://lists.sourceforge.net/lists/listinfo/colinux-devel
>
|
|
From: Gregory M. T. <gmt...@am...> - 2004-04-08 14:53:14
|
On Wednesday 07 April 2004 06:25 pm, Digital Infra, Inc. wrote: > I have not read whole thread (it is long!), > but if what you focus is about writing a loop back partition, > I already did it on conoppix. > > it can write loop back partition on NTFS. I have not tried it, but considering that the built-in kernel NTFS write support had it's "experimental/dangerous" warnings removed from the help in Andrew Morton's recent 2.6 kernels, I am guessing that it will simply refuse to do anything dangerous, rather than destroying your filesystem... be warned that this advice is probably worth what you paid for it. Anyhow, my educated guess is that if you create a non-compressed, non-encrypted large file using cygwin dd, filled with /dev/random data instead of /dev/zero (for extra paranoia about any spase-file issues) on an NTFS partition, it's totally safe to use linux's built-in NTFS "write" support and loop-devices to write to it, no captive NTFS required. I have used this technique to fix unbootable colinux partitions successfully, at least. I should document this technique in the wiki, I suppose... > and probably next version of KNOPPIX has "captive", > which loads genie NTFS.dll on Linux from c:/windows/system32, > so you can write real NTFS, if you have real Windows installed on your C:. captive NTFS is pretty nifty... makes you wonder about other drivers (I believe there has been some promising experimental work with NT display drivers and X as well). -- gmt "How prone all human institutions have been to decay; how subject the best-formed and most wisely organized governments have been to lose their check and totally dissolve; how difficult it has been for mankind, in all ages and countries, to preserve their dearest rights and best privileges, impelled as it were by an irresistible fate of despotism." --James Monroe |
|
From: Ian C. B. <ia...@bl...> - 2004-04-08 15:13:38
|
> captive NTFS is pretty nifty... makes you wonder about other drivers (I > believe there has been some promising experimental work with NT display > drivers and X as well). Also with wireless and other network device drivers (NDIS shim), not to mention with CODECs under avifile (with viewers like mplayer/xine/gstreamer/etc.). NDIS wrappers: http://ndiswrapper.sf.net http://www.linuxant.com AVIFile CODECs: http://avifile.sf.net Thunking shim layers to Windows native drivers is becoming an increasingly popular thing to do. This poor-man's binary compatibility silliness wouldn't be neccesary if vendors would simply open up their chipset reference docs. - Ian C. Blenke <ia...@bl...> |
|
From: Digital I. Inc. <ok...@di...> - 2004-04-09 10:20:04
|
Yeah, your guessing is right.
and you can read a virtual partition ( = just a big file on NTFS)
from NT.
if you formatted it with FAT32, use filedisk.exe. I felt it is stable.
with ext2, use ext2 IFS driver (under development...).
--- Okajima.
>On Wednesday 07 April 2004 06:25 pm, Digital Infra, Inc. wrote:
>> I have not read whole thread (it is long!),
>> but if what you focus is about writing a loop back partition,
>> I already did it on conoppix.
>>
>> it can write loop back partition on NTFS.
>
>I have not tried it, but considering that the built-in kernel NTFS write
>support had it's "experimental/dangerous" warnings removed from the help in
>Andrew Morton's recent 2.6 kernels, I am guessing that it will simply refuse
>to do anything dangerous, rather than destroying your filesystem... be warned
>that this advice is probably worth what you paid for it.
>
>Anyhow, my educated guess is that if you create a non-compressed,
>non-encrypted large file using cygwin dd, filled with /dev/random data
>instead of /dev/zero (for extra paranoia about any spase-file issues) on an
>NTFS partition, it's totally safe to use linux's built-in NTFS "write"
>support and loop-devices to write to it, no captive NTFS required. I have
>used this technique to fix unbootable colinux partitions successfully, at
>least. I should document this technique in the wiki, I suppose...
>
>> and probably next version of KNOPPIX has "captive",
>> which loads genie NTFS.dll on Linux from c:/windows/system32,
>> so you can write real NTFS, if you have real Windows installed on your C:.
>
>captive NTFS is pretty nifty... makes you wonder about other drivers (I
>believe there has been some promising experimental work with NT display
>drivers and X as well).
>
>--
>gmt
>
>"How prone all human institutions have been to decay; how subject
>the best-formed and most wisely organized governments have been
>to lose their check and totally dissolve; how difficult it has
>been for mankind, in all ages and countries, to preserve their
>dearest rights and best privileges, impelled as it were by an
>irresistible fate of despotism." --James Monroe
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IBM Linux Tutorials
>Free Linux tutorial presented by Daniel Robbins, President and CEO of
>GenToo technologies. Learn everything from fundamentals to system
>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>_______________________________________________
>coLinux-devel mailing list
>coL...@li...
>https://lists.sourceforge.net/lists/listinfo/colinux-devel
>
|
|
From: Eric S. J. <es...@ha...> - 2004-04-06 22:56:35
|
keksov wrote: > IMHO, as soon as you have the same kernel version under real Linux and may live > without device drivers apart bare minimum under coLinux/Windows you'll not > notice any significant difference under both instances of your Linux's boots. I three-quarters understand what you mean. What I am hearing is that I can run the same kernel both as a guest and native. The only difference is the device drivers. This is what gets puzzling. It sounds like under cooperative Linux, I use a different set of device drivers than under native operations. Is that correct? For example, to access the CD-ROM, I would use two different sets of drivers. > >>From technical point of view it's possible, e.g. I have tried exactly the same > configuration and it worked fine. In other words - dual boot of your raw Linux > installation is possible. The rest depends on your needs. somewhat more clarification is needed. For example, I want to use gentoo. Would I start the installation in native mode or in host/guest mode? I suspect I would need to install native and then convert to cooperative Linux. I also suspect I will need to wait given what I've heard about 2.6 support. Unfortunately, I really need the sound system support. but I will be paying attention. This system has some exciting possibilities for enhancing handicap accessibility for Linux. The big challenge I'm facing is "how do I make speech recognition work on/with Linux". Today, it's pretty primitive and requires two machines or a continuing investment in VMware. Cooperative Linux, holds out the possibility of providing a platform where that is not such a big issue. Of course, ideally I should be able to run this crap under wine but the installer problems are quite persistent. So we're focusing on making a bridge so that when speech recognition reaches Linux, the infrastructure will be ready for real and not a system created by people whose hands work and really don't understand the problems we face. > Sure, under coLinux you'll not get native graphical console but there were some > workarounds mentioned here in the list not far from now, just search archive. np, startx works for me. thanks for the information. --- eric |
|
From: Gregory M. T. <gmt...@am...> - 2004-04-07 02:06:07
|
On Tuesday 06 April 2004 05:53 pm, Eric S. Johansson wrote: > I three-quarters understand what you mean. What I am hearing is that I > can run the same kernel both as a guest and native. Maybe, but I am not sure you would want to. "Everything else" but the kernel sounds more logical to me... also remember that 2.4 means no NPTL-enabled goodies allowed. > The only difference > is the device drivers. This is what gets puzzling. It sounds like > under cooperative Linux, I use a different set of device drivers than > under native operations. Is that correct? For example, to access the > CD-ROM, I would use two different sets of drivers. Dunno about CD-ROM access in coLinux; I haven't tried it yet (samba<->NT filesharing does all I need there). > >From technical point of view it's possible, e.g. I have tried exactly the > > same configuration and it worked fine. In other words - dual boot of your > > raw Linux installation is possible. The rest depends on your needs. > > somewhat more clarification is needed. For example, I want to use > gentoo. Would I start the installation in native mode or in host/guest > mode? I suspect I would need to install native and then convert to > cooperative Linux. It's too bad, there used to be an image at http://killashandra.magenet.com/~s0be/ which was custom-made for this purpose. I used that as a starting point and am scooting along happily with gentoo. Anyhow, there is no reason you couldn't still do something like you describe: follow the standard Gentoo bootstrap instructions, but instead of creating a raw filesystem partition, install to a loopback device which points to your windows filesystem. For example, it is possible to use Linux's built in NTFS "write" support (which actually only supports writing to unencrypted, uncompressed files without changing their size -- but is still just-good-enough for this purpose) under native linux. Just: o create a big empty file with cygwin's "dd" or some other technique. o boot into native Linux o mount your NTFS partition in rw mode o create your loopback device pointing at the big empty file o format the loopback device as ext3 o mount it as /mnt/tmp/ o follow gentoo install instructions from there to the end (except kernel parts) o Boot back into windows o Point the coLinux XML file at your ext3/gentoo install It should work just fine. > I also suspect I will need to wait given what I've heard about 2.6 > support. Unfortunately, I really need the sound system support. > > but I will be paying attention. This system has some exciting > possibilities for enhancing handicap accessibility for Linux. The big > challenge I'm facing is "how do I make speech recognition work on/with > Linux". Today, it's pretty primitive and requires two machines or a > continuing investment in VMware. Cooperative Linux, holds out the > possibility of providing a platform where that is not such a big issue. Wow, I am extremely surprised there is no such software for Linux... can this really be true? > Of course, ideally I should be able to run this crap under wine but the > installer problems are quite persistent. So we're focusing on making a > bridge so that when speech recognition reaches Linux, the infrastructure > will be ready for real and not a system created by people whose hands > work and really don't understand the problems we face. Sorry to hear that wine is not working out for you... e-mail me with the details of the software that you are using and I might be able to help you. > > Sure, under coLinux you'll not get native graphical console but there > > were some workarounds mentioned here in the list not far from now, just > > search archive. > > np, startx works for me. "startx" is probably not going to work in coLinux, which has no framebuffer support. You will need to use a native X server like Cygwin X to get your gui fix in coLinux. > thanks for the information. HTH -- gmt |
|
From: keksov <ke...@gm...> - 2004-04-07 05:18:48
|
ESJ> What I am hearing is that I can run the same kernel both as a guest and native. If you mean under the word "same" the version number then yes, you are right. Actually it's very simple- the main part of coLinux is kernel 2.4 with some patches applied. You may run it under Windows and native Linux as well. But you can't boot the native Linux with the same vmlinux file which is used by coLinux. ESJ> The only difference is the device drivers. This is what gets puzzling. It ESJ> sounds like under cooperative Linux, I use a different set of device ESJ> drivers than under native operations. Is that correct? For example, to ESJ> access the CD-ROM, I would use two different sets of drivers. AFAIK, under coLinux all IDE block devices are accessed via cobd driver. I remember reports that it's even possible to mount CDROM under Windows as soon as it's not in use by Windows itself, i.e. no one files opened from it. Under coLinux It looks like that: userApp -> coLinux virtualisation driver -> native OS driver (1) -> hardware Where (1) is either Linux driver or Windows one. ESJ> somewhat more clarification is needed. For example, I want to use ESJ> gentoo. Would I start the installation in native mode or in host/guest ESJ> mode? I suspect I would need to install native and then convert to ESJ> cooperative Linux. I have two disks in my system. In pre coLinux times I've installed gentoo as alternative OS. After discovering coLinux I put the line <block_device index="0" path="\DEVICE\Harddisk2\Partition1" enabled="true"/> ( /root ) into default.colinux.xml and start coLinux under Windows. So, it have to be defined what OS is by itself- a kernel only or a kernel + all daemons and user apps. ESJ> I also suspect I will need to wait given what I've heard about 2.6 ESJ> support. Unfortunately, I really need the sound system support. As I've mentioned above all devices should be wrapped by coLinux visualization driver. Please correct me if is's wrong. ESJ> but I will be paying attention. This system has some exciting ESJ> possibilities for enhancing handicap accessibility for Linux. The big ESJ> challenge I'm facing is "how do I make speech recognition work on/with ESJ> Linux". Today, it's pretty primitive and requires two machines or a ESJ> continuing investment in VMware. Cooperative Linux, holds out the ESJ> possibility of providing a platform where that is not such a big issue. Take a look here, may be you'll find something interesting: http://www.faqs.org/docs/Linux-HOWTO/Speech-Recognition-HOWTO.html And pay closer attention to this one: http://www.speech.cs.cmu.edu/sphinx/Sphinx.html >> Sure, under coLinux you'll not get native graphical console but there were some >> workarounds mentioned here in the list not far from now, just search archive. ESJ> np, startx works for me. Oops... how it looks like? Can you post a screenshot, please? Regards, Dim |
|
From: Eric S. J. <es...@ha...> - 2004-04-07 13:24:26
|
keksov wrote: > Take a look here, may be you'll find something interesting: > http://www.faqs.org/docs/Linux-HOWTO/Speech-Recognition-HOWTO.html > > And pay closer attention to this one: > http://www.speech.cs.cmu.edu/sphinx/Sphinx.html been aware of them for years. Unfortunately, things like the ViaVoice for Linux was a stinking pile of Pooh and Sphinx was far too much of a bag of parts that nobody could get really working except the grad students themselves. Sphinx may be changing however. ---eric |
|
From: andre <avb...@gm...> - 2004-04-07 18:59:26
|
On Wednesday 07 April 2004 04:06, Gregory M. Turner wrote: > For example, it is possible to use Linux's built in NTFS "write" support > (which actually only supports writing to unencrypted, uncompressed files > without changing their size -- but is still just-good-enough for this > purpose) under native linux. Just: AFAIK understood it it also can do "everything else" but that only modifing a file without changing its size is save > o mount your NTFS partition in rw mode maybe the NTFS driver should need a read/modify mode? Another thing to do for this is modifing linux so fstab points to the right name depending on a colinux or linux boot. This can probably be done by modifing rc.sysinit. |
|
From: <ch...@to...> - 2004-04-07 23:33:58
|
> On Wednesday 07 April 2004 04:06, Gregory M. Turner wrote: >> For example, it is possible to use Linux's built in NTFS "write" support >> (which actually only supports writing to unencrypted, uncompressed files >> without changing their size -- but is still just-good-enough for this >> purpose) under native linux. Just: > > AFAIK understood it it also can do "everything else" but that only > modifing a > file without changing its size is save yes that is the only safe operation but the others are possible > >> o mount your NTFS partition in rw mode > > maybe the NTFS driver should need a read/modify mode? > that would be nice so that people who use it for loopbacks would be a little safer there is another project that uses the windows drivers for ntfs but is kinda legally questionable depending on local laws it is aginst the MS EULA so you need a local law that overides to use it legally. I have not tried it but it sounds interesting http://www.jankratochvil.net/project/captive/ > > > Another thing to do for this is modifing linux so fstab points to the > right > name depending on a colinux or linux boot. This can probably be done by > modifing rc.sysinit. > check out the topologilinux howTo in the wiki the method of handling fstab differences and other differences should be adaptable but you will need to create a do nothing initrd for booting nativly chris |
|
From: Digital I. Inc. <ok...@di...> - 2004-04-07 00:33:17
|
I am working on conoppix. it is KNOPPIX ( CD boot linux) based new linux distribution. it has three ways to boot - 1. CD boot 2. loop back boot 3. coLinux virtual boot loop back boot is, you can boot from c:/linux/conoppix.compressed.img by NTLDR. and the CD has cygwin/X Japanese installer forked by autorun.inf. ( Of course, it can display English). you put a CD to your Windows box, then a splash screen comes, everything installed, and runs coLinux. any problem? I think if you are newbie of Linux, you dont have to install gentoo on a raw partition. and it is easy to make "conoGentoo" or "conoFedra". somebody would try it. BTW, conoppix is just a working title, named by Aloni. what name is good? luckyly, conoppix.(com|net|org) and conoppix.jp are vacant. --- Okajima. >I am very intrigued by cooperative Linux at and I would like to try it >if I can have the same machine dual boot into Linux for Windows and if I >am running on windows, run cooperative Linux off of the dual boot partition. > >it seems to me that in order to do this, you would need two kernels and >the boot loaders would be configured to load either one or the other >depending a context. > >I will admit that my original thought was to try and install gentoo on >the system via a cooperative Linux installed base. From what I've >learned so far, I would say it is possible but not advisable. > >in any case, the two OS/triple boot model is intriguing for variety of >reasons and I'm wondering just how practical is it? > >---eric > > > >------------------------------------------------------- >This SF.Net email is sponsored by: IBM Linux Tutorials >Free Linux tutorial presented by Daniel Robbins, President and CEO of >GenToo technologies. Learn everything from fundamentals to system >administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click >_______________________________________________ >coLinux-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
|
From: Christophe T. <ch...@ae...> - 2004-04-07 01:28:09
|
That's a great idea. About the domain name, I think registering only the .org would make sense since it's an opensource/GPL initiative. Also, you could get the "conoppix" project registered on SourceForge for hosting. -Christophe ----- Original Message ----- From: "Digital Infra, Inc." <ok...@di...> To: "Eric S. Johansson" <es...@ha...> Cc: <col...@li...> Sent: Tuesday, April 06, 2004 5:29 PM Subject: Re: [coLinux-devel] conoppix > > I am working on conoppix. > > it is KNOPPIX ( CD boot linux) based new linux distribution. > > it has three ways to boot - > > 1. CD boot > 2. loop back boot > 3. coLinux virtual boot > > loop back boot is, you can boot from c:/linux/conoppix.compressed.img by NTLDR. > and the CD has cygwin/X Japanese installer forked by autorun.inf. > ( Of course, it can display English). > > you put a CD to your Windows box, then a splash screen comes, everything installed, > and runs coLinux. any problem? > I think if you are newbie of Linux, > you dont have to install gentoo on a raw partition. > > and it is easy to make "conoGentoo" or "conoFedra". > somebody would try it. > > BTW, conoppix is just a working title, named by Aloni. > what name is good? > luckyly, conoppix.(com|net|org) and conoppix.jp are vacant. > > > --- Okajima. > > > >I am very intrigued by cooperative Linux at and I would like to try it > >if I can have the same machine dual boot into Linux for Windows and if I > >am running on windows, run cooperative Linux off of the dual boot partition. > > > >it seems to me that in order to do this, you would need two kernels and > >the boot loaders would be configured to load either one or the other > >depending a context. > > > >I will admit that my original thought was to try and install gentoo on > >the system via a cooperative Linux installed base. From what I've > >learned so far, I would say it is possible but not advisable. > > > >in any case, the two OS/triple boot model is intriguing for variety of > >reasons and I'm wondering just how practical is it? > > > >---eric > > > > > > > >------------------------------------------------------- > >This SF.Net email is sponsored by: IBM Linux Tutorials > >Free Linux tutorial presented by Daniel Robbins, President and CEO of > >GenToo technologies. Learn everything from fundamentals to system > >administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > >_______________________________________________ > >coLinux-devel mailing list > >coL...@li... > >https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X