colinux-devel — Cooperative Linux development mailing list

Re: [coLinux-devel] Single user mode (i.e., kernel commandline parameters)

[Ian L. <Ian...@mq...>]

> >Yes you can get to a cmd prompt without init.  Change the boot 
> >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).


> Yep.  I tried putting multiple <bootparams>...</bootparams> entries in 
> the file.  Nothing appears to work.  Also, if 'root=/dev/cobd0' (or 
> whatever) is not first in the <bootparams> entry, the kernel panics 
> saying it cannot mount the root device and to please specify one.  It 
> appears that all items after 'root=...' are ignored.
> 

Yeah .. if you've got the wrong ver or Dan hasn't added it then you'll
have to wait for the next version .. or .. mount your file system under
another linux and move /bin/sh over init.


--
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/

Re: [coLinux-devel] Single user mode (i.e., kernel commandline parameters)

[Dan A. <da...@gm...>]

On Sat, Feb 14, 2004 at 12:58:40AM -0600, Jason A. Pattie wrote:
> How do I get to a command prompt without running init (i.e., I messed 
> with my /etc/shadow file and stopped myself from even being able to 
> login)?  I don't even think single user mode will help me at this point.

You can add init=/bin/bash to the bootparams in the XML file.

-- 
Dan Aloni
da...@gm...

Re: [coLinux-devel] Single user mode (i.e., kernel commandline parameters)

[Jason A. P. <pat...@pc...>]

Ian Latter wrote:

>Yes you can get to a cmd prompt without init.  Change the boot 
>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.

>(boot prompt equiv is "boot: vmlinux init=/bin/sh" or similar)  Its
>an old recovery/hacking technique.
>  
>
Yep.  I tried putting multiple <bootparams>...</bootparams> entries in 
the file.  Nothing appears to work.  Also, if 'root=/dev/cobd0' (or 
whatever) is not first in the <bootparams> entry, the kernel panics 
saying it cannot mount the root device and to please specify one.  It 
appears that all items after 'root=...' are ignored.

>
>----- Original Message -----
>  
>
>>From: "andre" <avb...@gm...>
>>To: <col...@li...>
>>Subject:  Re: [coLinux-devel] Single user mode (i.e., kernel commandline parameters)
>>Date: Sat, 14 Feb 2004 02:52:25 +0100
>>
>>On Saturday 14 February 2004 07:58, Jason A. Pattie wrote:
>>    
>>
>>>How do I get to a command prompt without running init (i.e., I messed
>>>with my /etc/shadow file and stopped myself from even being able to
>>>login)?  I don't even think single user mode will help me at this point.
>>>
>>>Thanks.
>>>      
>>>
>> You don't (maybe not true when you start it up in initlevel 1)
>>
>>But you can mount your partition from an other (co)linux instal and chroot to 
>>your partition and fix it.
>>
>>
>>-------------------------------------------------------
>>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
>>
>>    
>>
>
>--
>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/
>
>
>
>-------------------------------------------------------
>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
>
>  
>



-- 
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.

Re: [coLinux-devel] Using native Linux partitions as root device

[andre <avb...@gm...>]

On Saturday 14 February 2004 01:20, Jason A. Pattie wrote:
> My laptop is already a dual-booted Win2K/Linux machine.  Is it possible
> to forgoe using the Debian 1GB ext3 image from the download site and
> instead point it somehow at my existing Linux installation?  This would
> be really neat.
>
> Thanks.
It is something like 

<block_device index="0" path="\Device\HarddiskVolume2" enabled="true">
 </block_device>

in your xml file.

Re: [coLinux-devel] Single user mode (i.e., kernel commandline parameters)

[Ian L. <Ian...@mq...>]

Yes you can get to a cmd prompt without init.  Change the boot 
parameters in the default xml file such that "init=/bin/sh".

(boot prompt equiv is "boot: vmlinux init=/bin/sh" or similar)  Its
an old recovery/hacking technique.


----- Original Message -----
>From: "andre" <avb...@gm...>
>To: <col...@li...>
>Subject:  Re: [coLinux-devel] Single user mode (i.e., kernel commandline parameters)
>Date: Sat, 14 Feb 2004 02:52:25 +0100
>
> On Saturday 14 February 2004 07:58, Jason A. Pattie wrote:
> > How do I get to a command prompt without running init (i.e., I messed
> > with my /etc/shadow file and stopped myself from even being able to
> > login)?  I don't even think single user mode will help me at this point.
> >
> > Thanks.
>  You don't (maybe not true when you start it up in initlevel 1)
> 
> But you can mount your partition from an other (co)linux instal and chroot to 
> your partition and fix it.
> 
> 
> -------------------------------------------------------
> 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
> 

--
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/

Re: [coLinux-devel] Single user mode (i.e., kernel commandline parameters)

[andre <avb...@gm...>]

On Saturday 14 February 2004 07:58, Jason A. Pattie wrote:
> How do I get to a command prompt without running init (i.e., I messed
> with my /etc/shadow file and stopped myself from even being able to
> login)?  I don't even think single user mode will help me at this point.
>
> Thanks.
 You don't (maybe not true when you start it up in initlevel 1)

But you can mount your partition from an other (co)linux instal and chroot to 
your partition and fix it.

Re: [coLinux-devel] Getting X to work natively

[andre <avb...@gm...>]

On Saturday 14 February 2004 00:56, Ballard Jonathan wrote:
> I used cygwin X.
>
> On coLinux (Debian), use dselect to find xterm and install it or do an
> "apt-get install xterm" instead.
>
> From cygwin, use "xhost +" to allow any connection, and that is okay behind
> a firewall.

It is never okay to do a host + from a security perspective. At the very least 
do a host +192.168.0.40 or prevered use cookies or ssh

[coLinux-devel] Single user mode (i.e., kernel commandline parameters)

[Jason A. P. <pat...@pc...>]

How do I get to a command prompt without running init (i.e., I messed 
with my /etc/shadow file and stopped myself from even being able to 
login)?  I don't even think single user mode will help me at this point.

Thanks.


-- 
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.

Re: [coLinux-devel] Forced password expiration

[Jason A. P. <pat...@pc...>]

Jason A. Pattie wrote:

> Jason A. Pattie wrote:
>
>> I went to login to coLinux and suddenly I am being told that I am 
>> required to change my password immediately (root enforced).  
>> Authentication token no longer valid; new one required.
>>
>> All I did was change the root password and create a new user with the 
>> adduser command.  I've never experienced this before on a real Debian 
>> box.  Does it possibly have something to do with there not being a 
>> clock or something (just guessing)?
>>
>> Thanks.
>
>
>
> Whew!  I had to login again from the console, and it immediately 
> prompted me for a new password.  Was attempting that from SSH, and 
> obviously that didn't work.

But now that's happening all the time.  Every time I try to login, I 
have to reset my password.  What's going on?  I've effectively been 
locked out of SSH'ing into the coLinux machine.


-- 
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.

Re: [coLinux-devel] Forced password expiration

[Jason A. P. <pat...@pc...>]

Jason A. Pattie wrote:

> I went to login to coLinux and suddenly I am being told that I am 
> required to change my password immediately (root enforced).  
> Authentication token no longer valid; new one required.
>
> All I did was change the root password and create a new user with the 
> adduser command.  I've never experienced this before on a real Debian 
> box.  Does it possibly have something to do with there not being a 
> clock or something (just guessing)?
>
> Thanks.


Whew!  I had to login again from the console, and it immediately 
prompted me for a new password.  Was attempting that from SSH, and 
obviously that didn't work.


-- 
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.

Re: [coLinux-devel] Getting X to work natively

[Alejandro R. S. <as...@MI...>]

One reason I've found to use vnc instead of X forwarding is that it's
like screen. My vncviewer can crash and I can reconnect to it (though
that never happens). On the other hand, I've had problems with some X
servers on windows, and if they crash, anything you're running crashes
too.

-Alejandro

On Fri, 2004-02-13 at 18:21, andre wrote:
> On Friday 13 February 2004 23:24, Alejandro R. Sedeno wrote:
> > X won't run in the console, or using anything that requires a graphics
> > card. What's been done is to have a vnc server running X, and using
> > vncviewer to connect to it from windows. If it's not working at first,
> > check the logs it makes to help you find what's missing.
> >
> > Good luck!
> >
> > -Alejandro
> 
> Why would you use vncviewer when you can use a Xserver running on windows to 
> server the programs on colinux?
> 
> 
> -------------------------------------------------------
> 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
> 

[coLinux-devel] Forced password expiration

[Jason A. P. <pat...@pc...>]

I went to login to coLinux and suddenly I am being told that I am 
required to change my password immediately (root enforced).  
Authentication token no longer valid; new one required.

All I did was change the root password and create a new user with the 
adduser command.  I've never experienced this before on a real Debian 
box.  Does it possibly have something to do with there not being a clock 
or something (just guessing)?

Thanks.


-- 
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.

[PATCH] Re: [coLinux-devel] cobd devfs support

[Dan A. <da...@gm...>]

On Fri, Feb 13, 2004 at 04:11:13AM -0500, Pat Erley wrote:
> here's a basic patch to add cobd devfs support.  It's not 100% perfect, and I plan on getting it up to working with a /dev/cobd/ dir and symlink to it as the devices exist...
> 
> Pat Erley

Thanks, the patch I made below completes your effort.

This patch also fixes at least one invalid operation (termination 7) problem 
that was encountered. It turns out that time.c was trying to query the BIOS
directly for the system time and therefore was stopped by co_terminate(). In 
the next release, it would get this information from the host OS using a 
special interface. For now, the patch below adds devfs support and addresses 
the invalid operation problem alone.

(applies on top of 0.5.3-pre2's patch/linux)

diff -u linux/arch/i386/kernel/time.c linux/arch/i386/kernel/time.c
--- linux/arch/i386/kernel/time.c	2003-12-13 17:17:01.000000000 +0200
+++ linux/arch/i386/kernel/time.c	2004-02-14 01:50:50.000000000 +0200
@@ -121,6 +121,8 @@
 
 extern spinlock_t i8259A_lock;
 
+#ifndef CONFIG_COOPERATIVE
+
 #ifndef CONFIG_X86_TSC
 
 /* This function must be called with interrupts disabled 
@@ -254,6 +256,18 @@
 	return count;
 }
 
+#else
+
+static unsigned long do_slow_gettimeoffset(void)
+{
+	/* 
+	 * coLinux TODO for 0.5.3: Request the time from the host OS.
+	 */
+	return 0;
+}
+
+#endif
+
 static unsigned long (*do_gettimeoffset)(void) = do_slow_gettimeoffset;
 
 
diff -u linux/drivers/block/cobd.c linux/drivers/block/cobd.c
--- linux/drivers/block/cobd.c	2004-02-06 17:11:19.000000000 +0200
+++ linux/drivers/block/cobd.c	2004-02-14 01:30:47.000000000 +0200
@@ -10,6 +10,8 @@
 #include <linux/errno.h>
 #include <linux/major.h>
 #include <linux/slab.h>
+#include <linux/devfs_fs_kernel.h>
+
 
 #define MAJOR_NR COLINUX_MAJOR
 #define DEVICE_NR(device) MINOR(device)  /* has no partition bits */
@@ -19,6 +21,7 @@
 #define DEVICE_OFF(d) /* do-nothing */
 
 #include <linux/blk.h>
+#include <linux/blkpg.h>
 #include <linux/hdreg.h>
 #include <linux/cooperative.h>
 
@@ -231,10 +234,14 @@
 	for (i=0; i < cobd_devs; i++)
 		register_disk(NULL, MKDEV(MAJOR_NR, i), 1, &cobd_fops,  cobd_sizes[i]);
 
-	printk("cobd driver initialized\n");
+        devfs_register_series(NULL, "cobd%u", cobd_devs, DEVFS_FL_DEFAULT,
+                              MAJOR_NR, 0,
+                              S_IFBLK | S_IRUSR | S_IWUSR | S_IRGRP,
+                              &cobd_fops, NULL);
+	
+	printk("cobd: loaded (max %d devices)\n", cobd_devs);
 
-	result = 0;
-	return result;
+	return 0;
 
 fail_malloc_2:
 	kfree(cobd_blksizes);
@@ -242,6 +249,9 @@
 	kfree(cobd_sizes);
 fail_malloc:
 
+	if (devfs_unregister_blkdev(MAJOR_NR, "cobd"))
+		printk(KERN_WARNING "loop: cannot unregister blkdev\n");
+
 	return result;
 }
 
@@ -262,0 +273 @@
+
diff -u linux/include/asm-i386/io.h linux/include/asm-i386/io.h
--- linux/include/asm-i386/io.h	2004-02-08 00:43:12.000000000 +0200
+++ linux/include/asm-i386/io.h	2004-02-14 01:50:28.000000000 +0200
@@ -124,8 +124,7 @@
 static inline void * ioremap (unsigned long offset, unsigned long size)
 {
 #ifdef CONFIG_COOPERATIVE
- 	co_debug("ioremap %x:%d\n", offset, size); 
-	co_terminate(CO_TERMINATE_INVALID_OPERATION); 
+	panic("ioremap %ld:%ld\n", offset, size); 
 #endif
 	return __ioremap(offset, size, 0);
 }
@@ -153,8 +152,7 @@
 static inline void * ioremap_nocache (unsigned long offset, unsigned long size)
 {
 #ifdef CONFIG_COOPERATIVE
- 	co_debug("ioremap %x:%d\n", offset, size); 
-	co_terminate(CO_TERMINATE_INVALID_OPERATION); 
+	panic("ioremap_nocache %ld:%ld\n", offset, size); 
 #endif
         return __ioremap(offset, size, _PAGE_PCD);
 }
@@ -443,7 +441,9 @@
 
 static inline unsigned long badio(const char *file, int line)
 {
-	co_terminate(CO_TERMINATE_INVALID_OPERATION); 
+#ifdef CONFIG_COOPERATIVE
+	panic("badio %s:%d\n", file, line); 
+#endif
 	return 0;
 }
 



-- 
Dan Aloni
da...@gm...

Re: [coLinux-devel] Getting X to work natively

[Ballard J. <sac...@ho...>]

I used cygwin X.

On coLinux (Debian), use dselect to find xterm and install it or do an
"apt-get install xterm" instead.

From cygwin, use "xhost +" to allow any connection, and that is okay behind
a firewall.

Start the xserver.   Here is a .bat file I used to start it from the Start
menu. Update the "set CYGWIN_ROOT=" if needed.

---

@echo off
SET DISPLAY=127.0.0.1:0.0
SET CYGWIN_ROOT=C:\cygwin

REM
REM The path in the CYGWIN_ROOT environment variable assignment assume
REM that Cygwin is installed in a directory called 'cygwin' in the root
REM directory of the current drive.  You will only need to modify
REM CYGWIN_ROOT if you have installed Cygwin in another directory.  For
REM example, if you installed Cygwin in \foo\bar\baz\cygwin, you will need
REM to change \cygwin to \foo\bar\baz\cygwin.


SET PATH=.;%CYGWIN_ROOT%\bin;%CYGWIN_ROOT%\usr\X11R6\bin;%PATH%


REM
REM Cleanup after last run.
REM

if not exist %CYGWIN_ROOT%\tmp\.X11-unix\X0 goto CLEANUP-FINISH
attrib -s %CYGWIN_ROOT%\tmp\.X11-unix\X0
del %CYGWIN_ROOT%\tmp\.X11-unix\X0

:CLEANUP-FINISH
if exist %CYGWIN_ROOT%\tmp\.X11-unix rmdir %CYGWIN_ROOT%\tmp\.X11-unix

REM
REM

start XWin -multiwindow


----- Original Message -----
From: "Jason A. Pattie" <pat...@pc...>
To: <col...@li...>
Sent: Friday, February 13, 2004 8:39 PM
Subject: Re: [coLinux-devel] Getting X to work natively


> Alejandro R. Sedeno wrote:
>
> >X won't run in the console, or using anything that requires a graphics
> >card. What's been done is to have a vnc server running X, and using
> >vncviewer to connect to it from windows. If it's not working at first,
> >check the logs it makes to help you find what's missing.
> >
> >Good luck!
> >
> >
> Interesting approach.  Thanks.
>
> I suppose it might be faster running it this way than using Cygwin's X
> server?
>
> One of the neat features of Cygwin's latest X servers is -multiwindow,
> which allows Windows to "manage" X clients that connect.
>
>
>
> --
> 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.
>
>
>
> -------------------------------------------------------
> 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
>

Re: [coLinux-devel] Getting X to work natively

[andre <avb...@gm...>]

On Friday 13 February 2004 23:24, Alejandro R. Sedeno wrote:
> X won't run in the console, or using anything that requires a graphics
> card. What's been done is to have a vnc server running X, and using
> vncviewer to connect to it from windows. If it's not working at first,
> check the logs it makes to help you find what's missing.
>
> Good luck!
>
> -Alejandro

Why would you use vncviewer when you can use a Xserver running on windows to 
server the programs on colinux?

Re: [coLinux-devel] Getting X to work natively

[Jason A. P. <pat...@pc...>]

Alejandro R. Sedeno wrote:

>X won't run in the console, or using anything that requires a graphics
>card. What's been done is to have a vnc server running X, and using
>vncviewer to connect to it from windows. If it's not working at first,
>check the logs it makes to help you find what's missing.
>
>Good luck!
>  
>
Interesting approach.  Thanks.

I suppose it might be faster running it this way than using Cygwin's X
server?

One of the neat features of Cygwin's latest X servers is -multiwindow,
which allows Windows to "manage" X clients that connect.



-- 
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.

Re: [coLinux-devel] Getting X to work natively

[Alejandro R. S. <as...@MI...>]

X won't run in the console, or using anything that requires a graphics
card. What's been done is to have a vnc server running X, and using
vncviewer to connect to it from windows. If it's not working at first,
check the logs it makes to help you find what's missing.

Good luck!

-Alejandro

On Fri, 2004-02-13 at 21:48, Jason A. Pattie wrote:
> I read an e-mail that said that once someone got networking going and 
> Internet Connection Sharing, they just apt-get update'd and apt-get 
> install'd X, vnc, etc. and "it all just worked".  Does that mean that 
> you got X running natively under Windows?  I tried using the 'vesa' 
> driver to X 4.1.0 available in woody.  It messes up the Windows display 
> and moves my existing desktop offscreen.  Moving the mouse slides the 
> screen around until it "locks" back in place the way it should be.  I'm 
> currently going to go for the kdm running on coLinux with cygwin's X 
> server as the display.  It would be nice to be able to alleviate this 
> dependency, though.
> 
> Thanks.
> 

[coLinux-devel] Getting X to work natively

[Jason A. P. <pat...@pc...>]

I read an e-mail that said that once someone got networking going and 
Internet Connection Sharing, they just apt-get update'd and apt-get 
install'd X, vnc, etc. and "it all just worked".  Does that mean that 
you got X running natively under Windows?  I tried using the 'vesa' 
driver to X 4.1.0 available in woody.  It messes up the Windows display 
and moves my existing desktop offscreen.  Moving the mouse slides the 
screen around until it "locks" back in place the way it should be.  I'm 
currently going to go for the kdm running on coLinux with cygwin's X 
server as the display.  It would be nice to be able to alleviate this 
dependency, though.

Thanks.


-- 
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.

Re: [coLinux-devel] Getting networking to work

[Jason A. P. <pat...@pc...>]

Jason A. Pattie wrote:

> I've successfully downloaded the latest pre-release from the 
> SourceForge site and gotten it setup along with the 1GB image file for 
> Debian.  I found an e-mail on the devel mailing list detailing how to 
> setup the TAP device to work with Internet Connection Sharing.  It 
> also mentioned about how to setup /etc/network/interfaces and 
> /etc/hosts so lo was configured properly and localhost could be 
> ping'ed, etc.  I got all that working except for there seems to be a 
> connectivity issue between Windows and Linux.  I can ping the Linux 
> side from Windows just fine.  ifconfig under Windows gives me 
> 192.168.0.1 for the TAP connection and my network card under Windows 
> seems to be retaining its LAN IP address.  On the Linux side, I get 
> 192.168.0.40 for eth0, but I cannot ping 192.168.0.1.  I can't figure 
> out what to do next to get this to work.  Maybe the TAP driver is not 
> working correctly?  I don't have any firewalling or port filtering in 
> place under Windows that I can tell, except that I am running 
> ZoneAlarm.  Could this be causing interference?  I've selected 'Yes' 
> whenever it attempts to do the pings or other connection attempts.  
> I'll disable it and try again and let you know.

Nevermind.  ZoneAlarm was the issue.  I can now get to the Interrnet 
from Linux.  Hmm.  I don't know how to make that work, but I guess I 
kind of care, since Windows still needs protection even though Linux is 
now running on top of it.


-- 
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.

[coLinux-devel] Using native Linux partitions as root device

[Jason A. P. <pat...@pc...>]

My laptop is already a dual-booted Win2K/Linux machine.  Is it possible 
to forgoe using the Debian 1GB ext3 image from the download site and 
instead point it somehow at my existing Linux installation?  This would 
be really neat.

Thanks.


-- 
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.

[coLinux-devel] Getting networking to work

[Jason A. P. <pat...@pc...>]

I've successfully downloaded the latest pre-release from the SourceForge 
site and gotten it setup along with the 1GB image file for Debian.  I 
found an e-mail on the devel mailing list detailing how to setup the TAP 
device to work with Internet Connection Sharing.  It also mentioned 
about how to setup /etc/network/interfaces and /etc/hosts so lo was 
configured properly and localhost could be ping'ed, etc.  I got all that 
working except for there seems to be a connectivity issue between 
Windows and Linux.  I can ping the Linux side from Windows just fine.  
ifconfig under Windows gives me 192.168.0.1 for the TAP connection and 
my network card under Windows seems to be retaining its LAN IP address.  
On the Linux side, I get 192.168.0.40 for eth0, but I cannot ping 
192.168.0.1.  I can't figure out what to do next to get this to work.  
Maybe the TAP driver is not working correctly?  I don't have any 
firewalling or port filtering in place under Windows that I can tell, 
except that I am running ZoneAlarm.  Could this be causing 
interference?  I've selected 'Yes' whenever it attempts to do the pings 
or other connection attempts.  I'll disable it and try again and let you 
know.


-- 
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.

Re: [coLinux-devel] 2.6.0 port

[Dan A. <da...@gm...>]

On Fri, Feb 13, 2004 at 08:13:19AM -0500, Pat Erley wrote:
> what's the status of a 2.6.0 port and where can I pull a cvs or svn latest?
> 
> I'd like to work on the 2.6 port but don't want to start with te patch in the current release if there are already signifigant improvements.

You are welcomed, but I'd prefer not to start a 2.6 port at this stage, 
because it forces a fork on that part of development. Let both 2.6 and 
coLinux's 2.4 patch mature a little first.

-- 
Dan Aloni
da...@gm...

[coLinux-devel] 2.6.0 port

[Pat E. <pat...@ma...>]

what's the status of a 2.6.0 port and where can I pull a cvs or svn latest?

I'd like to work on the 2.6 port but don't want to start with te patch in the current release if there are already signifigant improvements.

Pat Erley

Re: [coLinux-devel] cobd devfs support

[Pat E. <pat...@ma...>]

On Fri, 13 Feb 2004 04:11:13 -0500
Pat Erley <pat...@ma...> wrote:

> here's a basic patch to add cobd devfs support.  It's not 100% perfect, and I plan on getting it up to working with a /dev/cobd/ dir and symlink to it as the devices exist...
> 
> Pat Erley
> 

NOTE:

this applies on top of the 'linux' patch included with the colinux source

Pat Erley

[coLinux-devel] cobd devfs support

[Pat E. <pat...@ma...>]

here's a basic patch to add cobd devfs support.  It's not 100% perfect, and I plan on getting it up to working with a /dev/cobd/ dir and symlink to it as the devices exist...

Pat Erley