3ware and Debian?
Hi, Does anyone here run any 3ware IDE RAID cards here, and Debian as well? Do you know if 3ware's "Web-based RAID Control" program works in Debian? Thanks. Sincerely, Jason
Re: unstable is "unstable"; stable is "outdated"
> > > aspect of their distro pretty good. They are business people over there, > > > and they know how frequent business users like to have updates, and when > > ... > > > > People here around *only* know RedHat, and it's *the best*, because > > each half year you can buy a new Version. > > > > It seems that RH learnt much from M$ ;) Then perhaps Debian should also head that way "more" (not completely) and release a new version more often, rather than waiting so long?
Re: unstable is "unstable"; stable is "outdated"
> > Last Debian Weekly News says that a Maintainer dropped 18 packages out > of frustration with the slow pace of Debian 3.0. It also says that > this slow pace is because Bugs are simply not fixed. Yes, I read about that in the Debian Week too. > > > If companies would a) adopt Debian packages (by inhouse programmers), > and/or b) sponsor packages Maintainers, there would be some economic > thrive behind the Debian Releases, and it would just be fair, because > Debian is thriving a lot of companies, isn't it? > True... but not to the point (at least for us) to hire a person to specifically maintain debian packages and such. We run a mirror in HK :-) It would have been nice if Corel's spin on Debian took off, as they could then really sponsor some developers to work on debian/corel's distro. Hum... i wonder if any other distro's based on Debian are helping out...
Re: The Debian way to turn off accept_source_route.
You could put it in /etc/init.d/networking or /etc/init.d/bootmisc.sh Both seem appropriate... - Original Message - From: "Donovan Baarda" <[EMAIL PROTECTED]> To: Sent: Wednesday, February 06, 2002 12:43 PM Subject: The Debian way to turn off accept_source_route. > G'day, > > was just fiddling with my everything-server and thought I noticed what > looked like a bit of source-routed traffic was going through it. I noticed > /proc/sys/net/ipv4/conf/default/accept_source_route was '1', the same as all > the interfaces. After getting a bit worried, it looks like the > ../all/accept_source_route was '0'. I'm assuming the '../all/..' overides > the individual interfaces, but then I'm not sure _what_ that little blip of > traffic was. > > I know decent firewalling will kill source-routed traffic, but doing > "cat 0 > /proc/sys/net/ipv4/conf/all/accept_source_route" is probably also a > good idea. Does Debian do this somewhere? What is the kernel default? If > Debian doesn't already do this, what is the correct way to do it? The > /etc/network/options will set '../all/forwarding', but nothing else. > > -- > -- > ABO: finger [EMAIL PROTECTED] for more info, including pgp key > -- > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
3ware and Debian?
Hi, Does anyone here run any 3ware IDE RAID cards here, and Debian as well? Do you know if 3ware's "Web-based RAID Control" program works in Debian? Thanks. Sincerely, Jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: unstable is "unstable"; stable is "outdated"
> > > aspect of their distro pretty good. They are business people over there, > > > and they know how frequent business users like to have updates, and when > > ... > > > > People here around *only* know RedHat, and it's *the best*, because > > each half year you can buy a new Version. > > > > It seems that RH learnt much from M$ ;) Then perhaps Debian should also head that way "more" (not completely) and release a new version more often, rather than waiting so long? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: unstable is "unstable"; stable is "outdated"
> > Last Debian Weekly News says that a Maintainer dropped 18 packages out > of frustration with the slow pace of Debian 3.0. It also says that > this slow pace is because Bugs are simply not fixed. Yes, I read about that in the Debian Week too. > > > If companies would a) adopt Debian packages (by inhouse programmers), > and/or b) sponsor packages Maintainers, there would be some economic > thrive behind the Debian Releases, and it would just be fair, because > Debian is thriving a lot of companies, isn't it? > True... but not to the point (at least for us) to hire a person to specifically maintain debian packages and such. We run a mirror in HK :-) It would have been nice if Corel's spin on Debian took off, as they could then really sponsor some developers to work on debian/corel's distro. Hum... i wonder if any other distro's based on Debian are helping out... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: The Debian way to turn off accept_source_route.
You could put it in /etc/init.d/networking or /etc/init.d/bootmisc.sh Both seem appropriate... - Original Message - From: "Donovan Baarda" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 06, 2002 12:43 PM Subject: The Debian way to turn off accept_source_route. > G'day, > > was just fiddling with my everything-server and thought I noticed what > looked like a bit of source-routed traffic was going through it. I noticed > /proc/sys/net/ipv4/conf/default/accept_source_route was '1', the same as all > the interfaces. After getting a bit worried, it looks like the > ../all/accept_source_route was '0'. I'm assuming the '../all/..' overides > the individual interfaces, but then I'm not sure _what_ that little blip of > traffic was. > > I know decent firewalling will kill source-routed traffic, but doing > "cat 0 > /proc/sys/net/ipv4/conf/all/accept_source_route" is probably also a > good idea. Does Debian do this somewhere? What is the kernel default? If > Debian doesn't already do this, what is the correct way to do it? The > /etc/network/options will set '../all/forwarding', but nothing else. > > -- > -- > ABO: finger [EMAIL PROTECTED] for more info, including pgp key > -- > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems building FreeSWAN kernel package.
On Wed, Feb 06, 2002 at 04:36:38PM -0500, [EMAIL PROTECTED] wrote: > > You don't really say what you did. Did you run make menuconfig or equiv? > Missing autoconf is probably not freeswan related unless the patcher got > mangled. Well, the documentation in the README.Debian (for kernel-patch-freeswan) states: <-snip-> If you want to use the freeswan utilities, you will need a patched kernel. When you install the kernel-patch-freeswan package and use make-kpkg to build your kernel, it should be patched automatically when you set the environment variable PATCH_THE_KERNEL=YES Usually you can then create a kernel package with make-kpkg --config=menuconfig --revision= kernel_image The "--config=menuconfig" parameter forces make-kpkg to call "make menuconfig" after patching the kernel source, so that you have the possibility to configure compile-time options for freeswan. <-snip-> So I assumed menuconfig would pop up, (which it never did). > make-kpkg built freeswan flawlessly on several i86 machines here in > past couple of weeks. All running current unstable. Maybe a month > ago I did have to tweak it but recent freeswan package fixed that. Well, below I describe my failed attempt at trying to apply the kernel-patch-freeswan manually. Maybe you can provide some suggestions to either the above, or below attempts. > > The documentation (README.Debian) is pretty sparse, and I don't know where > > else to go to get info on doing this. Any comments or suggestions greatly > > appreciated. Thanks in advance. > > Try applying patches by hand to see what happens. Then just build kernel > as usual. Ok, this is how the documentation describes applying the patch manually. <-snip-> If you really want to compile your kernel without the help of kernel-package, you can patch it by going to your kernel source tree directory and entering 'make -C /usr/src/kernel-patches/all/freeswan -f Makefile insert KERNELSRC= PATCHER=/usr/src/kernel-patches/all/freeswan/patcher' <-snip-> gateway:/usr/src/linux# make -C /usr/src/kernel-patches/all/freeswan/ -f Makefile insert KERNELSRV=/usr/src/kernel-source-2.4.17 PATCHER=/usr/src/kernel-patches/all/freeswan/patcher make: Entering directory `/usr/src/kernel-patches/all/freeswan' echo "===" === echo "`date` `cd /usr/src/linux ; pwd`" Wed Feb 6 06:56:52 PST 2002 /usr/src/linux make _patches2.3 BINDIR=/usr/local/lib/ipsec PUBDIR=/usr/local/sbin PRIVDIR=/usr/local/lib/ipsec REALPRIVDIR=/usr/local/lib/ipsec MANTREE=/usr/local/man DESTDIR= INSTALL="install" make[1]: Entering directory `/usr/src/kernel-patches/all/freeswan' * applying klips/patches2.2/Documentation.Configure.help to /usr/src/linux/Documentation/Configure.help... patching file ./Documentation/Configure.help Hunk #1 FAILED at 3530. 1 out of 1 hunk FAILED -- saving rejects to file ./Documentation/Configure.help.rej * /usr/src/linux/Documentation/Configure.help patch failed, restoring original /usr/src/kernel-patches/all/freeswan/patcher: patch on /usr/src/linux/Documentation/Configure.help failed! /usr/src/kernel-patches/all/freeswan/patcher: restoring original /usr/src/linux/Documentation/Configure.help, /usr/src/kernel-patches/all/freeswan/patcher: leaving patch attempt in /usr/src/linux/Documentation/Configure.help.mangled make[1]: *** [_patches2.3] Error 1 make[1]: Leaving directory `/usr/src/kernel-patches/all/freeswan' make: *** [patches] Error 2 make: Leaving directory `/usr/src/kernel-patches/all/freeswan' gateway:/usr/src/linux# That's as far as I get. Any suggestions? I really want to avoid building a stock kernel because I am trying to do this the "debian way" and get a debian kernel package out of it. (which I can use on other systems, or at least learn what I need to do to make custom ones for other architectures). -- Nick Jennings
postgres back-up
I need to make back-up for a lot of database in my potato. Now I stop postgres, tar, restart postgres. But I dont like. I need to back up usernames, password, ecc... how _ Sebastian Ezequiel Ovide
Re: Problems building FreeSWAN kernel package.
On Wed, Feb 06, 2002 at 12:38:27PM -0800, Nick Jennings wrote: > Hello, > > Getting a VPN set up on my gateway machine. Running woody (2.4.17). > > Installed the packages: > freeswan, kernel-patch-freeswan, kernel-package, gawk > > After reading /usr/share/doc/kerne-package-freeswan/README.Debian I > also installed: > kernel-source-2.4.17, kernel-headers-2.4.17 > > gateway:/# /usr/src/kernel-source-2.4.17/ > gateway:/usr/src/kernel-source-2.4.17# make-kpkg --config=menuconfig > --revision=gateway.ipsec.1 buildpackage > <-snip-> > <** goes on for a while, then errors out: **> > <-snip-> > /usr/bin/make _sfdep_kernel _sfdep_drivers _sfdep_mm _sfdep_fs _sfdep_net > _sfdep_ipc _sfdep_lib _sfdep_arch/i386/kernel _sfdep_arch/i386/mm > _sfdep_arch/i386/lib _sfdep_arch/i386/math-emu _FASTDEP_ALL_SUB_DIRS="kernel > drivers mm fs net ipc lib arch/i386/kernel arch/i386/mm arch/i386/lib > arch/i386/math-emu" > make[3]: Entering directory `/usr/src/kernel-source-2.4.17' > /usr/bin/make -C kernel fastdep > make[4]: Entering directory `/usr/src/kernel-source-2.4.17/kernel' > make[4]: *** No rule to make target > `/usr/src/kernel-source-2.4.17/include/linux/autoconf.h', needed by > `/usr/src/kernel-source-2.4.17/include/linux/modules/signal.ver'. Stop. > make[4]: Leaving directory `/usr/src/kernel-source-2.4.17/kernel' > make[3]: *** [_sfdep_kernel] Error 2 > make[3]: Leaving directory `/usr/src/kernel-source-2.4.17' > make[2]: *** [dep-files] Error 2 > make[2]: Leaving directory `/usr/src/kernel-source-2.4.17' > make[1]: *** [stamp-build] Error 2 > make[1]: Leaving directory `/usr/src/kernel-source-2.4.17' > make: *** [stamp-buildpackage] Error 2 > gateway:/usr/src/kernel-source-2.4.17# > You don't really say what you did. Did you run make menuconfig or equiv? Missing autoconf is probably not freeswan related unless the patcher got mangled. make-kpkg built freeswan flawlessly on several i86 machines here in past couple of weeks. All running current unstable. Maybe a month ago I did have to tweak it but recent freeswan package fixed that. > > The documentation (README.Debian) is pretty sparse, and I don't know where > else to go to get info on doing this. Any comments or suggestions greatly > appreciated. Thanks in advance. Try applying patches by hand to see what happens. Then just build kernel as usual. > > -- > Nick Jennings > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Christopher F. Miller, Publisher [EMAIL PROTECTED] MaineStreet Communications, Inc 208 Portland Road, Gray, ME 04039 1.207.657.5078 http://www.maine.com/ Content/site management, online commerce, internet integration, Debian linux
Re: "transparent" firewall possible?
> It is a pretty thing, and can virtually be plugged in anywhere to provide > instant firewall protection :-) Yeah, I use it at home on my DSL line as BT (in the UK) don't allow any routing at layer 3 to put a firewall in any other way. Matt.
Problems building FreeSWAN kernel package.
Hello, Getting a VPN set up on my gateway machine. Running woody (2.4.17). Installed the packages: freeswan, kernel-patch-freeswan, kernel-package, gawk After reading /usr/share/doc/kerne-package-freeswan/README.Debian I also installed: kernel-source-2.4.17, kernel-headers-2.4.17 gateway:/# /usr/src/kernel-source-2.4.17/ gateway:/usr/src/kernel-source-2.4.17# make-kpkg --config=menuconfig --revision=gateway.ipsec.1 buildpackage <-snip-> <** goes on for a while, then errors out: **> <-snip-> /usr/bin/make _sfdep_kernel _sfdep_drivers _sfdep_mm _sfdep_fs _sfdep_net _sfdep_ipc _sfdep_lib _sfdep_arch/i386/kernel _sfdep_arch/i386/mm _sfdep_arch/i386/lib _sfdep_arch/i386/math-emu _FASTDEP_ALL_SUB_DIRS="kernel drivers mm fs net ipc lib arch/i386/kernel arch/i386/mm arch/i386/lib arch/i386/math-emu" make[3]: Entering directory `/usr/src/kernel-source-2.4.17' /usr/bin/make -C kernel fastdep make[4]: Entering directory `/usr/src/kernel-source-2.4.17/kernel' make[4]: *** No rule to make target `/usr/src/kernel-source-2.4.17/include/linux/autoconf.h', needed by `/usr/src/kernel-source-2.4.17/include/linux/modules/signal.ver'. Stop. make[4]: Leaving directory `/usr/src/kernel-source-2.4.17/kernel' make[3]: *** [_sfdep_kernel] Error 2 make[3]: Leaving directory `/usr/src/kernel-source-2.4.17' make[2]: *** [dep-files] Error 2 make[2]: Leaving directory `/usr/src/kernel-source-2.4.17' make[1]: *** [stamp-build] Error 2 make[1]: Leaving directory `/usr/src/kernel-source-2.4.17' make: *** [stamp-buildpackage] Error 2 gateway:/usr/src/kernel-source-2.4.17# The documentation (README.Debian) is pretty sparse, and I don't know where else to go to get info on doing this. Any comments or suggestions greatly appreciated. Thanks in advance. -- Nick Jennings
Re: Mass installation procedure for Debian?
Hi, After reading the debian-ISP list for about a week I would like to say thank's for some interesting info. Re: > > many thanks for the hints, ideas and all this. > > I have to look at the different approaches and what > > comes closest to what I really want. For an ADSL router that we like to copy: The working system is on hda we put a 250MB or more disk as hdc and run a script to copy hda to hdc lilo hdc so that it will boot as hda make some changes in /etc Much as I like Debian, dselect and all that, sometimes there is just a simpler way to do stuff. Regards [EMAIL PROTECTED]
Re: Problems building FreeSWAN kernel package.
On Wed, Feb 06, 2002 at 04:36:38PM -0500, [EMAIL PROTECTED] wrote: > > You don't really say what you did. Did you run make menuconfig or equiv? > Missing autoconf is probably not freeswan related unless the patcher got > mangled. Well, the documentation in the README.Debian (for kernel-patch-freeswan) states: <-snip-> If you want to use the freeswan utilities, you will need a patched kernel. When you install the kernel-patch-freeswan package and use make-kpkg to build your kernel, it should be patched automatically when you set the environment variable PATCH_THE_KERNEL=YES Usually you can then create a kernel package with make-kpkg --config=menuconfig --revision= kernel_image The "--config=menuconfig" parameter forces make-kpkg to call "make menuconfig" after patching the kernel source, so that you have the possibility to configure compile-time options for freeswan. <-snip-> So I assumed menuconfig would pop up, (which it never did). > make-kpkg built freeswan flawlessly on several i86 machines here in > past couple of weeks. All running current unstable. Maybe a month > ago I did have to tweak it but recent freeswan package fixed that. Well, below I describe my failed attempt at trying to apply the kernel-patch-freeswan manually. Maybe you can provide some suggestions to either the above, or below attempts. > > The documentation (README.Debian) is pretty sparse, and I don't know where > > else to go to get info on doing this. Any comments or suggestions greatly > > appreciated. Thanks in advance. > > Try applying patches by hand to see what happens. Then just build kernel > as usual. Ok, this is how the documentation describes applying the patch manually. <-snip-> If you really want to compile your kernel without the help of kernel-package, you can patch it by going to your kernel source tree directory and entering 'make -C /usr/src/kernel-patches/all/freeswan -f Makefile insert KERNELSRC= PATCHER=/usr/src/kernel-patches/all/freeswan/patcher' <-snip-> gateway:/usr/src/linux# make -C /usr/src/kernel-patches/all/freeswan/ -f Makefile insert KERNELSRV=/usr/src/kernel-source-2.4.17 PATCHER=/usr/src/kernel-patches/all/freeswan/patcher make: Entering directory `/usr/src/kernel-patches/all/freeswan' echo "===" === echo "`date` `cd /usr/src/linux ; pwd`" Wed Feb 6 06:56:52 PST 2002 /usr/src/linux make _patches2.3 BINDIR=/usr/local/lib/ipsec PUBDIR=/usr/local/sbin PRIVDIR=/usr/local/lib/ipsec REALPRIVDIR=/usr/local/lib/ipsec MANTREE=/usr/local/man DESTDIR= INSTALL="install" make[1]: Entering directory `/usr/src/kernel-patches/all/freeswan' * applying klips/patches2.2/Documentation.Configure.help to /usr/src/linux/Documentation/Configure.help... patching file ./Documentation/Configure.help Hunk #1 FAILED at 3530. 1 out of 1 hunk FAILED -- saving rejects to file ./Documentation/Configure.help.rej * /usr/src/linux/Documentation/Configure.help patch failed, restoring original /usr/src/kernel-patches/all/freeswan/patcher: patch on /usr/src/linux/Documentation/Configure.help failed! /usr/src/kernel-patches/all/freeswan/patcher: restoring original /usr/src/linux/Documentation/Configure.help, /usr/src/kernel-patches/all/freeswan/patcher: leaving patch attempt in /usr/src/linux/Documentation/Configure.help.mangled make[1]: *** [_patches2.3] Error 1 make[1]: Leaving directory `/usr/src/kernel-patches/all/freeswan' make: *** [patches] Error 2 make: Leaving directory `/usr/src/kernel-patches/all/freeswan' gateway:/usr/src/linux# That's as far as I get. Any suggestions? I really want to avoid building a stock kernel because I am trying to do this the "debian way" and get a debian kernel package out of it. (which I can use on other systems, or at least learn what I need to do to make custom ones for other architectures). -- Nick Jennings -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
postgres back-up
I need to make back-up for a lot of database in my potato. Now I stop postgres, tar, restart postgres. But I dont like. I need to back up usernames, password, ecc... how _ Sebastian Ezequiel Ovide -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems building FreeSWAN kernel package.
On Wed, Feb 06, 2002 at 12:38:27PM -0800, Nick Jennings wrote: > Hello, > > Getting a VPN set up on my gateway machine. Running woody (2.4.17). > > Installed the packages: > freeswan, kernel-patch-freeswan, kernel-package, gawk > > After reading /usr/share/doc/kerne-package-freeswan/README.Debian I > also installed: > kernel-source-2.4.17, kernel-headers-2.4.17 > > gateway:/# /usr/src/kernel-source-2.4.17/ > gateway:/usr/src/kernel-source-2.4.17# make-kpkg --config=menuconfig >--revision=gateway.ipsec.1 buildpackage > <-snip-> > <** goes on for a while, then errors out: **> > <-snip-> > /usr/bin/make _sfdep_kernel _sfdep_drivers _sfdep_mm _sfdep_fs _sfdep_net _sfdep_ipc >_sfdep_lib _sfdep_arch/i386/kernel _sfdep_arch/i386/mm _sfdep_arch/i386/lib >_sfdep_arch/i386/math-emu _FASTDEP_ALL_SUB_DIRS="kernel drivers mm fs net ipc lib >arch/i386/kernel arch/i386/mm arch/i386/lib arch/i386/math-emu" > make[3]: Entering directory `/usr/src/kernel-source-2.4.17' > /usr/bin/make -C kernel fastdep > make[4]: Entering directory `/usr/src/kernel-source-2.4.17/kernel' > make[4]: *** No rule to make target >`/usr/src/kernel-source-2.4.17/include/linux/autoconf.h', needed by >`/usr/src/kernel-source-2.4.17/include/linux/modules/signal.ver'. Stop. > make[4]: Leaving directory `/usr/src/kernel-source-2.4.17/kernel' > make[3]: *** [_sfdep_kernel] Error 2 > make[3]: Leaving directory `/usr/src/kernel-source-2.4.17' > make[2]: *** [dep-files] Error 2 > make[2]: Leaving directory `/usr/src/kernel-source-2.4.17' > make[1]: *** [stamp-build] Error 2 > make[1]: Leaving directory `/usr/src/kernel-source-2.4.17' > make: *** [stamp-buildpackage] Error 2 > gateway:/usr/src/kernel-source-2.4.17# > You don't really say what you did. Did you run make menuconfig or equiv? Missing autoconf is probably not freeswan related unless the patcher got mangled. make-kpkg built freeswan flawlessly on several i86 machines here in past couple of weeks. All running current unstable. Maybe a month ago I did have to tweak it but recent freeswan package fixed that. > > The documentation (README.Debian) is pretty sparse, and I don't know where > else to go to get info on doing this. Any comments or suggestions greatly > appreciated. Thanks in advance. Try applying patches by hand to see what happens. Then just build kernel as usual. > > -- > Nick Jennings > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Christopher F. Miller, Publisher [EMAIL PROTECTED] MaineStreet Communications, Inc 208 Portland Road, Gray, ME 04039 1.207.657.5078 http://www.maine.com/ Content/site management, online commerce, internet integration, Debian linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "transparent" firewall possible?
> It is a pretty thing, and can virtually be plugged in anywhere to provide > instant firewall protection :-) Yeah, I use it at home on my DSL line as BT (in the UK) don't allow any routing at layer 3 to put a firewall in any other way. Matt. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Problems building FreeSWAN kernel package.
Hello, Getting a VPN set up on my gateway machine. Running woody (2.4.17). Installed the packages: freeswan, kernel-patch-freeswan, kernel-package, gawk After reading /usr/share/doc/kerne-package-freeswan/README.Debian I also installed: kernel-source-2.4.17, kernel-headers-2.4.17 gateway:/# /usr/src/kernel-source-2.4.17/ gateway:/usr/src/kernel-source-2.4.17# make-kpkg --config=menuconfig --revision=gateway.ipsec.1 buildpackage <-snip-> <** goes on for a while, then errors out: **> <-snip-> /usr/bin/make _sfdep_kernel _sfdep_drivers _sfdep_mm _sfdep_fs _sfdep_net _sfdep_ipc _sfdep_lib _sfdep_arch/i386/kernel _sfdep_arch/i386/mm _sfdep_arch/i386/lib _sfdep_arch/i386/math-emu _FASTDEP_ALL_SUB_DIRS="kernel drivers mm fs net ipc lib arch/i386/kernel arch/i386/mm arch/i386/lib arch/i386/math-emu" make[3]: Entering directory `/usr/src/kernel-source-2.4.17' /usr/bin/make -C kernel fastdep make[4]: Entering directory `/usr/src/kernel-source-2.4.17/kernel' make[4]: *** No rule to make target `/usr/src/kernel-source-2.4.17/include/linux/autoconf.h', needed by `/usr/src/kernel-source-2.4.17/include/linux/modules/signal.ver'. Stop. make[4]: Leaving directory `/usr/src/kernel-source-2.4.17/kernel' make[3]: *** [_sfdep_kernel] Error 2 make[3]: Leaving directory `/usr/src/kernel-source-2.4.17' make[2]: *** [dep-files] Error 2 make[2]: Leaving directory `/usr/src/kernel-source-2.4.17' make[1]: *** [stamp-build] Error 2 make[1]: Leaving directory `/usr/src/kernel-source-2.4.17' make: *** [stamp-buildpackage] Error 2 gateway:/usr/src/kernel-source-2.4.17# The documentation (README.Debian) is pretty sparse, and I don't know where else to go to get info on doing this. Any comments or suggestions greatly appreciated. Thanks in advance. -- Nick Jennings -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mass installation procedure for Debian?
Hi, After reading the debian-ISP list for about a week I would like to say thank's for some interesting info. Re: > > many thanks for the hints, ideas and all this. > > I have to look at the different approaches and what > > comes closest to what I really want. For an ADSL router that we like to copy: The working system is on hda we put a 250MB or more disk as hdc and run a script to copy hda to hdc lilo hdc so that it will boot as hda make some changes in /etc Much as I like Debian, dselect and all that, sometimes there is just a simpler way to do stuff. Regards [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
AW: Subject: ip accounting -> PostgreSQL
On woody there si s.th. called "trafstats" which should do that. It's on my todo list, but not yet. Have a look at it... -Ursprüngliche Nachricht- Von: Nicholay P. Chuprynin [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 6. Februar 2002 15:58 An: debian-isp@lists.debian.org Betreff: Re: Subject: ip accounting -> PostgreSQL All what we need is: source IP, destination IP, source port, destination port, bytes, time. For now nacctd periodically stores this information in the text file, and simple perl script (periodically) moves fresh data to MySQL. But we like the idea to put it directly into database. Why Postgres? It have some features that we want to use in the future. Maybe we missing something important? Nicholay On Thu, 7 Feb 2002, Kevin Littlejohn wrote: > There's a whole slew of ways you can do this, and it'll depend a lot on > how much detail you need. Probably the best approach is to settle on a > front-end system of some sort - be it argus for full netflow-like reporting, > or some sort of snmp poller if you're looking for snmp data, or whatever, > then hack up an import system that can run periodically and import all > data from a given directory into the database. That saves you from having > to worry about what happens if the database is down, too. > > KJL > > On Wed, Feb 06, 2002 at 07:38:39PM +0500, Nicholay P. Chuprynin wrote: > > > > Hello All. > > We need to do IP based traffic accounting on our server, but the main > > question is to store accounting information into PostgreSQL database. > > Any suggestions? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Subject: ip accounting -> PostgreSQL
All what we need is: source IP, destination IP, source port, destination port, bytes, time. For now nacctd periodically stores this information in the text file, and simple perl script (periodically) moves fresh data to MySQL. But we like the idea to put it directly into database. Why Postgres? It have some features that we want to use in the future. Maybe we missing something important? Nicholay On Thu, 7 Feb 2002, Kevin Littlejohn wrote: > There's a whole slew of ways you can do this, and it'll depend a lot on > how much detail you need. Probably the best approach is to settle on a > front-end system of some sort - be it argus for full netflow-like reporting, > or some sort of snmp poller if you're looking for snmp data, or whatever, > then hack up an import system that can run periodically and import all > data from a given directory into the database. That saves you from having > to worry about what happens if the database is down, too. > > KJL > > On Wed, Feb 06, 2002 at 07:38:39PM +0500, Nicholay P. Chuprynin wrote: > > > > Hello All. > > We need to do IP based traffic accounting on our server, but the main > > question is to store accounting information into PostgreSQL database. > > Any suggestions?
Re: Subject: ip accounting -> PostgreSQL
On Mit, 06 Feb 2002, Nicholay P. Chuprynin wrote: > We need to do IP based traffic accounting on our server, but the main > question is to store accounting information into PostgreSQL database. > Any suggestions? You have to recompile the ipac-ng package to support postgresql. If you are using kernel 2.2 I have no idea. -- Noèl Köthe
Subject: ip accounting -> PostgreSQL
Hello All. We need to do IP based traffic accounting on our server, but the main question is to store accounting information into PostgreSQL database. Any suggestions? Thanks, Nicholay
Re: Mass installation procedure for Debian?
On Wed, 6 Feb 2002, Oliver Andrich wrote: > many thanks for the hints, ideas and all this. I have to look at the different > approaches and what comes closest to what I really want. Much to read and > test. Please come up with your findings here, at least I'm very interested in other people's experiences. Alex -- "Forgive me, but I'm talking to a politician." John Simpson, BBC World
AW: Subject: ip accounting -> PostgreSQL
On woody there si s.th. called "trafstats" which should do that. It's on my todo list, but not yet. Have a look at it... -Ursprüngliche Nachricht- Von: Nicholay P. Chuprynin [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 6. Februar 2002 15:58 An: [EMAIL PROTECTED] Betreff: Re: Subject: ip accounting -> PostgreSQL All what we need is: source IP, destination IP, source port, destination port, bytes, time. For now nacctd periodically stores this information in the text file, and simple perl script (periodically) moves fresh data to MySQL. But we like the idea to put it directly into database. Why Postgres? It have some features that we want to use in the future. Maybe we missing something important? Nicholay On Thu, 7 Feb 2002, Kevin Littlejohn wrote: > There's a whole slew of ways you can do this, and it'll depend a lot on > how much detail you need. Probably the best approach is to settle on a > front-end system of some sort - be it argus for full netflow-like reporting, > or some sort of snmp poller if you're looking for snmp data, or whatever, > then hack up an import system that can run periodically and import all > data from a given directory into the database. That saves you from having > to worry about what happens if the database is down, too. > > KJL > > On Wed, Feb 06, 2002 at 07:38:39PM +0500, Nicholay P. Chuprynin wrote: > > > > Hello All. > > We need to do IP based traffic accounting on our server, but the main > > question is to store accounting information into PostgreSQL database. > > Any suggestions? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Subject: ip accounting -> PostgreSQL
All what we need is: source IP, destination IP, source port, destination port, bytes, time. For now nacctd periodically stores this information in the text file, and simple perl script (periodically) moves fresh data to MySQL. But we like the idea to put it directly into database. Why Postgres? It have some features that we want to use in the future. Maybe we missing something important? Nicholay On Thu, 7 Feb 2002, Kevin Littlejohn wrote: > There's a whole slew of ways you can do this, and it'll depend a lot on > how much detail you need. Probably the best approach is to settle on a > front-end system of some sort - be it argus for full netflow-like reporting, > or some sort of snmp poller if you're looking for snmp data, or whatever, > then hack up an import system that can run periodically and import all > data from a given directory into the database. That saves you from having > to worry about what happens if the database is down, too. > > KJL > > On Wed, Feb 06, 2002 at 07:38:39PM +0500, Nicholay P. Chuprynin wrote: > > > > Hello All. > > We need to do IP based traffic accounting on our server, but the main > > question is to store accounting information into PostgreSQL database. > > Any suggestions? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Subject: ip accounting -> PostgreSQL
On Mit, 06 Feb 2002, Nicholay P. Chuprynin wrote: > We need to do IP based traffic accounting on our server, but the main > question is to store accounting information into PostgreSQL database. > Any suggestions? You have to recompile the ipac-ng package to support postgresql. If you are using kernel 2.2 I have no idea. -- Noèl Köthe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Subject: ip accounting -> PostgreSQL
Hello All. We need to do IP based traffic accounting on our server, but the main question is to store accounting information into PostgreSQL database. Any suggestions? Thanks, Nicholay -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mass installation procedure for Debian?
On Wed, 6 Feb 2002, Oliver Andrich wrote: > many thanks for the hints, ideas and all this. I have to look at the different > approaches and what comes closest to what I really want. Much to read and > test. Please come up with your findings here, at least I'm very interested in other people's experiences. Alex -- "Forgive me, but I'm talking to a politician." John Simpson, BBC World -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mass installation procedure for Debian?
Hi, many thanks for the hints, ideas and all this. I have to look at the different approaches and what comes closest to what I really want. Much to read and test. Best regards, Oliver -- - Oliver Andrich | Tel.: 0261-5009075 IT Projektmanagement,| Mobil: 0172-6538591 Systemprogrammierung und -design | Fax: 069-13305990076 | Email: [EMAIL PROTECTED] - Fingerprint: 2AB5 B998 8BD2 AC3A E12A 3A8A 171E 5B1B EC4B 3C2B -
Re: unstable is "unstable"; stable is "outdated"
On Tue, 5/Feb/02 23:03:40, [EMAIL PROTECTED] wrote: > Hello! > > On Sat, Feb 02, 2002 at 06:39:46AM +0800, Jason Lim wrote: > ... > > aspect of their distro pretty good. They are business people over there, > > and they know how frequent business users like to have updates, and when > ... > > People here around *only* know RedHat, and it's *the best*, because > each half year you can buy a new Version. > It seems that RH learnt much from M$ ;) Regards, Chris
Re: exim maildir
Michael Merritt <[EMAIL PROTECTED]> writes: > What do I need to do for Courier to authenticate multiple domain users? How > should their user accounts be setup on the system? IE, how will courier > distinguish between [EMAIL PROTECTED] and [EMAIL PROTECTED] > > -- > Michael MerrittO2/CO2 Conversion Specialist [w] I use the full email-address as login name for IMAP/POP3. The accounts are stored in LDAP, together with the infos for exim. An easier way (for a small numer of email accounts) might be authuserdb Ramin
Re: Squid and FTP
On Wed, Feb 06, 2002 at 09:35:51AM +0200, Craigsc wrote: > Hi All > > Can someone explain to me how I can use Squid > to proxy / cache FTP requests. I need to be > able to restrict FTP downloads and it would > be preferable to do it though Squid as I see > it has the support in the config file. > > Any information would be appreciated as > always :) Squid will do ftp proxying, but only on very strict terms - it'll proxy/cache requests from web browsers, that are sent in http-style. It will not proxy or cache for true ftp clients. There is a package called "frox" (apt-get install frox ;), that seems to do the trick nicely of transparently converting ftp access from ftp clients into proxyable ftp connections, which you can then put through squid. I don't know how it would go under load, and I note that the very act of what it does means ftp connections are slower (but not transfers, necessarily), but it might be what you're after. KJL
Re: Mass installation procedure for Debian?
Hi, many thanks for the hints, ideas and all this. I have to look at the different approaches and what comes closest to what I really want. Much to read and test. Best regards, Oliver -- - Oliver Andrich | Tel.: 0261-5009075 IT Projektmanagement,| Mobil: 0172-6538591 Systemprogrammierung und -design | Fax: 069-13305990076 | Email: [EMAIL PROTECTED] - Fingerprint: 2AB5 B998 8BD2 AC3A E12A 3A8A 171E 5B1B EC4B 3C2B - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Squid and FTP
Hi All Can someone explain to me how I can use Squid to proxy / cache FTP requests. I need to be able to restrict FTP downloads and it would be preferable to do it though Squid as I see it has the support in the config file. Any information would be appreciated as always :) Craig
Re: unstable is "unstable"; stable is "outdated"
On Tue, 5/Feb/02 23:03:40, [EMAIL PROTECTED] wrote: > Hello! > > On Sat, Feb 02, 2002 at 06:39:46AM +0800, Jason Lim wrote: > ... > > aspect of their distro pretty good. They are business people over there, > > and they know how frequent business users like to have updates, and when > ... > > People here around *only* know RedHat, and it's *the best*, because > each half year you can buy a new Version. > It seems that RH learnt much from M$ ;) Regards, Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: exim maildir
Michael Merritt <[EMAIL PROTECTED]> writes: > What do I need to do for Courier to authenticate multiple domain users? How > should their user accounts be setup on the system? IE, how will courier > distinguish between [EMAIL PROTECTED] and [EMAIL PROTECTED]? > > -- > Michael MerrittO2/CO2 Conversion Specialist [w] I use the full email-address as login name for IMAP/POP3. The accounts are stored in LDAP, together with the infos for exim. An easier way (for a small numer of email accounts) might be authuserdb Ramin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
