Menu
▾
▴
devil-linux-develop — developer discussions
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(55) |
Oct
(44) |
Nov
(156) |
Dec
(123) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(130) |
Feb
(156) |
Mar
(162) |
Apr
(171) |
May
(97) |
Jun
(127) |
Jul
(58) |
Aug
(81) |
Sep
(86) |
Oct
(45) |
Nov
(41) |
Dec
(84) |
| 2003 |
Jan
(71) |
Feb
(87) |
Mar
(133) |
Apr
(152) |
May
(151) |
Jun
(232) |
Jul
(320) |
Aug
(237) |
Sep
(271) |
Oct
(536) |
Nov
(301) |
Dec
(393) |
| 2004 |
Jan
(393) |
Feb
(184) |
Mar
(314) |
Apr
(225) |
May
(139) |
Jun
(77) |
Jul
(87) |
Aug
(75) |
Sep
(139) |
Oct
(50) |
Nov
(8) |
Dec
(28) |
| 2005 |
Jan
(66) |
Feb
(63) |
Mar
(14) |
Apr
(14) |
May
(8) |
Jun
(23) |
Jul
(21) |
Aug
(6) |
Sep
(29) |
Oct
(55) |
Nov
(38) |
Dec
(8) |
| 2006 |
Jan
(5) |
Feb
(10) |
Mar
(1) |
Apr
(15) |
May
(32) |
Jun
(44) |
Jul
(11) |
Aug
(8) |
Sep
(9) |
Oct
(14) |
Nov
(4) |
Dec
(3) |
| 2007 |
Jan
(3) |
Feb
(3) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(35) |
Aug
(49) |
Sep
(8) |
Oct
(42) |
Nov
(44) |
Dec
(7) |
| 2008 |
Jan
(2) |
Feb
(7) |
Mar
(8) |
Apr
(80) |
May
(74) |
Jun
(29) |
Jul
(5) |
Aug
(7) |
Sep
(6) |
Oct
(1) |
Nov
|
Dec
|
| 2009 |
Jan
(8) |
Feb
(19) |
Mar
(3) |
Apr
(24) |
May
(22) |
Jun
(23) |
Jul
(8) |
Aug
(23) |
Sep
(8) |
Oct
(27) |
Nov
(52) |
Dec
(27) |
| 2010 |
Jan
(36) |
Feb
(29) |
Mar
(17) |
Apr
(28) |
May
(21) |
Jun
(4) |
Jul
|
Aug
(28) |
Sep
(18) |
Oct
(6) |
Nov
(34) |
Dec
(16) |
| 2011 |
Jan
(18) |
Feb
(12) |
Mar
|
Apr
|
May
(9) |
Jun
(1) |
Jul
(5) |
Aug
(5) |
Sep
(7) |
Oct
(16) |
Nov
(26) |
Dec
(17) |
| 2012 |
Jan
(6) |
Feb
(34) |
Mar
(52) |
Apr
(10) |
May
(3) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(4) |
Nov
(1) |
Dec
(4) |
| 2013 |
Jan
(5) |
Feb
|
Mar
|
Apr
(5) |
May
(4) |
Jun
|
Jul
|
Aug
(14) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
(2) |
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(11) |
| 2015 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2004-07-22 13:30:49
|
Feature Requests item #995916, was opened at 2004-07-22 08:30 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=995916&group_id=34096 Category: Packages Group: None Status: Open Priority: 5 Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: add DVD+RW tools Initial Comment: http://fy.chalmers.se/~appro/linux/DVD+RW/tools/ What are the dvd+rw-tools for? A. As implied/already mentioned - to master the DVD media, both +RW/+R and -R[W]. I could simply refer to the tutorial below, but figured that couple of words about the [original] design ideas behind growisofs, the principal burning utility, wouldn't harm. Even though a modified kernel can let you put for example an ext2 file system on DVD+RW, it's probably not very practical, because you most likely want to access the data on an arbitrary computer. Or in other words you most likely want ISO9660. The trouble is that you might as well want to add data now and then. And what options do you have in the lack of multiple sessions (no, DVD+RW has no notion of multiple sessions)? Complete re- mastering which takes more and more time as data set grows? Well, yes, unless you employ growisofs! Growisofs provides the way to both lay down and grow an ISO9660 file system on (as well as to burn an arbitrary pre-mastered image to) all supported DVD media. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=995916&group_id=34096 |
|
From: Bruce S. <bw...@ar...> - 2004-07-22 13:06:35
|
> > > I can check in a few changes if you want, which should take care of this
> > > problem.
> > > I didn't do it yet because of my build problems. So at least you can test it.
> >
> > OK. Check them in and I'll start another compile tonight.
>
> DONE, it's all in CVS now.
Still hangs waiting for input:
*
* I2C support
*
I2C support (CONFIG_I2C) [M/n/y/?]
I2C bit-banging interfaces (CONFIG_I2C_ALGOBIT) [M/n/?]
Philips style parallel port adapter (CONFIG_I2C_PHILIPSPAR) [M/n/?]
ELV adapter (CONFIG_I2C_ELV) [M/n/?]
Velleman K8000 adapter (CONFIG_I2C_VELLEMAN) [M/n/?]
NatSemi SCx200 I2C using GPIO pins (CONFIG_SCx200_I2C) [M/n/?]
GPIO pin used for SCL (CONFIG_SCx200_I2C_SCL) [12] (NEW)
|
|
From: Serge L. <se...@nn...> - 2004-07-22 05:41:46
|
Hello Heiko, Wednesday, July 21, 2004, 4:34:01 PM, you wrote: HZ> I tried 1.2 and 1.3. I expect you did compile for Kernel 2.4 ? Yes. DL has 2.4, host system - 2.6 -- Best regards, Serge mailto:se...@nn... |
|
From: Heiko Z. <he...@zu...> - 2004-07-21 23:41:24
|
On Wed, 2004-07-21 at 18:12, Bruce Smith wrote: > > > * > > > * I2C support > > > * > > > I2C support (CONFIG_I2C) [M/n/y/?] > > > I2C bit-banging interfaces (CONFIG_I2C_ALGOBIT) [M/n/?] > > > Philips style parallel port adapter (CONFIG_I2C_PHILIPSPAR) [M/n/?] > > > ELV adapter (CONFIG_I2C_ELV) [M/n/?] > > > Velleman K8000 adapter (CONFIG_I2C_VELLEMAN) [M/n/?] > > > NatSemi SCx200 I2C using GPIO pins (CONFIG_SCx200_I2C) [M/n/?] > > > GPIO pin used for SCL (CONFIG_SCx200_I2C_SCL) [12] (NEW) > > > > Are u using 1.3 ? > > Yes. > > > I can check in a few changes if you want, which should take care of this > > problem. > > I didn't do it yet because of my build problems. So at least you can test it. > > OK. Check them in and I'll start another compile tonight. DONE, it's all in CVS now. -- Regards Heiko http://www.devil-linux.org |
|
From: Bruce S. <bw...@ar...> - 2004-07-21 22:12:01
|
> > * > > * I2C support > > * > > I2C support (CONFIG_I2C) [M/n/y/?] > > I2C bit-banging interfaces (CONFIG_I2C_ALGOBIT) [M/n/?] > > Philips style parallel port adapter (CONFIG_I2C_PHILIPSPAR) [M/n/?] > > ELV adapter (CONFIG_I2C_ELV) [M/n/?] > > Velleman K8000 adapter (CONFIG_I2C_VELLEMAN) [M/n/?] > > NatSemi SCx200 I2C using GPIO pins (CONFIG_SCx200_I2C) [M/n/?] > > GPIO pin used for SCL (CONFIG_SCx200_I2C_SCL) [12] (NEW) > > Are u using 1.3 ? Yes. > I can check in a few changes if you want, which should take care of this > problem. > I didn't do it yet because of my build problems. So at least you can test it. OK. Check them in and I'll start another compile tonight. - BS |
|
From: Heiko Z. <he...@zu...> - 2004-07-21 21:35:17
|
> New LFS, mrproper. The lm_sensors script hangs waiting for input. > Here's a tail of the log file: > > > > * > * I2C support > * > I2C support (CONFIG_I2C) [M/n/y/?] > I2C bit-banging interfaces (CONFIG_I2C_ALGOBIT) [M/n/?] > Philips style parallel port adapter (CONFIG_I2C_PHILIPSPAR) [M/n/?] > ELV adapter (CONFIG_I2C_ELV) [M/n/?] > Velleman K8000 adapter (CONFIG_I2C_VELLEMAN) [M/n/?] > NatSemi SCx200 I2C using GPIO pins (CONFIG_SCx200_I2C) [M/n/?] > GPIO pin used for SCL (CONFIG_SCx200_I2C_SCL) [12] (NEW) Are u using 1.3 ? I can check in a few changes if you want, which should take care of this problem. I didn't do it yet because of my build problems. So at least you can test it. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Bruce S. <bw...@ar...> - 2004-07-21 21:16:20
|
New LFS, mrproper. The lm_sensors script hangs waiting for input.
Here's a tail of the log file:
*
* I2C support
*
I2C support (CONFIG_I2C) [M/n/y/?]
I2C bit-banging interfaces (CONFIG_I2C_ALGOBIT) [M/n/?]
Philips style parallel port adapter (CONFIG_I2C_PHILIPSPAR) [M/n/?]
ELV adapter (CONFIG_I2C_ELV) [M/n/?]
Velleman K8000 adapter (CONFIG_I2C_VELLEMAN) [M/n/?]
NatSemi SCx200 I2C using GPIO pins (CONFIG_SCx200_I2C) [M/n/?]
GPIO pin used for SCL (CONFIG_SCx200_I2C_SCL) [12] (NEW)
|
|
From: SourceForge.net <no...@so...> - 2004-07-21 14:13:12
|
Feature Requests item #995257, was opened at 2004-07-21 09:13 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=995257&group_id=34096 Category: Packages Group: None Status: Open Priority: 5 Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: add nfs client Initial Comment: add nfs client ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=995257&group_id=34096 |
|
From: Heiko Z. <he...@zu...> - 2004-07-21 14:01:18
|
>> >> > I'm running SuSE 9.1 (2.6 kernel based), and haven't had any >> problems >> >> > compiling a 2.4 DL, but I haven't tried compiling a 2.6 DL. >> >> >> >> It's probably worth a try with SuSE 9.1. >> > >> > I can run a 2.6 compile on SuSE 9.1 and see what happens. What >> should, >> > or shouldn't I select in menuconfig? Is there a profile for 2.6? >> >> No need for this, but thanks anyway. >> The 2.6 compile is not stable yet, I actually had on my list for this >> week >> to fix most of the problems there. >> But as I mentioned, the 2.4 compile *must* work... > > I haven't had any problems compiling 2.4 DL on SuSE 9.1. I haven't > run a full compile for a couple weeks, but I plan on running a full > mrproper/new-lfs soon for a new DL box I need to install. > > I can let you know how it goes ... That would be great. >> I'm currently downloading the personal edition of suse 9.1, this is >> enough >> to do some testing. > > All the RPM's are available for SuSE 9.1 professional. You can do an > install of professional over the internet. Or, I've heard that you can > install the personal edition and then download/install the professional > RPM's if needed. That sounds interesting, I'll take a look at it tonight. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Bruce S. <bw...@ar...> - 2004-07-21 13:48:07
|
> >> > I'm running SuSE 9.1 (2.6 kernel based), and haven't had any problems > >> > compiling a 2.4 DL, but I haven't tried compiling a 2.6 DL. > >> > >> It's probably worth a try with SuSE 9.1. > > > > I can run a 2.6 compile on SuSE 9.1 and see what happens. What should, > > or shouldn't I select in menuconfig? Is there a profile for 2.6? > > No need for this, but thanks anyway. > The 2.6 compile is not stable yet, I actually had on my list for this week > to fix most of the problems there. > But as I mentioned, the 2.4 compile *must* work... I haven't had any problems compiling 2.4 DL on SuSE 9.1. I haven't run a full compile for a couple weeks, but I plan on running a full mrproper/new-lfs soon for a new DL box I need to install. I can let you know how it goes ... > I'm currently downloading the personal edition of suse 9.1, this is enough > to do some testing. All the RPM's are available for SuSE 9.1 professional. You can do an install of professional over the internet. Or, I've heard that you can install the personal edition and then download/install the professional RPM's if needed. - BS |
|
From: Heiko Z. <he...@zu...> - 2004-07-21 13:36:20
|
>> >> > HZ> is anybody compiling DL under Fedora Core 2 ? >> >> > Yes I am. >> >> > HZ> I just upgraded 2 boxes and now I have all kinds of problems... >> >> > I have no problem (1.2 only) >> >> >> >> I tried 1.2 and 1.3. I expect you did compile for Kernel 2.4 ? >> > >> > You can compile DL for kernel 2.4 but not 2.6? >> >> Both don't work and at least the 2.4 must.... >> >> > Where does it abort? On the kernel compile? >> >> No, different places. Currently one machine doesn't like gcc, the other >> pwlib. Both applications shouldn't cause any trouble, they didn't get >> modified for quite a while. > > That's really weird. I'm not a big fan of Fedora. I switched to SuSE > shortly after upgrading to FC1 and running into problems (not DL > related). I haven't tried FC2, but I've heard of other people having > problems. (YMMV :) Yeah I get that impression, too. >> > I'm running SuSE 9.1 (2.6 kernel based), and haven't had any problems >> > compiling a 2.4 DL, but I haven't tried compiling a 2.6 DL. >> >> It's probably worth a try with SuSE 9.1. > > I can run a 2.6 compile on SuSE 9.1 and see what happens. What should, > or shouldn't I select in menuconfig? Is there a profile for 2.6? No need for this, but thanks anyway. The 2.6 compile is not stable yet, I actually had on my list for this week to fix most of the problems there. But as I mentioned, the 2.4 compile *must* work... I'm currently downloading the personal edition of suse 9.1, this is enough to do some testing. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Bruce S. <bw...@ar...> - 2004-07-21 13:23:59
|
> >> > HZ> is anybody compiling DL under Fedora Core 2 ? > >> > Yes I am. > >> > HZ> I just upgraded 2 boxes and now I have all kinds of problems... > >> > I have no problem (1.2 only) > >> > >> I tried 1.2 and 1.3. I expect you did compile for Kernel 2.4 ? > > > > You can compile DL for kernel 2.4 but not 2.6? > > Both don't work and at least the 2.4 must.... > > > Where does it abort? On the kernel compile? > > No, different places. Currently one machine doesn't like gcc, the other > pwlib. Both applications shouldn't cause any trouble, they didn't get > modified for quite a while. That's really weird. I'm not a big fan of Fedora. I switched to SuSE shortly after upgrading to FC1 and running into problems (not DL related). I haven't tried FC2, but I've heard of other people having problems. (YMMV :) > > I'm running SuSE 9.1 (2.6 kernel based), and haven't had any problems > > compiling a 2.4 DL, but I haven't tried compiling a 2.6 DL. > > It's probably worth a try with SuSE 9.1. I can run a 2.6 compile on SuSE 9.1 and see what happens. What should, or shouldn't I select in menuconfig? Is there a profile for 2.6? - BS |
|
From: Heiko Z. <he...@zu...> - 2004-07-21 13:16:21
|
>> > HZ> is anybody compiling DL under Fedora Core 2 ? >> > Yes I am. >> > HZ> I just upgraded 2 boxes and now I have all kinds of problems... >> > I have no problem (1.2 only) >> >> I tried 1.2 and 1.3. I expect you did compile for Kernel 2.4 ? > > You can compile DL for kernel 2.4 but not 2.6? Both don't work and at least the 2.4 must.... > Where does it abort? On the kernel compile? No, different places. Currently one machine doesn't like gcc, the other pwlib. Both applications shouldn't cause any trouble, they didn't get modified for quite a while. > I'm running SuSE 9.1 (2.6 kernel based), and haven't had any problems > compiling a 2.4 DL, but I haven't tried compiling a 2.6 DL. It's probably worth a try with SuSE 9.1. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Bruce S. <bw...@ar...> - 2004-07-21 13:06:57
|
> > HZ> is anybody compiling DL under Fedora Core 2 ? > > Yes I am. > > HZ> I just upgraded 2 boxes and now I have all kinds of problems... > > I have no problem (1.2 only) > > I tried 1.2 and 1.3. I expect you did compile for Kernel 2.4 ? You can compile DL for kernel 2.4 but not 2.6? Where does it abort? On the kernel compile? I'm running SuSE 9.1 (2.6 kernel based), and haven't had any problems compiling a 2.4 DL, but I haven't tried compiling a 2.6 DL. - BS |
|
From: Heiko Z. <he...@zu...> - 2004-07-21 12:36:20
|
> Dear Heiko, > > Wednesday, July 21, 2004, 3:56:53 AM, you wrote: > > HZ> is anybody compiling DL under Fedora Core 2 ? > Yes I am. > HZ> I just upgraded 2 boxes and now I have all kinds of problems... > I have no problem (1.2 only) I tried 1.2 and 1.3. I expect you did compile for Kernel 2.4 ? I guess I will at least give the build machine the old SuSE 8.0 back... I don't really want to remove FC2 from my Notebook, that means I have to keep trying. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Serge L. <se...@nn...> - 2004-07-21 06:14:38
|
Dear Heiko, Wednesday, July 21, 2004, 3:56:53 AM, you wrote: HZ> is anybody compiling DL under Fedora Core 2 ? Yes I am. HZ> I just upgraded 2 boxes and now I have all kinds of problems... I have no problem (1.2 only) -- Best regards, Serge mailto:se...@nn... |
|
From: Heiko Z. <he...@zu...> - 2004-07-21 00:01:20
|
Hey, is anybody compiling DL under Fedora Core 2 ? I just upgraded 2 boxes and now I have all kinds of problems... -- Regards Heiko http://www.devil-linux.org |
|
From: Heiko Z. <he...@zu...> - 2004-07-19 15:41:22
|
Thanks for all the stuff, I'll added it to my todo list. Heiko > Okay folks, I have tested and perfected the serial console booting. > > Why not submit a patch? I suck at making patches (lame, I know). They > are always wrong. Besides, the steps are very simple (3 lines). > > 1 - Modify scripts/build-iso > Find this line: > > BOOT_OPTIONS_DL="root=/dev/ram0 initrd=/boot/initrd.gz init=/linuxrc > $BOOT_OPTION_RAMDISK" > > and turn it into this line: > > BOOT_OPTIONS_DL="root=/dev/ram0 initrd=/boot/initrd.gz init=/linuxrc > $BOOT_OPTION_RAMDISK console=tty0 console=tty0,9600n8 " > > This change is enough to allow kernel boot messages to populate COM1. > It is also enough to create a boot prompt...but ONLY in single user mode > (init 1). We need this in multi-user modes (3,5). > > 2 - Modify /etc/inittab > Append the following line to your inittab file: > S0:2345:respawn:/sbin/agetty -L 9600 ttyS0 vt102 > > 3 - Modify /etc/securetty (optional) > Append: > ttyS0 > to your securetty file. > If you do not, you have to log in as a regular user and su root. > > **** YOU ARE DONE - REBOOT and ENJOY **** > > Notes: > 1 - For those concerned with systems W/O a serial port. > I have a Laptop WITHOUT a serial port. I booted the DL image on it and > did not receive any errors or weird messages. More testing is welcome, > but I am confident that the kernel boot change (scripts/build-iso) is > harmless for 99.99999% of systems out there. > > 2 - Why agetty instead of mgetty? > Beats me! I wasted hours trying to make mgetty work. It DID work, but > with a glitch: you could only log in once! Any attempt to log in again > would render the serial port useless till the next reboot! No matter > what I tried to do, mgetty just would NOT give me a login prompt again > till a reboot. I looked at my SuSE box, and commented out in their > inittab was "agetty". Hey, if SuSE can do it, so can we! > > -- > Have a great day > > Peter Frischknecht > Empowering Solutions, Inc. > http://www.empoweringsolutions.com > AIM: esipeterf > > > ------------------------------------------------------- > This SF.Net email is sponsored by BEA Weblogic Workshop > FREE Java Enterprise J2EE developer tools! > Get your free copy of BEA WebLogic Workshop 8.1 today. > http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click > _______________________________________________ > Devil-linux-develop mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-develop > > -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Peter F. <pe...@em...> - 2004-07-19 01:37:48
|
Okay folks, I have tested and perfected the serial console booting. Why not submit a patch? I suck at making patches (lame, I know). They are always wrong. Besides, the steps are very simple (3 lines). 1 - Modify scripts/build-iso Find this line: BOOT_OPTIONS_DL="root=/dev/ram0 initrd=/boot/initrd.gz init=/linuxrc $BOOT_OPTION_RAMDISK" and turn it into this line: BOOT_OPTIONS_DL="root=/dev/ram0 initrd=/boot/initrd.gz init=/linuxrc $BOOT_OPTION_RAMDISK console=tty0 console=tty0,9600n8 " This change is enough to allow kernel boot messages to populate COM1. It is also enough to create a boot prompt...but ONLY in single user mode (init 1). We need this in multi-user modes (3,5). 2 - Modify /etc/inittab Append the following line to your inittab file: S0:2345:respawn:/sbin/agetty -L 9600 ttyS0 vt102 3 - Modify /etc/securetty (optional) Append: ttyS0 to your securetty file. If you do not, you have to log in as a regular user and su root. **** YOU ARE DONE - REBOOT and ENJOY **** Notes: 1 - For those concerned with systems W/O a serial port. I have a Laptop WITHOUT a serial port. I booted the DL image on it and did not receive any errors or weird messages. More testing is welcome, but I am confident that the kernel boot change (scripts/build-iso) is harmless for 99.99999% of systems out there. 2 - Why agetty instead of mgetty? Beats me! I wasted hours trying to make mgetty work. It DID work, but with a glitch: you could only log in once! Any attempt to log in again would render the serial port useless till the next reboot! No matter what I tried to do, mgetty just would NOT give me a login prompt again till a reboot. I looked at my SuSE box, and commented out in their inittab was "agetty". Hey, if SuSE can do it, so can we! -- Have a great day Peter Frischknecht Empowering Solutions, Inc. http://www.empoweringsolutions.com AIM: esipeterf |
|
From: SourceForge.net <no...@so...> - 2004-07-17 15:49:27
|
Feature Requests item #992900, was opened at 2004-07-17 10:49 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=992900&group_id=34096 Category: Packages Group: None Status: Open Priority: 5 Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: add The Doorman Initial Comment: http://doorman.sourceforge.net/ Summary This project allows a server to run silently, invisibly, with all TCP ports closed... except to those who know... the secret knock! Discussion The doorman is intended to run on systems which have their firewall rules turned down tightly enough as to be effectively invisible to the outside world. The doorman adds and removes extra rules in a carefully controlled manner. Using metaphor 1... The doorman daemon "guards the door" of a host, admitting only recognized parties. It allows a server which is not intended for general public access to run with all of it's TCP ports closed to the outside world. A matching "knocker" is provided, with which to persuade the doorman to open the door a crack, just wide enough for a single TCP connection from a single IP address. And now, switching to metaphor 2... :) A private server thus rigged for silent running has greatly enhanced security. Port scans cannot reveal it's existence. Even if it's existence is known by other means (or the firewall isn't all that tight), possible bugs in server code cannot be exploited; packets from unknown sources simply never get to the bug. The current implementation of the doorman, "doormand", is suitable for protecting only TCP services on Unix-type systems. The door-knocker, "knock", can be run under Unix, GNU/Linux, or Microsoft Windows. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=992900&group_id=34096 |
|
From: SourceForge.net <no...@so...> - 2004-07-17 15:48:35
|
Feature Requests item #992899, was opened at 2004-07-17 10:48 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=992899&group_id=34096 Category: Packages Group: None Status: Open Priority: 5 Submitted By: Heiko Zuerker (smiley73) Assigned to: Nobody/Anonymous (nobody) Summary: add trapdoor2 Initial Comment: http://oss.linbit.com/trapdoor2/ trapdoor2 (td2) allows remote users to execute local commands by sending 'magic cookies'. this can e.g. be used to alter local firewalling rules so people can connect to local services after sending the magick cookie. td2 is implemented as high-secure https server. the daemon processes are running in a chroot jail with multiple rlimits set. even if td2 can be exploited (e.g. using a hypothetical security hole in the SSL implementation), it is very unlikely that the attacker can execute any commands on the machine and/or can cause any damage. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=410646&aid=992899&group_id=34096 |
|
From: Bruce S. <bw...@ar...> - 2004-07-14 12:45:38
|
> > > I just noticed 'motion' was in /sbin instead of /usr/sbin, I messed up > > > copy_files, here is the fix. The other scripts I wrote seem correct. > > > Roland > > > > I'm actually out of town right now, Bruce can you apply the patch in 1.2 & > > 1.3 ? > > Sure, I'll do it tomorrow. Off to a LUG meeting now ... Done and committed. - BS |
|
From: Bruce S. <bw...@ar...> - 2004-07-13 22:15:03
|
> > I just noticed 'motion' was in /sbin instead of /usr/sbin, I messed up > > copy_files, here is the fix. The other scripts I wrote seem correct. > > Roland > > I'm actually out of town right now, Bruce can you apply the patch in 1.2 & > 1.3 ? Sure, I'll do it tomorrow. Off to a LUG meeting now ... - BS |
|
From: Heiko Z. <he...@zu...> - 2004-07-13 22:11:19
|
> Hi, > I just noticed 'motion' was in /sbin instead of /usr/sbin, I messed up > copy_files, here is the fix. The other scripts I wrote seem correct. > Roland I'm actually out of town right now, Bruce can you apply the patch in 1.2 & 1.3 ? Thanks! -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Roland P. <ro...@pa...> - 2004-07-13 21:26:47
|
Hi, I just noticed 'motion' was in /sbin instead of /usr/sbin, I messed up copy_files, here is the fix. The other scripts I wrote seem correct. Roland -- ICQ UIN 49339118 Linux Counter #88774 GPG-Key 1024D/59C6AFA6 2003-02-07 Roland Pabel <ro...@pa...> |
35 messages has been excluded from this view by a project administrator.
