You can subscribe to this list here.
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(20) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
(91) |
Feb
(111) |
Mar
(226) |
Apr
(65) |
May
(197) |
Jun
(202) |
Jul
(92) |
Aug
(87) |
Sep
(120) |
Oct
(133) |
Nov
(89) |
Dec
(155) |
2008 |
Jan
(251) |
Feb
(136) |
Mar
(174) |
Apr
(149) |
May
(56) |
Jun
(32) |
Jul
(36) |
Aug
(171) |
Sep
(245) |
Oct
(244) |
Nov
(218) |
Dec
(272) |
2009 |
Jan
(113) |
Feb
(119) |
Mar
(192) |
Apr
(117) |
May
(93) |
Jun
(46) |
Jul
(80) |
Aug
(54) |
Sep
(109) |
Oct
(70) |
Nov
(145) |
Dec
(110) |
2010 |
Jan
(137) |
Feb
(87) |
Mar
(45) |
Apr
(157) |
May
(58) |
Jun
(99) |
Jul
(188) |
Aug
(136) |
Sep
(101) |
Oct
(100) |
Nov
(61) |
Dec
(60) |
2011 |
Jan
(84) |
Feb
(43) |
Mar
(70) |
Apr
(17) |
May
(69) |
Jun
(28) |
Jul
(43) |
Aug
(21) |
Sep
(151) |
Oct
(120) |
Nov
(84) |
Dec
(101) |
2012 |
Jan
(119) |
Feb
(82) |
Mar
(70) |
Apr
(115) |
May
(66) |
Jun
(131) |
Jul
(70) |
Aug
(65) |
Sep
(66) |
Oct
(86) |
Nov
(197) |
Dec
(81) |
2013 |
Jan
(65) |
Feb
(48) |
Mar
(32) |
Apr
(68) |
May
(98) |
Jun
(59) |
Jul
(41) |
Aug
(52) |
Sep
(42) |
Oct
(37) |
Nov
(10) |
Dec
(27) |
2014 |
Jan
(61) |
Feb
(34) |
Mar
(30) |
Apr
(52) |
May
(45) |
Jun
(40) |
Jul
(28) |
Aug
(9) |
Sep
(39) |
Oct
(69) |
Nov
(55) |
Dec
(19) |
2015 |
Jan
(13) |
Feb
(21) |
Mar
(5) |
Apr
(14) |
May
(30) |
Jun
(51) |
Jul
(31) |
Aug
(12) |
Sep
(29) |
Oct
(15) |
Nov
(24) |
Dec
(16) |
2016 |
Jan
(62) |
Feb
(76) |
Mar
(30) |
Apr
(43) |
May
(46) |
Jun
(62) |
Jul
(21) |
Aug
(49) |
Sep
(67) |
Oct
(27) |
Nov
(26) |
Dec
(38) |
2017 |
Jan
(7) |
Feb
(12) |
Mar
(69) |
Apr
(59) |
May
(54) |
Jun
(40) |
Jul
(76) |
Aug
(82) |
Sep
(92) |
Oct
(51) |
Nov
(32) |
Dec
(30) |
2018 |
Jan
(22) |
Feb
(25) |
Mar
(34) |
Apr
(35) |
May
(37) |
Jun
(21) |
Jul
(69) |
Aug
(55) |
Sep
(17) |
Oct
(67) |
Nov
(9) |
Dec
(5) |
2019 |
Jan
(19) |
Feb
(12) |
Mar
(15) |
Apr
(19) |
May
|
Jun
(27) |
Jul
(27) |
Aug
(25) |
Sep
(25) |
Oct
(27) |
Nov
(10) |
Dec
(14) |
2020 |
Jan
(22) |
Feb
(20) |
Mar
(36) |
Apr
(40) |
May
(52) |
Jun
(35) |
Jul
(21) |
Aug
(32) |
Sep
(71) |
Oct
(27) |
Nov
(11) |
Dec
(16) |
2021 |
Jan
(16) |
Feb
(21) |
Mar
(21) |
Apr
(27) |
May
(17) |
Jun
|
Jul
(2) |
Aug
(22) |
Sep
(23) |
Oct
(7) |
Nov
(11) |
Dec
(28) |
2022 |
Jan
(23) |
Feb
(18) |
Mar
(9) |
Apr
(15) |
May
(15) |
Jun
(7) |
Jul
(8) |
Aug
(15) |
Sep
(1) |
Oct
|
Nov
(11) |
Dec
(10) |
2023 |
Jan
(14) |
Feb
(10) |
Mar
(11) |
Apr
(13) |
May
(2) |
Jun
(30) |
Jul
(1) |
Aug
(15) |
Sep
(13) |
Oct
(3) |
Nov
(25) |
Dec
(5) |
2024 |
Jan
(3) |
Feb
(10) |
Mar
(9) |
Apr
|
May
(1) |
Jun
(15) |
Jul
(7) |
Aug
(10) |
Sep
(3) |
Oct
(8) |
Nov
(6) |
Dec
(15) |
2025 |
Jan
(3) |
Feb
(1) |
Mar
(7) |
Apr
(5) |
May
(13) |
Jun
(16) |
Jul
(1) |
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Lonnie A. <li...@lo...> - 2007-03-12 17:23:55
|
Darrick, I am now using Astlinux 0.4.5-RC2 on my net4801 at my home. Mostly SIP (including inbound registrations) and a little IAX2. No problems to report! I will sleep better now with asterisk 1.2.16 and udp/5060 open to it. Your (and of course Kristian's) hard work is appreciated. Lonnie On Mar 11, 2007, at 7:51 PM, Darrick Hartman wrote: > Images for Astlinux 0.4.5-RC2 will be available later this evening > on my > website. Significant changes include the updating of the timezone > files > that are used by Asterisk. Note that the system time does not use > these > files and relies on proper setting of the TZ_TIMEZONE variable. > > http://www.djhsolutions.com/astlinux > > The VIA and i586 images are ready for download. The wrap and net4801 > will follow later this evening. |
From: Sebastian A. <sp...@sy...> - 2007-03-12 17:00:19
|
Kristian wrote: > On 3/12/07, Sebastian Auriol <sp...@sy...> wrote: >> >> Perhaps it got confused about which version of zaptel to use: >> >> [seb@IVRA1 astlinux-0.4]$ ls build_i586/zaptel* -l -d >> lrwxrwxrwx 1 seb asterisk 48 Jan 18 18:02 build_i586/zaptel -> >> /home/seb/astlinux-0.4/build_i586/zaptel-1.2.9.1 >> drwxr-xr-x 9 seb asterisk 4096 Mar 9 19:42 build_i586/zaptel-1.2.15 >> drwxr-xr-x 8 seb asterisk 8192 Mar 9 19:41 >> build_i586/zaptel-1.2.9.1 [seb@IVRA1 astlinux-0.4]$ >> >> I did a make clean before a svn update, but not a make distclean (to >> save time - I thought I could get away with not rebuilding the >> toolchain)... >> >> Kind regards, >> >> Sebastian >> > > Sebastian, > > That is possible. Manually remove your zaptel directories > and try again. I tried removing the old zaptel directories but that didn't help (I didn't try removing the new zaptel directory) so I did a "make dirclean" and then a "rm -f -r build_i586" and then tried another make. It looks like there are still issues and that maybe the old version of zaptel was a red herring. I note that zaptel-1.2.15 has been extracted but has not been built yet. I don't know which is supposed to be built first - zaptel or wanpipe? But maybe this is the issue here: "cc1: /usr/src/zaptel: not a directory" Taken from the log below: make[3]: Leaving directory `/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/util/wancfg' make[2]: Leaving directory `/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/util' Done rm: cannot remove `/usr/include/linux/if_wanpipe.h': Permission denied rm: cannot remove `/usr/include/linux/if_wanpipe_common.h': Permission denied rm: cannot remove `/usr/include/linux/sdla_asy.h': Permission denied rm: cannot remove `/usr/include/linux/sdla_chdlc.h': Permission denied rm: cannot remove `/usr/include/linux/sdla_fr.h': Permission denied rm: cannot remove `/usr/include/linux/sdla_ppp.h': Permission denied rm: cannot remove `/usr/include/linux/sdla_x25.h': Permission denied rm: cannot remove `/usr/include/linux/sdladrv.h': Permission denied rm: cannot remove `/usr/include/linux/sdlapci.h': Permission denied rm: cannot remove `/usr/include/linux/sdlasfm.h': Permission denied rm: cannot remove `/usr/include/linux/wanpipe.h': Permission denied rm: cannot remove `/usr/include/linux/wanrouter.h': Permission denied make KBUILD_VERBOSE=0 -C /home/seb/astlinux-0.4/build_i586/linux-2.6.16.12 SUBDIRS=/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/ src/net EXTRA_FLAGS="-I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kd rivers/include -I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/includ e/annexg -I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/wanec -D__LINUX__ -I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/wanec -I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/wanec/ oct6100_api -I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/wanec/ oct6100_api/include -I/home/seb/astlinux-0.4/build_i586/linux-2.6.16.12/include/linux -I/home/seb/astlinux-0.4/build_i586/zaptel-1.2.15 " ZAPDIR=/home/seb/astlinux-0.4/build_i586/zaptel-1.2.15 HOMEDIR=/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8 modules make[2]: Entering directory `/home/seb/astlinux-0.4/build_i586/linux-2.6.16.12' CC [M] /home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/src/net/ ../wanrouter/af_wanpipe_src.o cc1: /usr/src/zaptel: not a directory make[3]: *** [/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/src/net /../wanrouter/af_wanpipe_src.o] Error 1 make[2]: *** [_module_/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers /src/net] Error 2 make[2]: Leaving directory `/home/seb/astlinux-0.4/build_i586/linux-2.6.16.12' make[1]: *** [all_kmod] Error 2 make[1]: Leaving directory `/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8' make: *** [/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/.built] Error 2 [seb@IVRA1 astlinux-0.4]$ Kind regards, Sebastian |
From: Manuel <lis...@gm...> - 2007-03-12 16:34:29
|
Ehhhh, thank you very much Kristian, I will try it this night. Tomorrow will tell you if works or not. Regards, --- Manuel -----Mensaje original----- De: ast...@li... [mailto:ast...@li...] En nombre de Kristian Kielhofner Enviado el: lunes, 12 de marzo de 2007 17:26 Para: AstLinux Users Mailing List Asunto: Re: [Astlinux-users] Add drivers 0.4 On 3/12/07, Darrick Hartman <dha...@dj...> wrote: > Manuel wrote: > > Darrick, > > > > I am again with my problems. Please, can you guide me how can I install the > > drivers for my NIC in AstLinux? Not in details only a orientation. This > > weekend I have tried to make a package with the drivers from Realtek without > > success. In the drivers not appears a configure file only a makefile and I > > have tried several thinks but not works. My Linux knowledge is very limited. > > I am really very frustrated. If I use trunk the image file not boot. If use > > 0.4 I need to install a NIC and remove the ISDN card. > > > > > Manuel, > > If I recall this was a realtek driver? 0.4 branch builds r8169 kernel > module by default if you use either the i586 or VIA image. > > Did you try modprobe 8169? > > Can you do an lspci -v > file.txt then attach file.txt to an email to me > so we can see exactly what hardware you are working with? Also please > supply the motherboard brand and model. > > Also tell us what specific astlinux image you are using? If this is an > image you built yourself, please try the i586-RC2 image available here: > http://www.djhsolutions.com/astlinux > > Darrick > Darrick, Manuel's problem is that his card's PCI ID is too new for the driver in 2.6.16.12. He has already sent me the output of lspci and we have confirmed that it does work with newer kernels. Manuel, 0.4 is the stable branch of AstLinux. We are not going to change kernel versions in the stable branch. I have just committed a kernel patch for the r8169 driver for 2.6.16.12 in the 0.4 branch that adds the PCI IDs from the r8169 driver in 2.6.20. This is a trivial patch and it should not effect the quality of the 0.4 branch. The next releases that Darrick releases should have this patch. -- Kristian Kielhofner ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
From: Kristian K. <kri...@gm...> - 2007-03-12 16:28:48
|
On 3/12/07, Sebastian Auriol <sp...@sy...> wrote: > > Perhaps it got confused about which version of zaptel to use: > > [seb@IVRA1 astlinux-0.4]$ ls build_i586/zaptel* -l -d > lrwxrwxrwx 1 seb asterisk 48 Jan 18 18:02 build_i586/zaptel -> > /home/seb/astlinux-0.4/build_i586/zaptel-1.2.9.1 > drwxr-xr-x 9 seb asterisk 4096 Mar 9 19:42 build_i586/zaptel-1.2.15 > drwxr-xr-x 8 seb asterisk 8192 Mar 9 19:41 build_i586/zaptel-1.2.9.1 > [seb@IVRA1 astlinux-0.4]$ > > I did a make clean before a svn update, but not a make distclean (to save > time - I thought I could get away with not rebuilding the toolchain)... > > Also, with a single processor machine, are there benefits to running two > simultaneous jobs? > > Kind regards, > > Sebastian > Sebastian, That is possible. Manually remove your zaptel directories and try again. The rule of thumb for parallel compiles is to use N CPUs + 1. So on a uni machine you would use -j2. That is why it is the default. :) I have a few eight way machines that I run anywhere from -j10 to -j12 on. -- Kristian Kielhofner |
From: Kristian K. <kri...@gm...> - 2007-03-12 16:25:40
|
On 3/12/07, Darrick Hartman <dha...@dj...> wrote: > Manuel wrote: > > Darrick, > > > > I am again with my problems. Please, can you guide me how can I install the > > drivers for my NIC in AstLinux? Not in details only a orientation. This > > weekend I have tried to make a package with the drivers from Realtek without > > success. In the drivers not appears a configure file only a makefile and I > > have tried several thinks but not works. My Linux knowledge is very limited. > > I am really very frustrated. If I use trunk the image file not boot. If use > > 0.4 I need to install a NIC and remove the ISDN card. > > > > > Manuel, > > If I recall this was a realtek driver? 0.4 branch builds r8169 kernel > module by default if you use either the i586 or VIA image. > > Did you try modprobe 8169? > > Can you do an lspci -v > file.txt then attach file.txt to an email to me > so we can see exactly what hardware you are working with? Also please > supply the motherboard brand and model. > > Also tell us what specific astlinux image you are using? If this is an > image you built yourself, please try the i586-RC2 image available here: > http://www.djhsolutions.com/astlinux > > Darrick > Darrick, Manuel's problem is that his card's PCI ID is too new for the driver in 2.6.16.12. He has already sent me the output of lspci and we have confirmed that it does work with newer kernels. Manuel, 0.4 is the stable branch of AstLinux. We are not going to change kernel versions in the stable branch. I have just committed a kernel patch for the r8169 driver for 2.6.16.12 in the 0.4 branch that adds the PCI IDs from the r8169 driver in 2.6.20. This is a trivial patch and it should not effect the quality of the 0.4 branch. The next releases that Darrick releases should have this patch. -- Kristian Kielhofner |
From: Darrick H. <dha...@dj...> - 2007-03-12 16:11:52
|
canuck15 wrote: > So does the new 0.4.5 image have Wanpipe drivers. Specifically, support > for Sangoma A200 cards? > Yes wanpipe drivers were added. These need to be tested, so please test away and report back. Thanks, Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com |
From: canuck15 <can...@ho...> - 2007-03-12 15:57:15
|
So does the new 0.4.5 image have Wanpipe drivers. Specifically, support for Sangoma A200 cards? |
From: Darrick H. <dha...@dj...> - 2007-03-12 12:36:25
|
Manuel wrote: > Darrick, > > I am again with my problems. Please, can you guide me how can I install the > drivers for my NIC in AstLinux? Not in details only a orientation. This > weekend I have tried to make a package with the drivers from Realtek without > success. In the drivers not appears a configure file only a makefile and I > have tried several thinks but not works. My Linux knowledge is very limited. > I am really very frustrated. If I use trunk the image file not boot. If use > 0.4 I need to install a NIC and remove the ISDN card. > > Manuel, If I recall this was a realtek driver? 0.4 branch builds r8169 kernel module by default if you use either the i586 or VIA image. Did you try modprobe 8169? Can you do an lspci -v > file.txt then attach file.txt to an email to me so we can see exactly what hardware you are working with? Also please supply the motherboard brand and model. Also tell us what specific astlinux image you are using? If this is an image you built yourself, please try the i586-RC2 image available here: http://www.djhsolutions.com/astlinux Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com |
From: Manuel <lis...@gm...> - 2007-03-12 12:21:16
|
Darrick, I am again with my problems. Please, can you guide me how can I install the drivers for my NIC in AstLinux? Not in details only a orientation. This weekend I have tried to make a package with the drivers from Realtek without success. In the drivers not appears a configure file only a makefile and I have tried several thinks but not works. My Linux knowledge is very limited. I am really very frustrated. If I use trunk the image file not boot. If use 0.4 I need to install a NIC and remove the ISDN card. Thanks & regards, -- Manuel |
From: Darrick H. <dha...@dj...> - 2007-03-12 11:59:39
|
Matt Riddell (NZ) wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Sorry if this is an obvious question, I haven't the time to check out > trunk at the mo. > > Anyone know if there's an AstLinux Environment with 1.4 's in it? > > Or is the best way to go to simply update the versions of Asterisk in > the build process from the dev environment? > Matt, Short answer is no. Not at the moment. Long answer. I'm working on releasing 0.4.5. Kristian is working on some major structural changes in trunk (changes that are needed to make upgrading in the future easier). After I get 0.4.5 out, I might have some time to take a look at what it will take to get 1.4.x to build in Astlinux. It's on the radar and with 1.4.1 out, most of the bugs should be worked out. It makes sense to have it included, but it will take some time as the patches for 1.2 will not just drop into place. Some of them won't be needed and quite possibly some new ones will have to be added. If you even look at the difference between the 0.4 branch and trunk, you'll see that there are several patches that Kristian has added that are not in 0.4, even though we're using the same version of Asterisk. In trunk, he's looking at adding realtime support. By realtime, we don't mean dynamic dialplans. We mean faster interaction with the hardware. This includes a realtime kernel and some other changes. Believe it or not, that the minor change in trunk compared to some of the other changes. If you wanted to get started, you could look at zaptel 1.4. That may be an easier package than asterisk itself. The big issue there will be the other packages that depend on zaptel (wanpipe and rhino). Re-creating the patches required to get zaptel to build would be easier than what will be needed for asterisk. Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com |
From: Sebastian A. <sp...@sy...> - 2007-03-12 09:41:34
|
Kristian Kielhofner wrote: > On 3/10/07, Sebastian Auriol <sp...@sy...> wrote: >> AstLinux 0.4 branch from yesterday fails to compile in the wanpipe >> package (which is enabled by default): snip >> BTW, this was with 1 concurrent job set to run; i385; i586; Generic >> i586 and VIA. >> >> Kind regards, >> >> Sebastian >> > > Sebastian, > > I just built 0.4 from scratch for geni586 with concurrent jobs set > to 10. Everything went fine. > > The rm /usr/include/linux errors are "normal". That's another > reason why you shouldn't run the build environment as root! > > Anyways, it looks like you haven't unpacked zaptel ($(ZAPTEL_DIR) > was not set, so the wanpipe makefile looked in /usr/src/zaptel by > default). Can you make sure that zaptel was unpacked (look in > build_i586 for zaptel-*)? Perhaps it got confused about which version of zaptel to use: [seb@IVRA1 astlinux-0.4]$ ls build_i586/zaptel* -l -d lrwxrwxrwx 1 seb asterisk 48 Jan 18 18:02 build_i586/zaptel -> /home/seb/astlinux-0.4/build_i586/zaptel-1.2.9.1 drwxr-xr-x 9 seb asterisk 4096 Mar 9 19:42 build_i586/zaptel-1.2.15 drwxr-xr-x 8 seb asterisk 8192 Mar 9 19:41 build_i586/zaptel-1.2.9.1 [seb@IVRA1 astlinux-0.4]$ I did a make clean before a svn update, but not a make distclean (to save time - I thought I could get away with not rebuilding the toolchain)... Also, with a single processor machine, are there benefits to running two simultaneous jobs? Kind regards, Sebastian |
From: Matt R. (NZ) <mat...@si...> - 2007-03-12 03:47:21
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sorry if this is an obvious question, I haven't the time to check out trunk at the mo. Anyone know if there's an AstLinux Environment with 1.4 's in it? Or is the best way to go to simply update the versions of Asterisk in the build process from the dev environment? - -- Cheers, Matt Riddell Director _______________________________________________ http://www.sineapps.com/news.php (Daily Asterisk News - html) http://wap.sineapps.com (Daily Asterisk News for your cellphone) http://feeds.feedburner.com/AsteriskNews (Daily Asterisk News - rss) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF9M1DS6d5vy0jeVcRArYrAJoDVxalNpbiUZb4CaHK284L+9sHwgCdGYJB RqIXzBkpQUnrpc7FkN0nbVk= =lGR3 -----END PGP SIGNATURE----- |
From: Tom L. <the...@gm...> - 2007-03-12 02:03:48
|
File replacement works well for Pacific Daylight time. FYI. Voicemail timestamps are accurate. On 3/11/07, Darrick Hartman <dha...@dj...> wrote: > As you probably know several areas recently changed their start of > daylight savings time to supposedly help conserve energy. We won't go > into that whole discussion, but suffice it to say that we've had to make > some changes. I'll provide a little history on the zoneinfo files and > how they tie into Astlinux along with the TZ variable, then give you a > link where you can grab some replacement files. > > Astlinux is built on uclibc. uclibc it self does not use the > information in the zoneinfo files usually found in /usr/share/zoneinfo > and linked from /etc/localtime. Asterisk however DOES read these files > directly rather than access this data via the *libc. This is how we > ended up with two variables in rc.conf referring to timezones. TZ sets > the timezone for the system, TIMEZONE sets it for Asterisk. > > If you don't mind the time on your voicemails being off by the daylight > savings time offset, you don't need to do anything. > > For the foreseeable future, the TZ variable will need to be adjusted as > mentioned in my previous email. Again, this is for the system time. > > The TIMEZONE variable can stay as is, but the zoneinfo files need to be > updated. I have a tar.gz file available which has updated timezone > data. This has not been fully tested, but it works on my test system. > I will be creating new images based on 0.4 branch which will have the > updated files. You can either update to these images or grab the file > and overwrite the files on your current image. I only recommend doing > this if you really know what you are doing. > > http://www.djhsolutions.com/astlinux/tzdata.tar.gz > > To overwrite the current files, you will need to mount your system > read-write. > Remove the existing files in /usr/share/zoneinfo > Replace them with the files in that tar.gz file. > > Darrick > > -- > Darrick Hartman > DJH Solutions, LLC > http://www.djhsolutions.com > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > |
From: Darrick H. <dha...@dj...> - 2007-03-12 00:51:35
|
Images for Astlinux 0.4.5-RC2 will be available later this evening on my website. Significant changes include the updating of the timezone files that are used by Asterisk. Note that the system time does not use these files and relies on proper setting of the TZ_TIMEZONE variable. http://www.djhsolutions.com/astlinux The VIA and i586 images are ready for download. The wrap and net4801 will follow later this evening. Please assist in testing if you can, particularly the Sangoma hardware as I have no way to test that functionality. Regards, Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com |
From: Darrick H. <dha...@dj...> - 2007-03-11 21:35:24
|
Kristian Kielhofner wrote: > On 3/11/07, Darrick Hartman <dha...@dj...> wrote: > >> As you probably know several areas recently changed their start of >> daylight savings time to supposedly help conserve energy. We won't go >> into that whole discussion, but suffice it to say that we've had to make >> some changes. I'll provide a little history on the zoneinfo files and >> how they tie into Astlinux along with the TZ variable, then give you a >> link where you can grab some replacement files. >> >> Astlinux is built on uclibc. uclibc it self does not use the >> information in the zoneinfo files usually found in /usr/share/zoneinfo >> and linked from /etc/localtime. Asterisk however DOES read these files >> directly rather than access this data via the *libc. This is how we >> ended up with two variables in rc.conf referring to timezones. TZ sets >> the timezone for the system, TIMEZONE sets it for Asterisk. >> >> If you don't mind the time on your voicemails being off by the daylight >> savings time offset, you don't need to do anything. >> >> For the foreseeable future, the TZ variable will need to be adjusted as >> mentioned in my previous email. Again, this is for the system time. >> >> The TIMEZONE variable can stay as is, but the zoneinfo files need to be >> updated. I have a tar.gz file available which has updated timezone >> data. This has not been fully tested, but it works on my test system. >> I will be creating new images based on 0.4 branch which will have the >> updated files. You can either update to these images or grab the file >> and overwrite the files on your current image. I only recommend doing >> this if you really know what you are doing. >> >> http://www.djhsolutions.com/astlinux/tzdata.tar.gz >> >> To overwrite the current files, you will need to mount your system >> read-write. >> Remove the existing files in /usr/share/zoneinfo >> Replace them with the files in that tar.gz file. >> >> Darrick >> >> > > Darrick, > > I see the commit for 0.4. I am merging that into trunk right now. > Thanks a lot! > > I am thinking that it probably makes more sense to have these as a > package - glibc-tzdata, for instance. > > Either the user could compile it themselves (similar to Lonnie's > method) or we could just offer a binary tarball to download and > install. > > What do you think? > > > I almost have the package ready... -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com |
From: Kristian K. <kri...@gm...> - 2007-03-11 21:18:17
|
On 3/11/07, Darrick Hartman <dha...@dj...> wrote: > As you probably know several areas recently changed their start of > daylight savings time to supposedly help conserve energy. We won't go > into that whole discussion, but suffice it to say that we've had to make > some changes. I'll provide a little history on the zoneinfo files and > how they tie into Astlinux along with the TZ variable, then give you a > link where you can grab some replacement files. > > Astlinux is built on uclibc. uclibc it self does not use the > information in the zoneinfo files usually found in /usr/share/zoneinfo > and linked from /etc/localtime. Asterisk however DOES read these files > directly rather than access this data via the *libc. This is how we > ended up with two variables in rc.conf referring to timezones. TZ sets > the timezone for the system, TIMEZONE sets it for Asterisk. > > If you don't mind the time on your voicemails being off by the daylight > savings time offset, you don't need to do anything. > > For the foreseeable future, the TZ variable will need to be adjusted as > mentioned in my previous email. Again, this is for the system time. > > The TIMEZONE variable can stay as is, but the zoneinfo files need to be > updated. I have a tar.gz file available which has updated timezone > data. This has not been fully tested, but it works on my test system. > I will be creating new images based on 0.4 branch which will have the > updated files. You can either update to these images or grab the file > and overwrite the files on your current image. I only recommend doing > this if you really know what you are doing. > > http://www.djhsolutions.com/astlinux/tzdata.tar.gz > > To overwrite the current files, you will need to mount your system > read-write. > Remove the existing files in /usr/share/zoneinfo > Replace them with the files in that tar.gz file. > > Darrick > Darrick, I see the commit for 0.4. I am merging that into trunk right now. Thanks a lot! I am thinking that it probably makes more sense to have these as a package - glibc-tzdata, for instance. Either the user could compile it themselves (similar to Lonnie's method) or we could just offer a binary tarball to download and install. What do you think? -- Kristian Kielhofner |
From: Tony P. <To...@pl...> - 2007-03-11 20:51:41
|
Darrick, Like you I am in on this warm Wisconsin day fixing DST values... My rc.conf has TZ_TIMEZONE=3DCST+6CDT,M3.2.0/2,M11.1.0/2 If I just set TZ, I get UTC time on the date. I also assume that we need to comment out the TIMEZONE setting as well so it= doesn't use the /usr/share/zoneinfo/$TIMEZONE file in localtime. Thanks again, you saved me a lookup. Tony |
From: Darrick H. <dha...@dj...> - 2007-03-11 20:47:12
|
As you probably know several areas recently changed their start of daylight savings time to supposedly help conserve energy. We won't go into that whole discussion, but suffice it to say that we've had to make some changes. I'll provide a little history on the zoneinfo files and how they tie into Astlinux along with the TZ variable, then give you a link where you can grab some replacement files. Astlinux is built on uclibc. uclibc it self does not use the information in the zoneinfo files usually found in /usr/share/zoneinfo and linked from /etc/localtime. Asterisk however DOES read these files directly rather than access this data via the *libc. This is how we ended up with two variables in rc.conf referring to timezones. TZ sets the timezone for the system, TIMEZONE sets it for Asterisk. If you don't mind the time on your voicemails being off by the daylight savings time offset, you don't need to do anything. For the foreseeable future, the TZ variable will need to be adjusted as mentioned in my previous email. Again, this is for the system time. The TIMEZONE variable can stay as is, but the zoneinfo files need to be updated. I have a tar.gz file available which has updated timezone data. This has not been fully tested, but it works on my test system. I will be creating new images based on 0.4 branch which will have the updated files. You can either update to these images or grab the file and overwrite the files on your current image. I only recommend doing this if you really know what you are doing. http://www.djhsolutions.com/astlinux/tzdata.tar.gz To overwrite the current files, you will need to mount your system read-write. Remove the existing files in /usr/share/zoneinfo Replace them with the files in that tar.gz file. Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com |
From: Kristian K. <kri...@gm...> - 2007-03-11 20:11:07
|
On 3/10/07, Sebastian Auriol <sp...@sy...> wrote: > AstLinux 0.4 branch from yesterday fails to compile in the wanpipe package > (which is enabled by default): > > make[3]: Leaving directory > `/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/util/wancfg' > make[2]: Leaving directory > `/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/util' > Done > rm: cannot remove `/usr/include/linux/if_wanpipe.h': Permission denied > rm: cannot remove `/usr/include/linux/if_wanpipe_common.h': Permission > denied > rm: cannot remove `/usr/include/linux/sdla_asy.h': Permission denied > rm: cannot remove `/usr/include/linux/sdla_chdlc.h': Permission denied > rm: cannot remove `/usr/include/linux/sdla_fr.h': Permission denied > rm: cannot remove `/usr/include/linux/sdla_ppp.h': Permission denied > rm: cannot remove `/usr/include/linux/sdla_x25.h': Permission denied > rm: cannot remove `/usr/include/linux/sdladrv.h': Permission denied > rm: cannot remove `/usr/include/linux/sdlapci.h': Permission denied > rm: cannot remove `/usr/include/linux/sdlasfm.h': Permission denied > rm: cannot remove `/usr/include/linux/wanpipe.h': Permission denied > rm: cannot remove `/usr/include/linux/wanrouter.h': Permission denied > make KBUILD_VERBOSE=0 -C /home/seb/astlinux-0.4/build_i586/linux-2.6.16.12 > SUBDIRS=/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/ > src/net > EXTRA_FLAGS="-I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kd > rivers/include > -I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/includ > e/annexg > -I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/wanec > -D__LINUX__ > -I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/wanec > -I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/wanec/ > oct6100_api > -I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/wanec/ > oct6100_api/include > -I/home/seb/astlinux-0.4/build_i586/linux-2.6.16.12/include/linux > -I/home/seb/astlinux-0.4/build_i586/zaptel-1.2.15 " > ZAPDIR=/home/seb/astlinux-0.4/build_i586/zaptel-1.2.15 > HOMEDIR=/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8 modules > make[2]: Entering directory > `/home/seb/astlinux-0.4/build_i586/linux-2.6.16.12' > CC [M] > /home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/src/net/ > ../wanrouter/af_wanpipe_src.o > cc1: /usr/src/zaptel: not a directory > make[3]: *** > [/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/src/net > /../wanrouter/af_wanpipe_src.o] Error 1 > make[2]: *** > [_module_/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers > /src/net] Error 2 > make[2]: Leaving directory > `/home/seb/astlinux-0.4/build_i586/linux-2.6.16.12' > make[1]: *** [all_kmod] Error 2 > make[1]: Leaving directory > `/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8' > make: *** [/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/.built] Error > 2 > [seb@IVRA1 astlinux-0.4]$ > > BTW, this was with 1 concurrent job set to run; i385; i586; Generic i586 and > VIA. > > Kind regards, > > Sebastian > Sebastian, I just built 0.4 from scratch for geni586 with concurrent jobs set to 10. Everything went fine. The rm /usr/include/linux errors are "normal". That's another reason why you shouldn't run the build environment as root! Anyways, it looks like you haven't unpacked zaptel ($(ZAPTEL_DIR) was not set, so the wanpipe makefile looked in /usr/src/zaptel by default). Can you make sure that zaptel was unpacked (look in build_i586 for zaptel-*)? -- Kristian Kielhofner |
From: Darrick H. <dha...@dj...> - 2007-03-11 15:50:07
|
Until the new timezone data files are updated, you can correct the time on your system by using the following: Using Central Time Zone (US) as an example, in rc.conf replace TZ=CST6CDT with TZ=CST+6CDT,M3.2.0/2,M11.1.0/2 EST5EDT would become EST+5EDT,M3.2.0/2,M11.1.0/2 This is better explained here: http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap08.html After making the change, the easiest thing to do is reboot. That will re-create the /etc/TZ file (well actually /tmp/etc/TZ) on your system. Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com |
From: Darrick H. <dha...@dj...> - 2007-03-10 20:15:43
|
Sebastian Auriol wrote: > AstLinux 0.4 branch from yesterday fails to compile in the wanpipe package > (which is enabled by default): > > make[3]: Leaving directory > `/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/util/wancfg' > make[2]: Leaving directory > `/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/util' > Done > rm: cannot remove `/usr/include/linux/if_wanpipe.h': Permission denied > rm: cannot remove `/usr/include/linux/if_wanpipe_common.h': Permission > denied > > This seems odd. I haven't seen this problem with wanpipe. It should compile without any problems. I would suggest backing up your dl directory, removing your entire local svn repository and starting fresh with the default settings. Follow this exactly. After this works, then you can try other things: Make sure you are not root. 1). get the current svn branch 0.4 2). copy the contents of your backed up dl to dl in your newly created svn directory 3). copy astlinux.config to .config 4). make oldconfig 5). make menuconfig <-- change nothing! 6). make This should compile without problems. If there are problems, report back. > BTW, this was with 1 concurrent job set to run; i385; i586; Generic i586 and > VIA. > do not select both Generic i586 and VIA. You can only select one target device. You should also be able to leave the concurrent job setting at 2. I think we've caught most of the places where only 1 job can run at a time and replaced 'make' with $(MAKE1) which only runs one job at a time. Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com |
From: Sebastian A. <sp...@sy...> - 2007-03-10 19:38:31
|
AstLinux 0.4 branch from yesterday fails to compile in the wanpipe package (which is enabled by default): make[3]: Leaving directory `/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/util/wancfg' make[2]: Leaving directory `/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/util' Done rm: cannot remove `/usr/include/linux/if_wanpipe.h': Permission denied rm: cannot remove `/usr/include/linux/if_wanpipe_common.h': Permission denied rm: cannot remove `/usr/include/linux/sdla_asy.h': Permission denied rm: cannot remove `/usr/include/linux/sdla_chdlc.h': Permission denied rm: cannot remove `/usr/include/linux/sdla_fr.h': Permission denied rm: cannot remove `/usr/include/linux/sdla_ppp.h': Permission denied rm: cannot remove `/usr/include/linux/sdla_x25.h': Permission denied rm: cannot remove `/usr/include/linux/sdladrv.h': Permission denied rm: cannot remove `/usr/include/linux/sdlapci.h': Permission denied rm: cannot remove `/usr/include/linux/sdlasfm.h': Permission denied rm: cannot remove `/usr/include/linux/wanpipe.h': Permission denied rm: cannot remove `/usr/include/linux/wanrouter.h': Permission denied make KBUILD_VERBOSE=0 -C /home/seb/astlinux-0.4/build_i586/linux-2.6.16.12 SUBDIRS=/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/ src/net EXTRA_FLAGS="-I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kd rivers/include -I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/includ e/annexg -I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/wanec -D__LINUX__ -I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/wanec -I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/wanec/ oct6100_api -I/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/wanec/ oct6100_api/include -I/home/seb/astlinux-0.4/build_i586/linux-2.6.16.12/include/linux -I/home/seb/astlinux-0.4/build_i586/zaptel-1.2.15 " ZAPDIR=/home/seb/astlinux-0.4/build_i586/zaptel-1.2.15 HOMEDIR=/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8 modules make[2]: Entering directory `/home/seb/astlinux-0.4/build_i586/linux-2.6.16.12' CC [M] /home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/src/net/ ../wanrouter/af_wanpipe_src.o cc1: /usr/src/zaptel: not a directory make[3]: *** [/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers/src/net /../wanrouter/af_wanpipe_src.o] Error 1 make[2]: *** [_module_/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/patches/kdrivers /src/net] Error 2 make[2]: Leaving directory `/home/seb/astlinux-0.4/build_i586/linux-2.6.16.12' make[1]: *** [all_kmod] Error 2 make[1]: Leaving directory `/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8' make: *** [/home/seb/astlinux-0.4/build_i586/wanpipe-3.1.0.p8/.built] Error 2 [seb@IVRA1 astlinux-0.4]$ BTW, this was with 1 concurrent job set to run; i385; i586; Generic i586 and VIA. Kind regards, Sebastian |
From: Manuel D. <man...@te...> - 2007-03-09 21:18:54
|
Darrick, Kristian, The lcd4linux package that I have sent in my last email is working in my system. The lcd4linux.conf is a sample for my picoLCD. The Init file I = don=92t know if works or not. Please verify it and if you think that the package = has enough quality and is useful for Astlinux community includes it in 0.4 = and trunk. Best regards, -- Manuel =20 -----Mensaje original----- De: ast...@li... [mailto:ast...@li...] En nombre de = Kristian Kielhofner Enviado el: jueves, 08 de marzo de 2007 20:39 Para: AstLinux Users Mailing List Asunto: Re: [Astlinux-users] Lcd4linux package On 3/8/07, Manuel Dominguez <man...@te...> wrote: > Thanks to all, > > I solve the problem using a similar method I have found in Internet. = Can you > take a look to see if the package settings are ok? > I have a problem with init. I don't know if the file I have installed = in > /etc/init.d is enough to start lcd4linux. By the moment not works and = I need > to type manually "mount -t usbfs usbfs /proc/bus/usb" and then start > lscd4linux. Some ideas? > > Thanks, > > -- > Manuel > Manuel, Once your package is added to AstLinux I will assign a start/stop point in the default runlevel. I also just commited a change to trunk that will mount usbfs by default from /etc/rc on startup. --=20 Kristian Kielhofner -------------------------------------------------------------------------= Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share = your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
From: Lenir S. <fla...@ya...> - 2007-03-09 20:50:27
|
I think you missed something on the updated files, this is what get when i try to compile: /usr/bin/install -D -m 0755 package/pcmcia/pcmcia-init /opt/astlinux2/astlinux/trunk/build_i586/root/etc/init.d/pcmcia rm -rf /opt/astlinux2/astlinux/trunk/build_i586/root/etc/pcmcia/cis [ -d /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux ] && \ /sbin/depmod \ -b /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux/ \ -F /opt/astlinux2/astlinux/trunk/build_i586/linux-2.6.20-astlinux/System.map \ > /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux/modules.dep WARNING: Couldn't open directory /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux//lib/modules/2.6.17-gentoo-r7: No such file or directory FATAL: Could not open /opt/astlinux2/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux//lib/modules/2.6.17-gentoo-r7/modules.dep.temp for writing: No such file or directory make: *** [/opt/astlinux2/astlinux/trunk/build_i586/pcmcia-cs-3.2.8/.modules.dep] Error 1 Kristian Kielhofner <kri...@gm...> wrote: On 3/6/07, Lenir Santiago wrote: > Well, i got PCMCIA to work on astlinux, however a few changes needed to be > applied to package/pcmcia/pcmcia.mk, /etc/init.d/pcmcia and /etc/rc, which > i have attached on this email. Also, i used the latest pcmcia-cs package > (3.2.8) So now i have my system booting off a USB flash pen and using a CF > card as the KD. and is working fine...Astlinux should consider putting this > on the next release. > > p.s. Make sure you do a 'cardmgr eject' before starting the pcmcia services > and 'cardmgr insert' after you have started the pcmcia service. > Lenir, Thank you for your fixes. I have included these (with slight mods) in trunk. Thanks again! -- Kristian Kielhofner ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... --------------------------------- It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. |
From: Manuel D. <man...@te...> - 2007-03-09 18:38:17
|
Hi again, I am again with the lcd. I have found a patch for lcdproc to support picoLCD. I have tried to include in package but some errors appears whe try to apply. My experience in linux is very limited. Can somebody take a look to the patch and oriented me where is the problem? Thanks all for your patience, -- Manuel |