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: Daniel <dan...@gm...> - 2004-02-06 19:03:41
|
The source of this bug is a typo in fileblock.c. Where it says if (CO_RC(OK)) it should be if (CO_OK(rc)) Daniel |
|
From: Richard G. <ric...@ri...> - 2004-02-06 18:11:37
|
I hope you know my wife will be mad at you because now I have to play with this tomorrow instead of household chores :-) Thanks Dan!! ----- Original Message ----- From: "Dan Aloni" <da...@gm...> To: "Cooperative Linux Development" <col...@li...> Sent: Friday, February 06, 2004 11:49 AM Subject: [coLinux-devel] The upcoming release > Hello, > > Amongst the changes for tomorrow's release, we have: > > * The daemon is killable like any other Windows process. Closing it, > CTRL-C, or ending the task, will all cleanly shutdown the Linux > system. > * printk()s are routed to the output of the colinux-daemon box, so you > can see the kernel as it boots without opening the console. > * Some fixes, especially for that BSOD bug lots of you have seen on > startup, and for the network packet corruption issue. > * The build doesn't depend anymore on the Microsoft DDK. > * Overall design improvements. > > Stay tooned. > > -- > Dan Aloni > da...@gm... > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > |
|
From: Thomas F. <tf...@no...> - 2004-02-06 18:05:54
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi coLinux-Hackers, here is just an other installation report. I started with the latest (and only) coLinux binary and added the colinux-daemon-replacement1. My System in win2000 SP4. I installed the system as described in the README file and started the colinux-daemon from a MSDOS window: ... Cooperative Linux daemon Installing kernel driver Creating monitor Monitor is running ... Ok, this is fine. I then started the colinux-console and connect .... YES! I'll see Linux running. Amazing! Excellent work! So far so good. But I also can confirm some errors reported on this list. First is the fsck reports a error message, so I disabled the rootcheck for the further steps. Then started with the basic system configuration and yes there are little display problems with the colinux-console but its good enough to setup the first basic steps and I later switched to ssh (putty). So I setup networking. I just enabled "Internet Connection Sharing" in the configuration of my LAN and that was all. IP-Host: 192.168.0.1 (Connection Sharing) IP-coLinux: 192.168.0.40 I then installed ssh with apt-get and I can confirm the network problems reported on this list. Sometimes it takes 5-6 times to get a package without md5sum errors. If I transfer larger files this problem appears more often. But this errors happens also with files < 1MB and sometimes I can transfer files larger the 1MB. I tried to install locales package but this is 3.3MB and with this size I get always md5sum errors. Maybe I should try this other TAB-Win32 driver that was discussed on the list. Any success with this driver? One other thing I see while installing with apt-get is that tar sends warnings abount date/time. System date is 1-jan-1970 = 0. Ok maybe I have to setup here something that the unix date/time is set by the host date/time or maybe this is still missing in this early stage of the colinux development. If I'll find no other solution I will try to get the current date/time from the network. I then tryed to attach a swap device as an extra cobd1 device. This works without a problem. I connected with putty and get the login prompt. Then a long pause (10-20 sec.) and then the password prompt. Is this long pause normal? I then tried to shutdown system with command "shutdown -h now". The terminal gets closed but the daemon is still running. I din't know what to do know, because I can't reconnect, so I just closed the MSDOS window I used to run the daemon. That was not a good idea I shortly receive a blue screen and some error messages about linux.sys. Because this is such a miracle that linux can run such easy within windows that I expected this kind of error much earlier. So I read again in this list and found command "shutdown -g0 -y -i0" and this works without problem... putty window gets closed and the daemon reports: Monitor shutting down Closing monitor Removing kernel driver Stopping driver service Removing driver service Conclusion: Very good work for the first release. Amazing what is possible. The biggest problem (for me) so far is the network issue because this is holding me back to install more packages. Next importend is the fsck problem. There is a workaround but to disable the check could only be a temporary solution. Less importend are the date/time, shutdown and terminal problems. Thanks to all the coLinux hackers that made this possible! Thanks and kind regards, Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAI9iWnwJBIFTVIqwRAvbIAJ0aFHTk2wPpyZOFEZn7J90xG5UlNgCfRfNN J5K8TJycJOSIR+b948mrui0= =8nXx -----END PGP SIGNATURE----- |
|
From: Dan A. <da...@gm...> - 2004-02-06 17:50:02
|
Hello,
Amongst the changes for tomorrow's release, we have:
* The daemon is killable like any other Windows process. Closing it,
CTRL-C, or ending the task, will all cleanly shutdown the Linux
system.
* printk()s are routed to the output of the colinux-daemon box, so you
can see the kernel as it boots without opening the console.
* Some fixes, especially for that BSOD bug lots of you have seen on
startup, and for the network packet corruption issue.
* The build doesn't depend anymore on the Microsoft DDK.
* Overall design improvements.
Stay tooned.
--
Dan Aloni
da...@gm...
|
|
From: Dan A. <da...@gm...> - 2004-02-06 16:33:53
|
On Fri, Feb 06, 2004 at 05:25:54PM +0100, Daniel Gl?ckner wrote: > It's not the tap driver. > > This happens when memcpy in conet_rx is interrupted by another > co_handle_device_interrupt which overwrites conet_frame. Good spotting! I'll look into this and produce a fix for the next release. -- Dan Aloni da...@gm... |
|
From: Daniel <dan...@gm...> - 2004-02-06 16:26:06
|
It's not the tap driver. This happens when memcpy in conet_rx is interrupted by another co_handle_device_interrupt which overwrites conet_frame. Daniel |
|
From: Dan A. <da...@gm...> - 2004-02-06 15:19:46
|
On Fri, Feb 06, 2004 at 08:59:12AM -0600, Richard Goodwin wrote: > Mine would never get past where it was Initializing System (or something > such) on the K splash screen. I assuemd it had something to do with sound so > I just let it lay. Should I revisit? There is currently a scheduling issue in coLinux. CPU-hungry processes somehow get prioritized. KDE's artsd is one example. However, I noticed that it has a watchdog which kills it if it takes too much CPU. -- Dan Aloni da...@gm... |
|
From: Ian C. B. <ia...@bl...> - 2004-02-06 15:12:20
|
On Fri, Feb 06, 2004 at 08:59:12AM -0600, Richard Goodwin wrote: > Mine would never get past where it was Initializing System (or something > such) on the K splash screen. I assuemd it had something to do with sound so > I just let it lay. Should I revisit? Try sshing in and killing off the "arts" daemon. I'll give it a go here in a bit myself on a colinux image to help walk through it. - Ian C. Blenke <ia...@bl...> |
|
From: Dan A. <da...@gm...> - 2004-02-06 15:06:30
|
On Fri, Feb 06, 2004 at 09:55:37AM -0500, Matt Behrens wrote: > The cygwin cross notes say binutils 2.14 is bad, but latest in > testing/unstable is 2.14.90 -- shall I use 2.12.90 from stable > instead? You can use binutils 2.14. I experienced some problems while writing the notes, but later it turned out to be not related to binutils. -- Dan Aloni da...@gm... |
|
From: Gregor M. <mi...@ra...> - 2004-02-06 15:01:23
|
Hi, > You can setup another cobd0 device as a swap deivce. Use mkswap and dd. $ mount -t vfat /devhda /mnt/windows --> mount: fs type not supproted by kernel $ modprobe --> modprobe: Can't open dependencies file /lib/moduels/2.2.24/modules.dep (No such file or directory) Do I have to recompile the kernel? Or is there another way? Regards, Gregor -- | Gregor Mitsch | | www.gmdsoft.de/mitsch | |
|
From: Richard G. <ric...@ri...> - 2004-02-06 14:59:11
|
Mine would never get past where it was Initializing System (or something such) on the K splash screen. I assuemd it had something to do with sound so I just let it lay. Should I revisit? ----- Original Message ----- From: "Ian C. Blenke" <ia...@bl...> To: "Vinay Kumar" <lvi...@ho...> Cc: <col...@li...> Sent: Friday, February 06, 2004 6:44 AM Subject: Re: [coLinux-devel] How to start KDE on Colinux > On Fri, Feb 06, 2004 at 03:26:57AM -0500, Vinay Kumar wrote: > > Does any have idea how to start KDE on colinux > > First, install kde - I recommend the latest 3.2 from kde.org: > > host$ ssh root@192.168.1.40 > colinux# echo "deb http://download.kde.org/stable/3.2/Debian stable main" >> /etc/apt/sources.list > colinux# apt-get update > colinux# apt-get install kde xbase-clients > > The xbase-clients bit is important for xauth. Now, use X11 forwarding over SSH: > > host$ export DISPLAY=:0.0 > host$ ssh -X 192.168.1.40 > colinux$ startkde > > Alternatively, you can install the kdm package, edit the Xservers file > to comment out the local execution of a display and Xaccess file to > permit access from anywhere ("*"), then run kdm. This will allow you to > pull up a XDMCP queried session from your host's X server. > > Hope this helps. > > - Ian C. Blenke <ia...@bl...> > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > |
|
From: Matt B. <ma...@zi...> - 2004-02-06 14:55:57
|
The cygwin cross notes say binutils 2.14 is bad, but latest in testing/unstable is 2.14.90 -- shall I use 2.12.90 from stable instead? --=20 Matt Behrens <ma...@zi...> <http://www.zigg.com/> Life's too short to recompile what you don't hack. <http://www.debian.org/> |
|
From: Ian C. B. <ia...@bl...> - 2004-02-06 12:45:17
|
On Fri, Feb 06, 2004 at 03:26:57AM -0500, Vinay Kumar wrote: > Does any have idea how to start KDE on colinux First, install kde - I recommend the latest 3.2 from kde.org: host$ ssh root@192.168.1.40 colinux# echo "deb http://download.kde.org/stable/3.2/Debian stable main" >> /etc/apt/sources.list colinux# apt-get update colinux# apt-get install kde xbase-clients The xbase-clients bit is important for xauth. Now, use X11 forwarding over SSH: host$ export DISPLAY=:0.0 host$ ssh -X 192.168.1.40 colinux$ startkde Alternatively, you can install the kdm package, edit the Xservers file to comment out the local execution of a display and Xaccess file to permit access from anywhere ("*"), then run kdm. This will allow you to pull up a XDMCP queried session from your host's X server. Hope this helps. - Ian C. Blenke <ia...@bl...> |
|
From: Thomas F. <tf...@no...> - 2004-02-06 11:31:23
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Dan Aloni and Linux-Hackers, this is realy good news. This gives me a chance to build this projekt from source. But because I never used a (Linux-->Windows) cross compiler I have a stupid "user-questions". I started building the cross compiler as described in the document "cygwin-cross-build" and I understand, that I should first patch win32api before building coLinux with it. But I'm still a little bit confused about the mix of cygwin libs and mingw libs. Why not just use mingw? Are there dependencys in the project that can't be resolved? Thanks and regards, Thomas > Good evening, > > I've successfully managed to build and test linux.sys using the GNU > toolchain. I used ReactOS's helper.mk, pointed by Steven Edwards to > generated the rather complex command line sequence that achieves this > goal (look at the patch below). > > Thanks for Nir Perry for encouraging me to try this method further than > I thought. > > Next coLinux release can be built on a Linux box entirely, using the GNU > toolchain. However, w32api needs to be patched and built from source, > because there is a mistake in one of the kernel imports defined there > (I'm mailing the author). > > Would one of you like me to maintain precompiled binaries of a cygwin > cross build tools for Linux, as .deb and/or .rpm files, so that the > others won't have to mess with setting up this build environment? > > > --- colinux-20040131/src/colinux/os/winnt/build/Makefile 2004-01-31 > 18:57:08.000000000 +0200 > +++ colinux-20040204/src/colinux/os/winnt/build/Makefile 2004-02-05 > 00:11:27.000000000 +0200 > @@ -21,47 +21,30 @@ > > DRIVER_TARGET := $(BUILD_PATH)/linux.sys > > -WINDIR=$(WINUSER)@$(WINBOX):$(WINREMOTEDIR) > -WINBOX_SCP=scp -i ~/.ssh/locallan > -WINBOX_SSH=ssh -X -l $(WINUSER) -i ~/.ssh/locallan $(WINBOX) > -WINLINK=$(WINBOX_SSH) /cygdrive/c/NTDDK/bin/link.exe > - > -WINLINK_FLAGS= \ > - /machine:ix86 \ > - /STACK:262144,4096 \ > - /MERGE:_PAGE=PAGE \ > - /MERGE:_TEXT=.text \ > - /SECTION:INIT,d \ > - /OPT:REF \ > - /OPT:ICF \ > - /IGNORE:4001,4037,4039,4044,4065,4070,4078,4087,4089,4198 \ > - /INCREMENTAL:NO \ > - /FULLBUILD \ > - /FORCE:MULTIPLE \ > - /NOCOMMENT \ > - /release \ > - /NODEFAULTLIB \ > - /debug:FULL \ > - /debugtype:cv \ > - /version:5.00 \ > - /osversion:5.00 \ > - /optidata \ > - /driver \ > - /align:0x1000 \ > - /filealign:0x1000 \ > - /subsystem:native,5.00 \ > - /base:0x10000 \ > - /entry:DriverEntry@8 \ > - > -WINLINK_LIBS= \ > - C:\\\\NTDDK\\\\libfre\\\\i386\\\\ntoskrnl.lib \ > - C:\\\\NTDDK\\\\libfre\\\\i386\\\\hal.lib \ > - C:\\\\NTDDK\\\\libfre\\\\i386\\\\wmilib.lib \ > - > -$(DRIVER_TARGET): $(BUILD_PATH)/driver.o > - $(WINBOX_SCP) $^ $(WINDIR) > - $(WINLINK) /out:$(notdir $@) $(WINLINK_FLAGS) $(notdir $^) > $(WINLINK_LIBS) > - $(WINBOX_SCP) $(WINDIR)$(notdir $@) $@ > +CLEAN_FILES += $(BUILD_PATH)/driver.base.tmp > +$(BUILD_PATH)/driver.base.tmp: $(BUILD_PATH)/driver.o > + i686-pc-cygwin-gcc -Wl,--base-file,$@ \ > + -Wl,--entry,_DriverEntry@8 \ > + -nostartfiles -nostdlib \ > + -o junk.tmp $^ -lntoskrnl -lhal > + rm -f junk.tmp > + > +CLEAN_FILES += $(BUILD_PATH)/driver.base.exp > +$(BUILD_PATH)/driver.base.exp: $(BUILD_PATH)/driver.base.tmp > + i686-pc-cygwin-dlltool --dllname linux.sys \ > + --base-file $^ \ > + --output-exp $@ > + > +$(DRIVER_TARGET): $(BUILD_PATH)/driver.o $(BUILD_PATH)/driver.base.exp > + i686-pc-cygwin-gcc \ > + -Wl,--subsystem,native \ > + -Wl,--image-base,0x10000 \ > + -Wl,--file-alignment,0x1000 \ > + -Wl,--section-alignment,0x1000 \ > + -Wl,--entry,_DriverEntry@8 \ > + -Wl,$(word 2,$^) \ > + -mdll -nostartfiles -nostdlib \ > + -o $@ $(word 1,$^) -lntoskrnl -lhal > > LOCAL_TARGET += $(DRIVER_TARGET) > LOCAL_FILES = \ > @@ -74,16 +57,7 @@ > > colinux: $(LOCAL_FILES) > > -parts: $(LOCAL_FILES) > - > -upload: $(LOCAL_FILES) > - $(WINBOX_SCP) $^ $(WINDIR) > - > -upload_console: > $(BUILD_ROOT)/colinux/os/current/user/console/colinux-console.exe > - $(WINBOX_SCP) $^ $(WINDIR) > - > driver: $(BUILD_PATH)/driver.o > - > > CLEAN_FILES := $(CLEAN_FILES) \ > $(LOCAL_TARGETS) > > > Here's the patch against w32api: > > --- w32api-2.4/lib/ddk/ntoskrnl.def 2003-02-09 15:26:01.000000000 +0200 > +++ w32api-2.4-patched/lib/ddk/ntoskrnl.def 2004-02-04 23:40:02.000000000 > +0200 > @@ -596,8 +596,8 @@ > KeSetTargetProcessorDpc@8 > ;KeSetTimeIncrement > @KeSetTimeUpdateNotifyRoutine@4 > -KeSetTimer@12 > -KeSetTimerEx@16 > +KeSetTimer@16 > +KeSetTimerEx@20 > ;KeStackAttachProcess > KeSynchronizeExecution@12 > ;KeTerminateThread > > -- > Dan Aloni > da...@gm... > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAI3wbnwJBIFTVIqwRAmoMAJ40NHrR7tv8CZFAItS5fp5qf8dbfgCguqqh 4jXdjM//cXrKDz+hA+Vxrfk= =q8Ko -----END PGP SIGNATURE----- |
|
From: Andrei D. <adr...@ia...> - 2004-02-06 10:11:15
|
Hi,
I have downloaded coLinux, and succeeded in running, but i have two
problems (have searched the mailing lists prior to this):
1. when mounting: i have the well known image error, but i haven;t been able
to find any info on how to mount the disk image read/write, or a link to a
patched disk image.
2. when exiting: press Ctrl + c in windows console, coLinux shuts down, but
in task management, the colinux-daemon process is still running, and "End
task" doesn't work.
Any help on any of the above would be highly appreciated
Thanks in advance, Andrei
|
|
From: Vinay K. <lvi...@ho...> - 2004-02-06 08:26:57
|
Does any have idea how to start KDE on colinux Thanks -Vinay |
|
From: John L. <jo...@su...> - 2004-02-06 06:51:14
|
When using ssh to transfer large files, or run real x apps, I've been getting "Corrupted MAC on Input" errors. I've looked around the net to see what might cause this, and apparently, the MAC here is not the MAC address, but a CRC like mechanism that ssh uses to ensure data integrity. Most seem to claim that the problem comes from either corrupted buffers on the NIC itself(since it passed the CRC test) or poor memory handling in the network driver. I'm guessing that the TAP driver might need a little tweaking somewhere, does someone here know anything about it? I might just see if I can look into the code myself, but I'm no networking hacker... Also, I find it interesting that some people seem not to see this at all. I'm running windows 2000 professional here. Maybe the tap driver behaves a little differently? Below are some tests that I ran. John LeSueur I've been trying to determine what's causing network errors, on large files, or at least get some kind of info about it, so I did the following tests. using netcat, I made the following test: in colinux: nc -l -p 6434 | dd of=kernel-source-2.4.24_2.4.24-1_all.deb on a redhat machine: nc 192.168.0.40 6434 < kernel-source-2.4.24_2.4.24-1_all.deb Then did an md5sum on the resulting transferred file original: 1e7f3309aca976167648c8a813128021 kernel-source-2.4.24_2.4.24-1_all.deb transferred to colinux: 7c2e08ac025865f8195a952170718e8b kernel-source-2.4.24_2.4.24-1_all.deb file sizes are exactly the same. Then to see if corruption is random(very likely), I transferred the same files again. original: 1e7f3309aca976167648c8a813128021 kernel-source-2.4.24_2.4.24-1_all.deb colinux: c969f5caaa6302b2f7a63c9ca3842e0d kernel-source.deb To make sure that it's not inside the kernel that we have errors(ha!), I ran in colinux: nc -l -p 6434 | dd of=kernel-source-2.4.24_2.4.24-1_all.deb2 in colinux: nc 127.0.0.1 6434 < kernel-source-2.4.24_2.4.24-1_all.deb files are the same. |
|
From: John L. <jo...@su...> - 2004-02-06 06:46:32
|
Vinay Kumar wrote: >I am getting ext3 filesystem error . I am very new to linux so and I >don't have a acess to linux system. So is there any way I could fix this >error > >The error is like > >fsck 1.27 >The filesystem size ( according to the superblock ) .......... > >Thanks in advance >-Vinay > > There is a known bug somewhere that causes this, Dan could tell you more, but the workaround is to disable the check of the root filesystem at boot. To do this, follow the instructions to remount the drive read-write, then use nano to edit /etc/init.d/checkroot.sh. Find the line that looks like rootcheck=yes and change it to rootcheck=no John |
|
From: Vinay K. <lvi...@ho...> - 2004-02-06 06:29:04
|
I am getting ext3 filesystem error . I am very new to linux so and I don't have a acess to linux system. So is there any way I could fix this error The error is like fsck 1.27 The filesystem size ( according to the superblock ) .......... Thanks in advance -Vinay |
|
From: Dan A. <da...@gm...> - 2004-02-06 01:31:01
|
On Thu, Feb 05, 2004 at 11:33:25PM +0100, Gregor Mitsch wrote: > Hi John! > > >Once you have the lan and the tap in the bridge, and colinux started, > >try using > >route add default gw 192.168.0.254 > > YEAH! It works! > > Thanks for your help!!! > > Now I'm stuck at another thing. It seems that the coLinux Debian has > very little main memory. Bigger programs don't work. Sometimes apt-get > quits because of insufficient memory. If I gnome2 is running apt does > not work at all. Is that the normal case? You can setup another cobd0 device as a swap deivce. Use mkswap and dd. -- Dan Aloni da...@gm... |
|
From: Gregor M. <mi...@ra...> - 2004-02-05 22:54:26
|
Hi John! > Once you have the lan and the tap in the bridge, and colinux started, > try using > route add default gw 192.168.0.254 YEAH! It works! Thanks for your help!!! Now I'm stuck at another thing. It seems that the coLinux Debian has very little main memory. Bigger programs don't work. Sometimes apt-get quits because of insufficient memory. If I gnome2 is running apt does not work at all. Is that the normal case? I'm using debian-testing. My machine has got 512 MB of physical RAM. Gregor -- | Gregor Mitsch | | www.gmdsoft.de/mitsch | |
|
From: Richard G. <ric...@ri...> - 2004-02-05 17:36:41
|
Hot on the heels of my last email, I found the section where it is disabled. Oh well, it shall have to be a proxy for me, so I'll sit back and wait for the next cL release... Thanks! ----- Original Message ----- From: "Robert" <ro...@ar...> To: "Richard Goodwin" <ric...@ri...> Cc: "Cooperative Linux Development" <col...@li...> Sent: Thursday, February 05, 2004 11:34 AM Subject: Re: [coLinux-devel] TCP Forwarding? Or General Networking Questions..? > There is a likelyhood that an admin would disable ICS by AD policy. It's a bit nasty to have a PC in a network competing with your "proper" DHCP server. > > Robert. > > Richard Goodwin wrote: > > Weird.. > > I'll dig up the MS KB article that I found that basically said "ICS is not > available when a machine is part of a domain". If that's not true, then it > must be that the admins-that-be feel that I shouldn't be allowed to enable > ICS ;-) > > ----- Original Message ----- > From: "Tony Hoyle" <tm...@no...> > To: "Tony Hoyle" <tm...@no...> > Cc: "Richard Goodwin" <ric...@ri...>; "Ian C. Blenke" > <ia...@bl...>; "Cooperative Linux Development" > <col...@li...> > Sent: Thursday, February 05, 2004 11:11 AM > Subject: Re: [coLinux-devel] TCP Forwarding? Or General Networking > Questions..? > > > Tony Hoyle wrote: > Bridging is there... I'm in a domain at the moment and right clicking on > the adapter has a 'bridge connections' option. > Internet connection sharing is there too, on the same page as the > internet connection firewall. > > Tony > > > > > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > |
|
From: Robert <ro...@ar...> - 2004-02-05 17:34:43
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
There is a likelyhood that an admin would disable ICS by AD policy.
It's a bit nasty to have a PC in a network competing with your "proper"
DHCP server.<br>
<br>
Robert.<br>
<br>
Richard Goodwin wrote:<br>
<blockquote cite="mid02c401c3ec0d$1208ea50$647ba8c0@beeners" type="cite">
<pre wrap="">Weird..
I'll dig up the MS KB article that I found that basically said "ICS is not
available when a machine is part of a domain". If that's not true, then it
must be that the admins-that-be feel that I shouldn't be allowed to enable
ICS ;-)
----- Original Message -----
From: "Tony Hoyle" <a class="moz-txt-link-rfc2396E" href="mailto:tm...@no..."><tm...@no...></a>
To: "Tony Hoyle" <a class="moz-txt-link-rfc2396E" href="mailto:tm...@no..."><tm...@no...></a>
Cc: "Richard Goodwin" <a class="moz-txt-link-rfc2396E" href="mailto:ric...@ri..."><ric...@ri...></a>; "Ian C. Blenke"
<a class="moz-txt-link-rfc2396E" href="mailto:ia...@bl..."><ia...@bl...></a>; "Cooperative Linux Development"
<a class="moz-txt-link-rfc2396E" href="mailto:col...@li..."><col...@li...></a>
Sent: Thursday, February 05, 2004 11:11 AM
Subject: Re: [coLinux-devel] TCP Forwarding? Or General Networking
Questions..?
</pre>
<blockquote type="cite">
<pre wrap="">Tony Hoyle wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Bridging is there... I'm in a domain at the moment and right clicking on
the adapter has a 'bridge connections' option.
</pre>
</blockquote>
<pre wrap="">Internet connection sharing is there too, on the same page as the
internet connection firewall.
Tony
</pre>
</blockquote>
<pre wrap=""><!---->
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
<a class="moz-txt-link-freetext" href="http://www.eclipsecon.org/osdn">http://www.eclipsecon.org/osdn</a>
_______________________________________________
coLinux-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:coL...@li...">coL...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/colinux-devel">https://lists.sourceforge.net/lists/listinfo/colinux-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>
|
|
From: Richard G. <ric...@ri...> - 2004-02-05 17:25:37
|
Weird.. I'll dig up the MS KB article that I found that basically said "ICS is not available when a machine is part of a domain". If that's not true, then it must be that the admins-that-be feel that I shouldn't be allowed to enable ICS ;-) ----- Original Message ----- From: "Tony Hoyle" <tm...@no...> To: "Tony Hoyle" <tm...@no...> Cc: "Richard Goodwin" <ric...@ri...>; "Ian C. Blenke" <ia...@bl...>; "Cooperative Linux Development" <col...@li...> Sent: Thursday, February 05, 2004 11:11 AM Subject: Re: [coLinux-devel] TCP Forwarding? Or General Networking Questions..? > Tony Hoyle wrote: > > > > Bridging is there... I'm in a domain at the moment and right clicking on > > the adapter has a 'bridge connections' option. > > Internet connection sharing is there too, on the same page as the > internet connection firewall. > > Tony > > > > > |
|
From: Tony H. <tm...@no...> - 2004-02-05 17:11:35
|
Tony Hoyle wrote: > > Bridging is there... I'm in a domain at the moment and right clicking on > the adapter has a 'bridge connections' option. Internet connection sharing is there too, on the same page as the internet connection firewall. Tony |
81 messages has been excluded from this view by a project administrator.
