Menu
▾
▴
devil-linux-discuss — General Mailing List for all discussions
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(59) |
Sep
(57) |
Oct
(5) |
Nov
(45) |
Dec
(21) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(13) |
Feb
(22) |
Mar
(14) |
Apr
(7) |
May
(33) |
Jun
(57) |
Jul
(25) |
Aug
(40) |
Sep
(53) |
Oct
(58) |
Nov
(75) |
Dec
(22) |
| 2003 |
Jan
(101) |
Feb
(101) |
Mar
(103) |
Apr
(125) |
May
(85) |
Jun
(57) |
Jul
(62) |
Aug
(42) |
Sep
(76) |
Oct
(214) |
Nov
(290) |
Dec
(274) |
| 2004 |
Jan
(187) |
Feb
(172) |
Mar
(313) |
Apr
(209) |
May
(169) |
Jun
(147) |
Jul
(118) |
Aug
(193) |
Sep
(227) |
Oct
(125) |
Nov
(246) |
Dec
(191) |
| 2005 |
Jan
(244) |
Feb
(175) |
Mar
(165) |
Apr
(130) |
May
(217) |
Jun
(122) |
Jul
(188) |
Aug
(235) |
Sep
(165) |
Oct
(133) |
Nov
(209) |
Dec
(88) |
| 2006 |
Jan
(66) |
Feb
(89) |
Mar
(108) |
Apr
(91) |
May
(29) |
Jun
(45) |
Jul
(64) |
Aug
(42) |
Sep
(44) |
Oct
(81) |
Nov
(64) |
Dec
(9) |
| 2007 |
Jan
(24) |
Feb
(122) |
Mar
(55) |
Apr
(50) |
May
(84) |
Jun
(13) |
Jul
(80) |
Aug
(70) |
Sep
(78) |
Oct
(45) |
Nov
(56) |
Dec
(42) |
| 2008 |
Jan
(65) |
Feb
(3) |
Mar
(51) |
Apr
(151) |
May
(54) |
Jun
(72) |
Jul
(73) |
Aug
(47) |
Sep
(55) |
Oct
(123) |
Nov
(16) |
Dec
(4) |
| 2009 |
Jan
(23) |
Feb
(39) |
Mar
(27) |
Apr
(36) |
May
(35) |
Jun
(51) |
Jul
(11) |
Aug
(14) |
Sep
(40) |
Oct
(67) |
Nov
(38) |
Dec
(13) |
| 2010 |
Jan
(15) |
Feb
(35) |
Mar
(40) |
Apr
(11) |
May
(26) |
Jun
(10) |
Jul
(5) |
Aug
(50) |
Sep
(86) |
Oct
(67) |
Nov
(36) |
Dec
(11) |
| 2011 |
Jan
(50) |
Feb
(6) |
Mar
(13) |
Apr
(13) |
May
(29) |
Jun
(27) |
Jul
(26) |
Aug
(27) |
Sep
(21) |
Oct
(7) |
Nov
(27) |
Dec
(4) |
| 2012 |
Jan
(11) |
Feb
(20) |
Mar
(48) |
Apr
(18) |
May
(8) |
Jun
(19) |
Jul
|
Aug
(15) |
Sep
(3) |
Oct
(4) |
Nov
(5) |
Dec
(1) |
| 2013 |
Jan
(13) |
Feb
(7) |
Mar
(4) |
Apr
(25) |
May
(2) |
Jun
(8) |
Jul
(4) |
Aug
(8) |
Sep
(7) |
Oct
|
Nov
(5) |
Dec
(10) |
| 2014 |
Jan
|
Feb
|
Mar
(6) |
Apr
(20) |
May
(5) |
Jun
|
Jul
(2) |
Aug
|
Sep
(8) |
Oct
(21) |
Nov
(4) |
Dec
(7) |
| 2015 |
Jan
(10) |
Feb
(9) |
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(5) |
Sep
(11) |
Oct
|
Nov
(17) |
Dec
(32) |
| 2016 |
Jan
(10) |
Feb
(15) |
Mar
(4) |
Apr
(7) |
May
(10) |
Jun
(11) |
Jul
(15) |
Aug
(26) |
Sep
(13) |
Oct
(10) |
Nov
(16) |
Dec
(6) |
| 2017 |
Jan
(9) |
Feb
(3) |
Mar
|
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
(3) |
Sep
(3) |
Oct
(6) |
Nov
(8) |
Dec
|
| 2018 |
Jan
(12) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dominic R. <dl...@ed...> - 2009-11-18 13:29:59
|
Heiko Zuerker wrote: >> -----Original Message----- >> From: Bradlee Landis [mailto:bra...@gm...] >> Sent: Tuesday, November 17, 2009 2:02 PM >> >> No I didn't see that, but that's not good for me... Is there another >> LCD program? >> > > Please let us know if you find a program, I did a search a couple months > back and couldn't find anything. > LCDproc? http://www.lcdproc.org/index.php3 |
|
From: Heiko Z. <he...@zu...> - 2009-11-18 13:09:55
|
> -----Original Message----- > From: Bradlee Landis [mailto:bra...@gm...] > Sent: Tuesday, November 17, 2009 2:02 PM > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] "parport" Replacement Module > > No I didn't see that, but that's not good for me... Is there another > LCD program? Please let us know if you find a program, I did a search a couple months back and couldn't find anything. I have one computer with an LCD display which would be nice to use. I think kernel has now some support for LCD/LED devices, but have no clue what you can do or even how to. > I did see parport, but when I aliased it as /dev/parport/0, lcd4linux > still complained. It works with the hex code though, so I guess we'll > just stick to 1.4RC1 until I find another way to use the LCD screen. Is the LCD display really that critical? I would rather prefer having up-to-date software to be honest. Heiko |
|
From: Serge L. <fi...@in...> - 2009-11-18 08:01:09
|
On 11/17/2009 03:23 PM, Bradlee Landis wrote: > I have a server with 8GB of memory, but I'm only seeing 4GB. I saw > something online about 64 bit kernels and the PAE module built into > the kernel. Are either of these options available for Devil Linux? 64bit DL is still in progress. I believe you can get "the same" result if add the following lines to the end of build/scripts/config/linux-2.6/config_linux.686 file # CONFIG_HIGHMEM4G is not set CONFIG_HIGHMEM64G=y Sincerely, Serge |
|
From: Bradlee L. <bra...@gm...> - 2009-11-17 23:23:18
|
I have a server with 8GB of memory, but I'm only seeing 4GB. I saw something online about 64 bit kernels and the PAE module built into the kernel. Are either of these options available for Devil Linux? Thanks, Brad Landis |
|
From: Bradlee L. <bra...@gm...> - 2009-11-17 20:02:05
|
No I didn't see that, but that's not good for me... Is there another LCD program? I did see parport, but when I aliased it as /dev/parport/0, lcd4linux still complained. It works with the hex code though, so I guess we'll just stick to 1.4RC1 until I find another way to use the LCD screen. -Brad On Tue, Nov 17, 2009 at 12:11 PM, Dominic Raferd <dl...@ed...> wrote: > Perhaps you already saw these comments in the 1.4RC2 changelog: > > 1.4RC2: > - removed lcd4linux from default profile, since it isn't maintained anymore and not functional/compiling > 1.3.4: > - lcd4linux init script doesn't try to load the ppdev module anymore > > I guess no one (apart from you) is using lcd4linux under DL? > > Looks like there was a problem with ppdev under some earlier 2.6 kernels > (http://www.mail-archive.com/lin...@vg.../msg177843.html), > perhaps this is why it was removed? At least one person got it working > with a more recent kernel (2.6.29.1, but using another distro - boo!): > see http://tinycorelinux.com/forum/index.php?topic=3491.0 > > parport should be there though (modprobe -l -n *par*) > > Dominic > > > Bradlee Landis wrote: >> Well, I found that I could use the hex address "0x378" instead of a >> /dev, at least until I can figure out how to load the correct module. >> >> Was there a reason that ppdev module was removed from the new kernel? >> >> Thanks, >> Brad >> >> On Mon, Nov 16, 2009 at 11:35 AM, Bradlee Landis >> <bra...@gm...> wrote: >> >>> I'm looking to upgrade to 1.4RC1, and found that "parport" is no >>> longer a module in the kernel. I can't seem to get lcd4linux to run, >>> because /dev/parport/0 doesn't exist, and the since the previous >>> module "parport" is not in the kernel, what do I need to use instead? >>> >>> Am I supposed to use /etc/modprobe.conf instead of /etc/modules/? It >>> looks to be the right file... >>> >>> I'm having to do this, because one of our new servers ethernet modules >>> needs the "e1000e" module, as the previous just needed "e1000". If >>> there was a way to get the e1000e module into 1.2.15 without having to >>> remake the ISO, that would be easier even though I'd prefer to move to >>> 1.4. >>> >>> Thanks for the help, >>> Brad Landis >>> >>> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day >> trial. Simplify your report design, integration and deployment - and focus on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Devil-linux-discuss mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss >> >> > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > |
|
From: Dominic R. <dl...@ed...> - 2009-11-17 18:11:23
|
Perhaps you already saw these comments in the 1.4RC2 changelog: 1.4RC2: - removed lcd4linux from default profile, since it isn't maintained anymore and not functional/compiling 1.3.4: - lcd4linux init script doesn't try to load the ppdev module anymore I guess no one (apart from you) is using lcd4linux under DL? Looks like there was a problem with ppdev under some earlier 2.6 kernels (http://www.mail-archive.com/lin...@vg.../msg177843.html), perhaps this is why it was removed? At least one person got it working with a more recent kernel (2.6.29.1, but using another distro - boo!): see http://tinycorelinux.com/forum/index.php?topic=3491.0 parport should be there though (modprobe -l -n *par*) Dominic Bradlee Landis wrote: > Well, I found that I could use the hex address "0x378" instead of a > /dev, at least until I can figure out how to load the correct module. > > Was there a reason that ppdev module was removed from the new kernel? > > Thanks, > Brad > > On Mon, Nov 16, 2009 at 11:35 AM, Bradlee Landis > <bra...@gm...> wrote: > >> I'm looking to upgrade to 1.4RC1, and found that "parport" is no >> longer a module in the kernel. I can't seem to get lcd4linux to run, >> because /dev/parport/0 doesn't exist, and the since the previous >> module "parport" is not in the kernel, what do I need to use instead? >> >> Am I supposed to use /etc/modprobe.conf instead of /etc/modules/? It >> looks to be the right file... >> >> I'm having to do this, because one of our new servers ethernet modules >> needs the "e1000e" module, as the previous just needed "e1000". If >> there was a way to get the e1000e module into 1.2.15 without having to >> remake the ISO, that would be easier even though I'd prefer to move to >> 1.4. >> >> Thanks for the help, >> Brad Landis >> >> > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > |
|
From: Bradlee L. <bra...@gm...> - 2009-11-17 16:40:16
|
Well, I found that I could use the hex address "0x378" instead of a /dev, at least until I can figure out how to load the correct module. Was there a reason that ppdev module was removed from the new kernel? Thanks, Brad On Mon, Nov 16, 2009 at 11:35 AM, Bradlee Landis <bra...@gm...> wrote: > I'm looking to upgrade to 1.4RC1, and found that "parport" is no > longer a module in the kernel. I can't seem to get lcd4linux to run, > because /dev/parport/0 doesn't exist, and the since the previous > module "parport" is not in the kernel, what do I need to use instead? > > Am I supposed to use /etc/modprobe.conf instead of /etc/modules/? It > looks to be the right file... > > I'm having to do this, because one of our new servers ethernet modules > needs the "e1000e" module, as the previous just needed "e1000". If > there was a way to get the e1000e module into 1.2.15 without having to > remake the ISO, that would be easier even though I'd prefer to move to > 1.4. > > Thanks for the help, > Brad Landis > |
|
From: Bradlee L. <bra...@gm...> - 2009-11-16 17:36:13
|
I'm looking to upgrade to 1.4RC1, and found that "parport" is no longer a module in the kernel. I can't seem to get lcd4linux to run, because /dev/parport/0 doesn't exist, and the since the previous module "parport" is not in the kernel, what do I need to use instead? Am I supposed to use /etc/modprobe.conf instead of /etc/modules/? It looks to be the right file... I'm having to do this, because one of our new servers ethernet modules needs the "e1000e" module, as the previous just needed "e1000". If there was a way to get the e1000e module into 1.2.15 without having to remake the ISO, that would be easier even though I'd prefer to move to 1.4. Thanks for the help, Brad Landis |
|
From: Dominar R. <pos...@ao...> - 2009-11-15 20:26:49
|
Hello community! Is it possible to use DL as an wireless lan access point? I could set an IP address to my wlan card, but I couldn't set the ssid and encryption. Any ideas? Greetings DR. |
|
From: Serge L. <fi...@in...> - 2009-11-04 06:44:16
|
Bradlee Landis wrote: > > Is the conntrack-tools package in DL1.4? Yes, it is. Serge |
|
From: Bradlee L. <bra...@gm...> - 2009-11-03 21:47:34
|
Well, I found an email in the development list, and it looks like this is a known issue with cutter. Is the conntrack-tools package in DL1.4? On Tue, Nov 3, 2009 at 11:55 AM, Bradlee Landis <bra...@gm...> wrote: > I'm trying to find a program to kill connections, but the program > "cutter" does not seem to work. It always says "No matching > connections found." Is this a known issue? Are there alternate > programs to do the same thing? > > Thanks, > Brad > |
|
From: Bradlee L. <bra...@gm...> - 2009-11-03 17:55:35
|
I'm trying to find a program to kill connections, but the program "cutter" does not seem to work. It always says "No matching connections found." Is this a known issue? Are there alternate programs to do the same thing? Thanks, Brad |
|
From: Heiko Z. <he...@zu...> - 2009-10-27 11:57:44
|
Quoting Bruce Smith <bw...@re...>: >>> Do I need to include a 'make buildorder' in my set of commands, >>> or is there something we can commit in the build system to fix it? >> >> You only have to re-run 'buildorder' if scripts got added, removed or the >> order got changed. >> I'm not sure if there's an easy way to catch that. >> If you want to play save, you can always add it to your build line. On my >> build machine this adds almost an hour to the build. :-( > > I thought my compiles ran noticeably faster recently. :-) > >>> I looked in build/scripts/.buildorder/rc*.d/* and didn't see any links >>> to any shorewall-xxxx scripts. (even after running 'cvs update') >> >> You had those links before you re-ran the buildorder. > > Probably. I was thinking the links were checked out in CVS, > but I doubt sym-links can be checked in or out. > > Otherwise we could just keep them updated in CVS. I'm actually toying with the idea to change the 'make makefile' thing a bit: 1) don't create the makefile on the fly, create it during 'buildorder' 2) move the makefiles into the build/folder (maybe a subfolder of it) 3) check the makefiles into CVS This way we would always have a current (good) version in CVS. If anyone messes with the order of things, it's his/her responsibility to run a 'make buildorder' and check the updates into CVS. If anyone is bored and wants to implement this, you're more then welcome, it's bug 18 in mantis. ;-) -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
|
From: Bruce S. <bw...@re...> - 2009-10-27 00:29:06
|
>> Do I need to include a 'make buildorder' in my set of commands, >> or is there something we can commit in the build system to fix it? > > You only have to re-run 'buildorder' if scripts got added, removed or the > order got changed. > I'm not sure if there's an easy way to catch that. > If you want to play save, you can always add it to your build line. On my > build machine this adds almost an hour to the build. :-( I thought my compiles ran noticeably faster recently. :-) >> I looked in build/scripts/.buildorder/rc*.d/* and didn't see any links >> to any shorewall-xxxx scripts. (even after running 'cvs update') > > You had those links before you re-ran the buildorder. Probably. I was thinking the links were checked out in CVS, but I doubt sym-links can be checked in or out. Otherwise we could just keep them updated in CVS. - BS |
|
From: Heiko Z. <he...@zu...> - 2009-10-26 23:47:00
|
> -----Original Message----- > From: Bruce Smith [mailto:bw...@re...] > Sent: Monday, October 26, 2009 9:43 AM > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] Unable to login with DL 1.4RC2 > > >> >> >> ERROR > >> >> >> /data/build/scripts/shorewall-common not found > >> >> >> (LINK=S19shorewall-common - SCRIPT=shorewall-common > >> >> >> make: *** [install] Error 1 > >> >> > > >> >> > OOPS :D > >> >> > > >> >> > I did a change to the build system a few weeks back, so it > doesn't > >> >> > recalculate the build order every time, since insserv can run > up > >> to > >> >> an hour. > >> >> > I removed the shorewall-xxxxx scripts and now you have to > >> regenerate > >> >> the > >> >> > build order. > >> >> > > >> >> > make buildorder > >> >> > >> >> So run "make buildorder", then continue with "make install iso > dist" > >> > > >> > Correct. > >> > Buildorder is automatically invoked if the > build/scripts/.buildorder > >> > directory doesn't exist, that's why you didn't run into it before. > >> > >> Since this aborted in the 'install' phase, I'm wondering if the > >> 'build' worked for shorewall-common? Do I need to build > >> shorewall-common before the make-install? > > > > There is no more shorewall-common (or any of the shorewall-xxxx > scripts). > > It's now only the new shorewall script. As far as I remember it's > doesn't > > compile anything, so it should only do something during the > 'install'. > > OK, that worked. > > What do we need to do for future mrproper compiles? > > Do I need to include a 'make buildorder' in my set of commands, > or is there something we can commit in the build system to fix it? You only have to re-run 'buildorder' if scripts got added, removed or the order got changed. I'm not sure if there's an easy way to catch that. If you want to play save, you can always add it to your build line. On my build machine this adds almost an hour to the build. :-( > I looked in build/scripts/.buildorder/rc*.d/* and didn't see any links > to any shorewall-xxxx scripts. (even after running 'cvs update') You had those links before you re-ran the buildorder. Heiko |
|
From: Bruce S. <bw...@re...> - 2009-10-26 14:49:39
|
>> >> >> ERROR >> >> >> /data/build/scripts/shorewall-common not found >> >> >> (LINK=S19shorewall-common - SCRIPT=shorewall-common >> >> >> make: *** [install] Error 1 >> >> > >> >> > OOPS :D >> >> > >> >> > I did a change to the build system a few weeks back, so it doesn't >> >> > recalculate the build order every time, since insserv can run up >> to >> >> an hour. >> >> > I removed the shorewall-xxxxx scripts and now you have to >> regenerate >> >> the >> >> > build order. >> >> > >> >> > make buildorder >> >> >> >> So run "make buildorder", then continue with "make install iso dist" >> > >> > Correct. >> > Buildorder is automatically invoked if the build/scripts/.buildorder >> > directory doesn't exist, that's why you didn't run into it before. >> >> Since this aborted in the 'install' phase, I'm wondering if the >> 'build' worked for shorewall-common? Do I need to build >> shorewall-common before the make-install? > > There is no more shorewall-common (or any of the shorewall-xxxx scripts). > It's now only the new shorewall script. As far as I remember it's doesn't > compile anything, so it should only do something during the 'install'. OK, that worked. What do we need to do for future mrproper compiles? Do I need to include a 'make buildorder' in my set of commands, or is there something we can commit in the build system to fix it? I looked in build/scripts/.buildorder/rc*.d/* and didn't see any links to any shorewall-xxxx scripts. (even after running 'cvs update') - BS |
|
From: Heiko Z. <he...@zu...> - 2009-10-25 18:23:46
|
> -----Original Message----- > From: Bruce Smith [mailto:bw...@re...] > Sent: Sunday, October 25, 2009 12:38 PM > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] Unable to login with DL 1.4RC2 > > >> >> ERROR > >> >> /data/build/scripts/shorewall-common not found > >> >> (LINK=S19shorewall-common - SCRIPT=shorewall-common > >> >> make: *** [install] Error 1 > >> > > >> > OOPS :D > >> > > >> > I did a change to the build system a few weeks back, so it doesn't > >> > recalculate the build order every time, since insserv can run up > to > >> an hour. > >> > I removed the shorewall-xxxxx scripts and now you have to > regenerate > >> the > >> > build order. > >> > > >> > make buildorder > >> > >> So run "make buildorder", then continue with "make install iso dist" > ? > > > > Correct. > > Buildorder is automatically invoked if the build/scripts/.buildorder > > directory doesn't exist, that's why you didn't run into it before. > > Since this aborted in the 'install' phase, I'm wondering if the > 'build' worked for shorewall-common? Do I need to build > shorewall-common before the make-install? There is no more shorewall-common (or any of the shorewall-xxxx scripts). It's now only the new shorewall script. As far as I remember it's doesn't compile anything, so it should only do something during the 'install'. Heiko |
|
From: Bruce S. <bw...@re...> - 2009-10-25 17:38:30
|
>> >> ERROR >> >> /data/build/scripts/shorewall-common not found >> >> (LINK=S19shorewall-common - SCRIPT=shorewall-common >> >> make: *** [install] Error 1 >> > >> > OOPS :D >> > >> > I did a change to the build system a few weeks back, so it doesn't >> > recalculate the build order every time, since insserv can run up to >> an hour. >> > I removed the shorewall-xxxxx scripts and now you have to regenerate >> the >> > build order. >> > >> > make buildorder >> >> So run "make buildorder", then continue with "make install iso dist" ? > > Correct. > Buildorder is automatically invoked if the build/scripts/.buildorder > directory doesn't exist, that's why you didn't run into it before. Since this aborted in the 'install' phase, I'm wondering if the 'build' worked for shorewall-common? Do I need to build shorewall-common before the make-install? - BS |
|
From: Heiko Z. <he...@zu...> - 2009-10-25 15:58:30
|
> -----Original Message----- > From: Bruce Smith [mailto:bw...@re...] > Sent: Sunday, October 25, 2009 9:08 AM > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] Unable to login with DL 1.4RC2 > > >> > Thanks Heiko but I need the server version... > >> > >> I tried making a server version for you last night, > >> but it aborted with this error: > >> > >> ... > >> executing shadow with option install (in /data/build/tmp/shadow- > 4.1.0) > >> ERROR > >> /data/build/scripts/shorewall-common not found > >> (LINK=S19shorewall-common - SCRIPT=shorewall-common > >> make: *** [install] Error 1 > > > > OOPS :D > > > > I did a change to the build system a few weeks back, so it doesn't > > recalculate the build order every time, since insserv can run up to > an hour. > > I removed the shorewall-xxxxx scripts and now you have to regenerate > the > > build order. > > > > make buildorder > > So run "make buildorder", then continue with "make install iso dist" ? Correct. Buildorder is automatically invoked if the build/scripts/.buildorder directory doesn't exist, that's why you didn't run into it before. Heiko |
|
From: Bruce S. <bw...@re...> - 2009-10-25 14:08:35
|
>> > Thanks Heiko but I need the server version... >> >> I tried making a server version for you last night, >> but it aborted with this error: >> >> ... >> executing shadow with option install (in /data/build/tmp/shadow-4.1.0) >> ERROR >> /data/build/scripts/shorewall-common not found >> (LINK=S19shorewall-common - SCRIPT=shorewall-common >> make: *** [install] Error 1 > > OOPS :D > > I did a change to the build system a few weeks back, so it doesn't > recalculate the build order every time, since insserv can run up to an hour. > I removed the shorewall-xxxxx scripts and now you have to regenerate the > build order. > > make buildorder So run "make buildorder", then continue with "make install iso dist" ? - BS |
|
From: Dominic R. <dl...@ed...> - 2009-10-25 13:58:59
|
Heiko Zuerker wrote: > I uploaded a new -server build into the testing directory, give that one a > try and let us know if it's behaving better. > > Heiko Thanks I am trying that now, will let you know if the problem recurs (for the time being I have taken out Serge's syslog-ng fix). Dominic |
|
From: Heiko Z. <he...@zu...> - 2009-10-25 13:24:32
|
> -----Original Message----- > From: Bruce Smith [mailto:bw...@re...] > Sent: Sunday, October 25, 2009 7:17 AM > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] Unable to login with DL 1.4RC2 > > > Thanks Heiko but I need the server version... > > I tried making a server version for you last night, > but it aborted with this error: > > ... > executing shadow with option install (in /data/build/tmp/shadow-4.1.0) > ERROR > /data/build/scripts/shorewall-common not found > (LINK=S19shorewall-common - SCRIPT=shorewall-common > make: *** [install] Error 1 > > > Anyone? OOPS :D I did a change to the build system a few weeks back, so it doesn't recalculate the build order every time, since insserv can run up to an hour. I removed the shorewall-xxxxx scripts and now you have to regenerate the build order. make buildorder c ya Heiko |
|
From: Bruce S. <bw...@re...> - 2009-10-25 12:37:49
|
> Thanks Heiko but I need the server version... I tried making a server version for you last night, but it aborted with this error: ... executing shadow with option install (in /data/build/tmp/shadow-4.1.0) ERROR /data/build/scripts/shorewall-common not found (LINK=S19shorewall-common - SCRIPT=shorewall-common make: *** [install] Error 1 Anyone? - BS |
|
From: Heiko Z. <he...@zu...> - 2009-10-24 14:42:54
|
I uploaded a new -server build into the testing directory, give that one a try and let us know if it's behaving better. Heiko |
|
From: Dominic R. <dl...@ed...> - 2009-10-23 12:52:52
|
Heiko Zuerker wrote:
> Quoting Dominic Raferd <dl...@ed...>:
>> My inability to login did not occur immediately but only after DL had
>> been running for some days or weeks. My /var/log/messages shows
>> things like:
>> Oct 20 16:04:55 src@me login[8918]: pam_unix(login:session): session
>> opened for user root by LOGIN(uid=0)
>> Oct 20 16:04:55 src@me login[12927]: ROOT LOGIN on 'tty1'
>> Oct 20 16:07:31 src@me login[8918]: pam_unix(login:session): session
>> closed for user root
>>
>> The last line is me doing CTRL+C, I think. So it looks to me as if login
>> proceeded okay; I guess it is whatever daemon responds to a login (after
>> a login has succeeded) that is failing (agetty?)
>>
> This is weird.
> I have my servers running for weeks with the grsec version of DL and never experienced this issue.
> I'll compiling a new server version when I get a chance, so you can test a newer release.
Sorry I wrote that quite early in the morning. Now I look more closely
at what I posted I see that the login was on Oct 20; my attempted logins
on Oct 22 don't appear in /var/log/messages at all, in fact *nothing*
appears there since Oct 21 04:41 ('-- MARK --') - until I rebooted Oct
22 19:09. It looks as if my cron jobs had stopped working in the
intervening period, as had syslog-ng. Apache and Samba were definitely
still working through this period (Postfix I don't know).
|
50 messages has been excluded from this view by a project administrator.
