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: Manuel D. <man...@te...> - 2007-03-02 17:08:45
|
Thank you Kristian, you find the problem. This problem disappears but appears another one with squashfs. Sorry, I don't like to send so many questions but it's the first time that I use buildroot: toolchain/patch-kernel.sh /home/astlinux/trunk/build_i586/squashfs3.2-r2 target/squashfs/ squashfs\*.patch touch /home/astlinux/trunk/build_i586/squashfs3.2-r2/.unpacked make -j2 -C /home/astlinux/trunk/build_i586/squashfs3.2-r2/squashfs-tools; make[1]: Entering directory `/home/astlinux/trunk/build_i586/squashfs3.2-r2/squashfs-tools' cc -I. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -O2 -c -o mksquashfs.o mksquashfs.c cc -I. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -O2 -c -o read_fs.o read_fs.c mksquashfs.c:38:18: zlib.h: No such file or directory read_fs.c:35:18: zlib.h: No such file or directory read_fs.c: In function `read_block': read_fs.c:88: error: `Z_OK' undeclared (first use in this function) read_fs.c:88: error: (Each undeclared identifier is reported only once read_fs.c:88: error: for each function it appears in.) read_fs.c:89: error: `Z_MEM_ERROR' undeclared (first use in this function) read_fs.c:91: error: `Z_BUF_ERROR' undeclared (first use in this function) mksquashfs.c:562: error: syntax error before '*' token mksquashfs.c: In function `mangle2': mksquashfs.c:566: error: `z_stream' undeclared (first use in this function) mksquashfs.c:566: error: (Each undeclared identifier is reported only once mksquashfs.c:566: error: for each function it appears in.) mksquashfs.c:566: error: `stream' undeclared (first use in this function) mksquashfs.c:566: error: `strm' undeclared (first use in this function) mksquashfs.c:568: error: `uncompressed' undeclared (first use in -----Mensaje original----- De: ast...@li... [mailto:ast...@li...] En nombre de Kristian Kielhofner Enviado el: viernes, 02 de marzo de 2007 17:18 Para: AstLinux Users Mailing List Asunto: Re: [Astlinux-users] Compile errors On 3/2/07, Manuel Dominguez <man...@te...> wrote: > Hi all, > > I have the same packages version that Thorsten. I have compiled 0.4 without > problems but my problem appears in trunk. Always has an error trying to > compile fakeroot. Somebody knows what happens? It's possible to disable > fakeroot? The package is not selected in my astlinux.config. Please, I need > to begin to test with Astlinux trunk. > > Here is the error: > ..snipped.. > checking for g++... no > checking for c++... no > checking for gpp... no > checking for aCC... no > checking for CC... no > checking for cxx... no > checking for cc++... no > checking for cl... no > checking for FCC... no > checking for KCC... no > checking for RCC... no > checking for xlC_r... no > checking for xlC... no > checking whether we are using the GNU C++ compiler... no > checking whether g++ accepts -g... no > checking dependency style of g++... none > checking how to run the C++ preprocessor... /lib/cpp > configure: error: C++ preprocessor "/lib/cpp" fails sanity check > See `config.log' for more details. > make: > Script done on Thu 01 Mar 2007 08:16:48 PM EST Manuel, You need to install a C++ compiler on your host. How to do this varies greatly by distro but usually it is something like g++, c++-devel, etc. -- 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-02 16:17:39
|
On 3/2/07, Manuel Dominguez <man...@te...> wrote: > Hi all, > > I have the same packages version that Thorsten. I have compiled 0.4 without > problems but my problem appears in trunk. Always has an error trying to > compile fakeroot. Somebody knows what happens? It's possible to disable > fakeroot? The package is not selected in my astlinux.config. Please, I need > to begin to test with Astlinux trunk. > > Here is the error: > ..snipped.. > checking for g++... no > checking for c++... no > checking for gpp... no > checking for aCC... no > checking for CC... no > checking for cxx... no > checking for cc++... no > checking for cl... no > checking for FCC... no > checking for KCC... no > checking for RCC... no > checking for xlC_r... no > checking for xlC... no > checking whether we are using the GNU C++ compiler... no > checking whether g++ accepts -g... no > checking dependency style of g++... none > checking how to run the C++ preprocessor... /lib/cpp > configure: error: C++ preprocessor "/lib/cpp" fails sanity check > See `config.log' for more details. > make: > Script done on Thu 01 Mar 2007 08:16:48 PM EST Manuel, You need to install a C++ compiler on your host. How to do this varies greatly by distro but usually it is something like g++, c++-devel, etc. -- Kristian Kielhofner |
From: Manuel D. <man...@te...> - 2007-03-02 16:06:15
|
Hi all, I have the same packages version that Thorsten. I have compiled 0.4 = without problems but my problem appears in trunk. Always has an error trying to compile fakeroot. Somebody knows what happens? It's possible to disable fakeroot? The package is not selected in my astlinux.config. Please, I = need to begin to test with Astlinux trunk. Here is the error: zcat /home/astlinux/trunk/dl/fakeroot_1.2.13.tar.gz | tar -C /home/astlinux/trunk/toolchain_build_i586 -xf - /home/astlinux/trunk/toolchain_build_i586/bin/sed -i -e "s,getopt --version,getopt --version 2>/dev/null," \ =09 /home/astlinux/trunk/toolchain_build_i586/fakeroot-1.2.13/scripts/fakeroo= t.i n touch = /home/astlinux/trunk/toolchain_build_i586/fakeroot-1.2.13/.unpacked (cd /home/astlinux/trunk/toolchain_build_i586/fakeroot-1.2.13; rm -rf config.cache; \ CC=3D"gcc" \ ./configure \ --prefix=3D/usr \ ); checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... = no checking whether make sets $(MAKE)... (cached) yes checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables...=20 checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking dependency style of gcc... gcc3 checking for a sed that does not truncate output... /bin/sed checking for egrep... grep -E checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking whether we are using the GNU C++ compiler... no checking whether g++ accepts -g... no checking dependency style of g++... none checking how to run the C++ preprocessor... /lib/cpp configure: error: C++ preprocessor "/lib/cpp" fails sanity check See `config.log' for more details. make:=20 Script done on Thu 01 Mar 2007 08:16:48 PM EST -----Mensaje original----- De: ast...@li... [mailto:ast...@li...] En nombre de = Manuel Enviado el: mi=E9rcoles, 28 de febrero de 2007 10:22 Para: 'AstLinux Users Mailing List' Asunto: Re: [Astlinux-users] Compile errors Thanks Thorsten, Can you give me the packages version you have installed? It's possible = I'm using old version of these packages.=20 -- Manuel -----Mensaje original----- De: ast...@li... [mailto:ast...@li...] En nombre de tosh_hamburg Enviado el: mi=E9rcoles, 28 de febrero de 2007 9:36 Para: AstLinux Users Mailing List Asunto: Re: [Astlinux-users] Compile errors Hello Manuel, I tried to compile Astlinux on a CentOS box. To make everything work, I = had to install the the following packages: -gcc -bison -flex -autoconf -sharutils I hope that is helpful for you as well. The result is worth the effort. Thorsten -----Ursprungliche Nachricht----- Von: ast...@li... [mailto:ast...@li...]Im Auftrag von Manuel Dominguez Gesendet: Dienstag, 27. Februar 2007 21:26 An: 'AstLinux Users Mailing List' Betreff: Re: [Astlinux-users] Compile errors Thanks Darrick, I have updated svn trunk and another error appears: checking dependency style of g++... none checking how to run the C++ preprocessor... /lib/cpp configure: error: C++ preprocessor "/lib/cpp" fails sanity check See `config.log' for more details. make: *** [/home/astlinux/trunk/toolchain_build_i586/fakeroot-1.2.13/.configured] Error 1 Attached is the config.log Regards, -- Manuel -----Mensaje original----- De: ast...@li... [mailto:ast...@li...] En nombre de = Darrick Hartman Enviado el: lunes, 26 de febrero de 2007 21:07 Para: AstLinux Users Mailing List Asunto: Re: [Astlinux-users] Compile errors Manuel wrote: > Hi all, > > I am trying to compile AstLinux trunk using vmware image. The first > time receive error from misdn. I remove the package and try again but > all the time appears the same error: > > cp -a /home/astlinux/trunk/build_i586/staging_dir/sbin/ztcfg > /home/astlinux/trunk/build_i586/root/sbin/ztcfg > cp -a /home/astlinux/trunk/build_i586/staging_dir/sbin/zttool > /home/astlinux/trunk/build_i586/root/sbin/zttool > cp: cannot stat > `/home/astlinux/trunk/build_i586/staging_dir/sbin/zttool': No such > file or directory > make: *** [/home/astlinux/trunk/build_i586/root/sbin/ztcfg] Error 1 > > It's possible to compile trunk in this moment? Some idea to avoid this error? > This should be fixed now in trunk (and in the 0.4 branch). Please do an svn update with your trunk directory and grab the latest revision. 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=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.... -------------------------------------------------------------------------= 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.... -------------------------------------------------------------------------= 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.... -------------------------------------------------------------------------= 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: nedi <ne...@gm...> - 2007-03-02 06:46:45
|
Hi since firmware upgrade I have problems I have 2 SC-375 both of them are on the same astlinux server the one with the old firmware is on internal 16 connected and working dtmf the new one is on internal 17 connected don't work all settings in asterisk are the same . asterisk [general] useragent=pbx port=5060 context=default disallow=all allow=alaw allow=ulaw language=de maxexpiry=40 defaultexpiry=20 qualify=yes nat=yes [16] type=friend username=16 secret=16 callerid="16" <16> host=dynamic mailbox=16@default dtmfmode=rfc2833 canreinvite=no context=16 [17] type=friend username=17 secret=17 callerid="0715605260" <17> host=dynamic mailbox=17@default dtmfmode=rfc2833 canreinvite=no context=17 I typed in the console allversal*CLI>show codec and get allversal*CLI> show codec 17 1 (1 << 0) G.723.1 16 (1 << 4) G.726 allversal*CLI> show codec 15 1 (1 << 0) G.723.1 2 (1 << 1) GSM 4 (1 << 2) G.711 u-law 8 (1 << 3) G.711 A-law allversal*CLI> show codec 10 2 (1 << 1) GSM 8 (1 << 3) G.711 A-law what dose mean? Ext. internal 17 don'use Codec G.711 That can be problem with DTMF?? Regards nedi |
From: Darrick H. <dha...@dj...> - 2007-03-02 03:30:25
|
Lonnie Abelbeck wrote: > Greetings, > > I have created a "at-a-glance" status page for AstLinux... such that > I can quickly observe the health and activity of my many AstLinux boxes. > > The status page looks like this: (example does not have asterisk > running) > http://lonnie.abelbeck.com/share/status.php.jpg > > Additionally, if asterisk is running, the following sections are added: > > o SIP Active Channels: > o SIP Registrations: > o SIP Peer Status: > > Of course, you can easily edit and add commands of your own, like IAX > status if you use that. > Lonnie, Very nice! We might be able to utilize some of these additions in the standard interface. Thanks for the contributions. The web interface is one are that needs improvement. By all means, continue with the suggestions. Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com |
From: Darrick H. <dha...@dj...> - 2007-03-02 03:25:48
|
Use the older wrap image on that site. There are minor changes to anything applicable to the wrap image (you're not going to run a zaptel or wanpipe card on a wrap board). I'll make sure to compile a wrap image when I do the next set of upgrades. In general, the .config is the same as the asterisk.config with the change of the target device. Darrick ast...@el... wrote: >> I updated most of the test images last night/this morning with a few >> recent changes from svn. >> >> svn revision 678 includes the following changes: >> >> improved openntpd init >> full zaptel binaries >> preliminary wanpipe drivers (untested) >> >> I did not get an image built for the wrap boards yet, but images for >> VIA, generic i586 and the Soekris platform are available. >> >> http://www.djhsolutions.com/astlinux/ >> >> Once again, report back with any feedback on these images (even if it's >> just "it works fine"). >> >> Thanks, >> >> Darrick >> >> -- >> Darrick Hartman >> DJH Solutions, LLC >> http://www.djhsolutions.com >> > > > Is it possible for you to put up the .config file you use to generate > those images as well? I seem to be having a hell of a time compiling for > the WRAP, mostly because I don't know enough to know what should and > should not be checked off. I need to perform an idiot check, that idiot > being me. > > ------------------------------------------------------------------------- > 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.... > -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com |
From: Lonnie A. <li...@lo...> - 2007-03-02 02:38:39
|
Greetings, I have created a "at-a-glance" status page for AstLinux... such that I can quickly observe the health and activity of my many AstLinux boxes. The status page looks like this: (example does not have asterisk running) http://lonnie.abelbeck.com/share/status.php.jpg Additionally, if asterisk is running, the following sections are added: o SIP Active Channels: o SIP Registrations: o SIP Peer Status: Of course, you can easily edit and add commands of your own, like IAX status if you use that. The PHP/HTML code can be found here: http://lonnie.abelbeck.com/share/status.php.txt Rename status.php.txt to status.php Place status.php anywhere you have mini_httpd running as 'root' (be careful of security issues). Or, to try it out with the default https settings, you could place the file at: (after: "mount -o rw,remount /") /stat/var/www/admin/status.php Fix permissions: chmod 755 status.php Make '/' "ro" by: mount -o ro,remount / Access the page by: https://your_box/admin/status.php All comments welcome. Enjoy, Lonnie |
From: Kristian K. <kri...@gm...> - 2007-03-02 00:43:38
|
Whenever possible care has been taken to make building wih different package selections. It should dependencies for you. with that being said we usually only test full builds with the default config files... to answer you question- on a wrap you might not need zaptel/ztduumy at all. Certainly not libpri! On 3/1/07, ast...@el... <ast...@el...> wrote: > > On 3/1/07, ast...@el... <ast...@el...> wrote: > >> Is it possible for you to put up the .config file you use to generate > >> those images as well? I seem to be having a hell of a time compiling for > >> the WRAP, mostly because I don't know enough to know what should and > >> should not be checked off. I need to perform an idiot check, that idiot > >> being me. > >> > > > > asterisk, > > > > Most of the time this is all you need to do: > > > > cp astlinux.config .config > > make oldconfig > > make menuconfig (select WRAP) > > make > > > > Keep in mind that Darrick's images are from the 0.4 branch, not > > trunk. From what I have seen lately you have been trying to build > > trunk. trunk and 0.4 are quite different these days. > > > > -- > > Kristian Kielhofner > > > I have been trying to compile 0.4 and trunk separately, to try to > understand better. I just don't have a good impression of what I can > remove or add safely. As a simple example, the WRAP is using only ztdummy, > so how much zaptel and hardware related parts can be pared away? I figure > ZAP/PRI could be removed, but how much ISDN/mISDN stuff can I remove > before I cripple something or make a compile fail? > > ------------------------------------------------------------------------- > 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.... > -- Kristian Kielhofner |
From: <ast...@el...> - 2007-03-02 00:17:58
|
> On 3/1/07, ast...@el... <ast...@el...> wrote: >> Is it possible for you to put up the .config file you use to generate >> those images as well? I seem to be having a hell of a time compiling for >> the WRAP, mostly because I don't know enough to know what should and >> should not be checked off. I need to perform an idiot check, that idiot >> being me. >> > > asterisk, > > Most of the time this is all you need to do: > > cp astlinux.config .config > make oldconfig > make menuconfig (select WRAP) > make > > Keep in mind that Darrick's images are from the 0.4 branch, not > trunk. From what I have seen lately you have been trying to build > trunk. trunk and 0.4 are quite different these days. > > -- > Kristian Kielhofner I have been trying to compile 0.4 and trunk separately, to try to understand better. I just don't have a good impression of what I can remove or add safely. As a simple example, the WRAP is using only ztdummy, so how much zaptel and hardware related parts can be pared away? I figure ZAP/PRI could be removed, but how much ISDN/mISDN stuff can I remove before I cripple something or make a compile fail? |
From: Kristian K. <kri...@gm...> - 2007-03-02 00:07:34
|
On 3/1/07, ast...@el... <ast...@el...> wrote: > > Using rev 684, I managed to finish a compile. I was wondering though, > unionFS seems like a good idea to have though, having a clean mixed RO/RW > setup. I don't have a clear understanding of the current filesystem > structure for AstLinux though. Does this mean we should favor a lvm setup > then? > asterisk, rev 684 still has unionfs. It is applied as a patch to the kernel and built into bzImage. Over the next week or so I will finish integrating unionfs into AstLinux. I'll be announcing the new features shortly. -- Kristian Kielhofner |
From: <ast...@el...> - 2007-03-02 00:03:51
|
> On 3/1/07, ast...@el... <ast...@el...> wrote: >> > On 2/28/07, ast...@el... <ast...@el...> >> wrote: >> >> When doing make for the current trunk (673), it stopped while >> compiling >> >> astmanproxy. Seems it's expecting OpenSSL stuff, but since that seems >> to >> >> have not been downloaded/compiled/installed yet (A comes before O), >> it >> >> fails spectacularly. Is this normal, since trunk could be broken by >> >> something, or is my environment lacking something? I'm running CentOS >> >> 4.3 >> >> with all the dev stuff installed and updated. Do I have to do >> something >> >> silly like disable that package and compile, then go back and compile >> >> astmanproxy? >> >> >> > >> > asterisk, >> > >> > I just commited a fix for this in rev 675. Could you please try it >> > again? >> > >> > -- >> > Kristian Kielhofner >> >> I tried compiling with rev 678, that seemed fix that problem. Thank you. >> >> Though it next got hung up on unionFS. I noticed on the unionFS site >> that >> they are showing version 2.6 for 2.6.20 kernels, rather than the version >> 1.5 you use, though I doubt that makes much of a difference. >> >> > > asterisk, > > You are brave for following trunk these days - it has been pretty rough! > > Sorry for all of the changes lately but I think that they are > important for the progress of AstLinux. Some really cool things have > gone in the last few weeks. > > When I upgraded the kernel to 2.6.20 I was unsure of how I wanted to > handle the unionfs package. I thought that unionctl may come in handy > someday... Truth is it will probably just cause confusion (as it has > so far). As of rev 684 I have removed it from trunk. > > -- > Kristian Kielhofner > Using rev 684, I managed to finish a compile. I was wondering though, unionFS seems like a good idea to have though, having a clean mixed RO/RW setup. I don't have a clear understanding of the current filesystem structure for AstLinux though. Does this mean we should favor a lvm setup then? |
From: Kristian K. <kri...@gm...> - 2007-03-01 23:53:36
|
On 3/1/07, ast...@el... <ast...@el...> wrote: > Is it possible for you to put up the .config file you use to generate > those images as well? I seem to be having a hell of a time compiling for > the WRAP, mostly because I don't know enough to know what should and > should not be checked off. I need to perform an idiot check, that idiot > being me. > asterisk, Most of the time this is all you need to do: cp astlinux.config .config make oldconfig make menuconfig (select WRAP) make Keep in mind that Darrick's images are from the 0.4 branch, not trunk. From what I have seen lately you have been trying to build trunk. trunk and 0.4 are quite different these days. -- Kristian Kielhofner |
From: <ast...@el...> - 2007-03-01 23:48:32
|
> I updated most of the test images last night/this morning with a few > recent changes from svn. > > svn revision 678 includes the following changes: > > improved openntpd init > full zaptel binaries > preliminary wanpipe drivers (untested) > > I did not get an image built for the wrap boards yet, but images for > VIA, generic i586 and the Soekris platform are available. > > http://www.djhsolutions.com/astlinux/ > > Once again, report back with any feedback on these images (even if it's > just "it works fine"). > > Thanks, > > Darrick > > -- > Darrick Hartman > DJH Solutions, LLC > http://www.djhsolutions.com Is it possible for you to put up the .config file you use to generate those images as well? I seem to be having a hell of a time compiling for the WRAP, mostly because I don't know enough to know what should and should not be checked off. I need to perform an idiot check, that idiot being me. |
From: Kristian K. <kri...@gm...> - 2007-03-01 23:46:53
|
On 3/1/07, ast...@el... <ast...@el...> wrote: > > On 2/28/07, ast...@el... <ast...@el...> wrote: > >> When doing make for the current trunk (673), it stopped while compiling > >> astmanproxy. Seems it's expecting OpenSSL stuff, but since that seems to > >> have not been downloaded/compiled/installed yet (A comes before O), it > >> fails spectacularly. Is this normal, since trunk could be broken by > >> something, or is my environment lacking something? I'm running CentOS > >> 4.3 > >> with all the dev stuff installed and updated. Do I have to do something > >> silly like disable that package and compile, then go back and compile > >> astmanproxy? > >> > > > > asterisk, > > > > I just commited a fix for this in rev 675. Could you please try it > > again? > > > > -- > > Kristian Kielhofner > > I tried compiling with rev 678, that seemed fix that problem. Thank you. > > Though it next got hung up on unionFS. I noticed on the unionFS site that > they are showing version 2.6 for 2.6.20 kernels, rather than the version > 1.5 you use, though I doubt that makes much of a difference. > > asterisk, You are brave for following trunk these days - it has been pretty rough! Sorry for all of the changes lately but I think that they are important for the progress of AstLinux. Some really cool things have gone in the last few weeks. When I upgraded the kernel to 2.6.20 I was unsure of how I wanted to handle the unionfs package. I thought that unionctl may come in handy someday... Truth is it will probably just cause confusion (as it has so far). As of rev 684 I have removed it from trunk. -- Kristian Kielhofner |
From: <ast...@el...> - 2007-03-01 23:41:47
|
> On 2/28/07, ast...@el... <ast...@el...> wrote: >> When doing make for the current trunk (673), it stopped while compiling >> astmanproxy. Seems it's expecting OpenSSL stuff, but since that seems to >> have not been downloaded/compiled/installed yet (A comes before O), it >> fails spectacularly. Is this normal, since trunk could be broken by >> something, or is my environment lacking something? I'm running CentOS >> 4.3 >> with all the dev stuff installed and updated. Do I have to do something >> silly like disable that package and compile, then go back and compile >> astmanproxy? >> > > asterisk, > > I just commited a fix for this in rev 675. Could you please try it > again? > > -- > Kristian Kielhofner I tried compiling with rev 678, that seemed fix that problem. Thank you. Though it next got hung up on unionFS. I noticed on the unionFS site that they are showing version 2.6 for 2.6.20 kernels, rather than the version 1.5 you use, though I doubt that makes much of a difference. ----- Applying unionfs-nounionimap.patch using plaintext: patching file utils/Makefile touch /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/.source touch /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/.configured make -j2 -C /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713 CC=/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/staging_dir/bin/i586-linux-uclibc-gcc KVERS=2.6 MODDIR=/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/root/lib/modules/2.6.20-astlinux \ LINUXSRC=/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/linux PWD=/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713 EXTRACFLAGS=-DUNIONFS_UNSUPPORTED make[1]: Entering directory `/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713' ****************************************************************************** If you have questions about or problems building Unionfs, please read INSTALL. make -C /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/linux SUBDIRS=/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713 FISTDEVMK=/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/fistdev.mk modules ****************************************************************************** make -C utils all CC=/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/staging_dir/bin/i586-linux-uclibc-gcc UCFLAGS='-I.. -I. -g -O2 -Wall -Werror -DUNIONFS_VERSION=\"1.5pre-cvs200701241713\" -DSUP_MAJOR=2 -DSUP_MINOR=6 -DSUP_PATCH=19' make[2]: Entering directory `/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/utils' make[2]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/staging_dir/bin/i586-linux-uclibc-gcc -o unionctl unionctl.c usercommon.c -I.. -I. -g -O2 -Wall -Werror -DUNIONFS_VERSION=\"1.5pre-cvs200701241713\" -DSUP_MAJOR=2 -DSUP_MINOR=6 -DSUP_PATCH=19 /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/staging_dir/bin/i586-linux-uclibc-gcc -o uniondbg uniondbg.c -I.. -I. -g -O2 -Wall -Werror -DUNIONFS_VERSION=\"1.5pre-cvs200701241713\" -DSUP_MAJOR=2 -DSUP_MINOR=6 -DSUP_PATCH=19 make[2]: Leaving directory `/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/utils' make[2]: Entering directory `/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/linux-2.6.20-astlinux' make[2]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. CC [M] /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/subr.o CC [M] /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/dentry.o CC [M] /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/file.o CC [M] /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/inode.o CC [M] /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/main.o CC [M] /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/super.o CC [M] /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/stale_inode.o CC [M] /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/branchman.o CC [M] /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/xattr.o CC [M] /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/rdstate.o CC [M] /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/copyup.o CC [M] /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/dirhelper.o CC [M] /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/rename.o CC [M] /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/unlink.o CC [M] /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/lookup.o /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/lookup.c: In function `new_dentry_private_data': /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/lookup.c:421: error: `SLAB_ATOMIC' undeclared (first use in this function) /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/lookup.c:421: error: (Each undeclared identifier is reported only once /home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/lookup.c:421: error: for each function it appears in.) make[3]: *** [/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/lookup.o] Error 1 make[2]: *** [_module_/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713] Error 2 make[2]: Leaving directory `/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/linux-2.6.20-astlinux' make[1]: *** [unionfs.ko] Error 2 make[1]: Leaving directory `/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713' make: *** [/home/ouroboros/astlinuxbuildenv/astlinux/trunk/build_i586/unionfs-1.5pre-cvs200701241713/unionfs.ko] Error 2 |
From: Darrick H. <dha...@dj...> - 2007-03-01 23:17:43
|
Kevin Kiely wrote: > Thanks guys. I haven't looked at the new releases, is Arno's in the release > version now? > > Yes. Arno's firewall has been in the last few releases (0.4.4 for sure, but I think 0.4.3 has it as well). The test releases I have that will shortly become 0.4.5 also include Arno's firewall script. To use it, you'll need to change the fwvers variable to "arno" and copy /stat/etc/arno-iptables-firewall.conf to /mnt/kd and edit appropriately. After copying the file there, you'll need to edit the file, then reboot for the firewall change to take effect. Rebooting will create a symbolic link to /mnt/kd/arno-iptables-firewall.conf from /etc/arno-iptables-firewall.conf. If you need to make future changes, edit that file, then issue the following command to restart the firewall: arno-iptables-firewall restart If you have any questions, feel free to ask. Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com |
From: Kevin K. <Ast...@gt...> - 2007-03-01 23:03:16
|
Thanks guys. I haven't looked at the new releases, is Arno's in the release version now? -----Original Message----- From: Darrick Hartman [mailto:dha...@dj...] Sent: Thursday, March 01, 2007 5:33 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] Firewall with Traffic Shaper Kristian Kielhofner wrote: > On 3/1/07, Kevin Kiely <Ast...@gt...> wrote: > >> Is it possible to use Arno's Firewall with the traffic application in >> ASTLinux? I would like to use the traffic shaping and offer NAT >> mapping/forwarding. >> > From what I know or Arno's Firewall this should be possible. > AstShape operates independently of iptables so you should be fine. > > Darrick you know a bit more about Arno's, what do you think? > Yup. Works like a charm. Just define EXTUP and EXTDOWN in rc.conf and you should be good to go. 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.... -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.446 / Virus Database: 268.18.5/706 - Release Date: 2/28/2007 4:09 PM |
From: Darrick H. <dha...@dj...> - 2007-03-01 22:33:14
|
Kristian Kielhofner wrote: > On 3/1/07, Kevin Kiely <Ast...@gt...> wrote: > >> Is it possible to use Arno's Firewall with the traffic application in >> ASTLinux? I would like to use the traffic shaping and offer NAT >> mapping/forwarding. >> > From what I know or Arno's Firewall this should be possible. > AstShape operates independently of iptables so you should be fine. > > Darrick you know a bit more about Arno's, what do you think? > Yup. Works like a charm. Just define EXTUP and EXTDOWN in rc.conf and you should be good to go. Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com |
From: Kristian K. <kri...@gm...> - 2007-03-01 22:26:04
|
On 3/1/07, Kevin Kiely <Ast...@gt...> wrote: > Is it possible to use Arno's Firewall with the traffic application in > ASTLinux? I would like to use the traffic shaping and offer NAT > mapping/forwarding. > > Thanks, > > Kevin > Kevin, From what I know or Arno's Firewall this should be possible. AstShape operates independently of iptables so you should be fine. Darrick you know a bit more about Arno's, what do you think? -- Kristian Kielhofner |
From: Kevin K. <Ast...@gt...> - 2007-03-01 22:21:26
|
Is it possible to use Arno's Firewall with the traffic application in ASTLinux? I would like to use the traffic shaping and offer NAT mapping/forwarding. Thanks, Kevin |
From: Kristian K. <kri...@gm...> - 2007-03-01 21:41:57
|
On 3/1/07, nedi <ne...@gm...> wrote: > Hi all > I get for my gsm gateway new firmware and the new firmware have choice > DTMFMODE=rfc2833, info or inband. > can I use in Astlinux 0.3.0 DTMFMODE=rfc2833, info or inband i use only the > codec ulaw and alaw (G711). > > Before firmware upgrade I used DTMFMODE=rfc2543, now I can't use it. > > Thanks. > Nedi, If you are using alaw or ulaw you can use any dtmfmode that is supported by both (or all) of your endpoints. If you are using a compressed codec you can only use info or rfc2833. rfc2833 seems to be more popular these days because it follows the RTP path with the audio, not the signalling as with INFO. I myself prefer rfc2833. RFC 2543 is the old specification for SIP. The new one is RFC 3261. Either way they are not a DTMF mode and are not valid as a dtmfmode configure option in Asterisk. -- Kristian Kielhofner |
From: Kristian K. <kri...@gm...> - 2007-03-01 21:35:46
|
On 2/28/07, Lenir Santiago <fla...@ya...> wrote: > Does Astlinux have PCMCIA support? I want to run it on a VIA EPIA MII 1200 > based PC and i want to boot off a USB flash pen, and us the CF card slot or > PCMCIA slot to us a CF card to store all the configs, etc...The current > release 0.4.4 doesnt load PCMCIA. Is this possible? > > Thanks > Lenir, It depends... Depending on the configuration, some PCMCIA devices show up on the PCI bus with no special configuration - all you should have to do is load the compatible module. In this case CF cards usually just show up as hda, hdb, etc when loaded in a PCMCIA slot. -- Kristian Kielhofner |
From: nedi <ne...@gm...> - 2007-03-01 17:28:14
|
Hi all I get for my gsm gateway new firmware and the new firmware have choice DTMFMODE=rfc2833, info or inband. can I use in Astlinux 0.3.0 DTMFMODE=rfc2833, info or inband i use only the codec ulaw and alaw (G711). Before firmware upgrade I used DTMFMODE=rfc2543, now I can't use it. Thanks. |
From: Lenir S. <fla...@ya...> - 2007-03-01 15:11:10
|
Guys, i get the following error when i run makeimage.sh after i do the grub part, also im having to use /dev/loop/0 instead of /dev/loop: localhost trunk # ./makeimage.sh 973 This script will create a bootable AstLinux image from the development environment in this directory. Every care has been taken to prevent damage to your host operating system, house, etc. HOWEVER, IT IS ALWAYS POSSIBLE FOR SOMETHING TO GO WRONG. I CAN NOT GUARANTEE THAT THIS SCRIPT WILL NOT DESTROY YOUR MACHINE OR ANY DATA ON IT Press enter to continue, or CTRL+C to exit Would you like me to aggresively strip everything in your image? This can save as much as 10mb. Please answer yes or no Strip: no Stripping declined You will need to write down the number of cylinders, heads, and sectors for fdisk. Bad things happen if you mess this up! ======================================================================== bximage Disk Image Creation Tool for Bochs $Id: bximage.c,v 1.31 2005/11/20 20:26:35 vruppert Exp $ ======================================================================== I will create a 'flat' hard disk image with cyl=1976 heads=16 sectors per track=63 total sectors=1991808 total size=972.56 megabytes Writing: [] Done. I wrote 1019805696 bytes to disk.img. The following line should appear in your bochsrc: ata0-master: type=disk, path="disk.img", mode=flat, cylinders=1976, heads=16, spt=63 You need to run fdisk manually to partition the image. Please write down or memorize the following instructions: press 'x' - extra functionality press 'h' fill in heads - probably 16 press 's' fill in sectors - probably 63 press 'c' fill in cylinders - this changes press 'r' return to main menu press 'n' to add new partition press 'p' to choose primary partition press '1' to set partition number press Enter keys to choose default value of First Cylinder parameter. press Enter keys to choose default value of Last Cylinder parameter. press 'w' to write partition table and exit Press enter when you are ready Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel Building a new DOS disklabel. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won't be recoverable. Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite) Command (m for help): x Expert command (m for help): h Number of heads (1-256, default 255): 16 Expert command (m for help): s Number of sectors (1-63, default 63): Using default value 63 Warning: setting sector offset for DOS compatiblity Expert command (m for help): c Number of cylinders (1-1048576, default 123): 1976 The number of cylinders for this disk is set to 1976. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Expert command (m for help): r Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-1976, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-1976, default 1976): Using default value 1976 Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. WARNING: Re-reading the partition table failed with error 22: Invalid argument. The kernel still uses the old table. The new table will be used at the next reboot. Syncing disks. ln: `/dev/loop/0' and `/dev/loop/0' are the same file GRUB Help: grub> device (hd0) /dev/loop grub> root (hd0,0) grub> setup (hd0) grub> quit Press enter when you have this memorized Do it... GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub> device (hd0) /dev/loop/0 grub> root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub> setup (hd0) Checking if "/boot/grub/stage1" exists... yes Checking if "/boot/grub/stage2" exists... yes Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 18 sectors are embedded. succeeded Running "install /boot/grub/stage1 (hd0) (hd0)1+18 p (hd0,0)/boot/grub/stage2 /boot/grub/menu.lst"... failed Error 22: No such partition grub> quit Probing devices to guess BIOS drives. This may take a long time. Done. localhost trunk # Here's the contents of my /dev : localhost trunk # ls /dev/loop* /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6 /dev/loop7 /dev/loop: 0 1 2 3 4 5 6 7 localhost trunk # --------------------------------- Looking for earth-friendly autos? Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center. |
From: Darrick H. <dha...@dj...> - 2007-03-01 15:06:39
|
I updated most of the test images last night/this morning with a few recent changes from svn. svn revision 678 includes the following changes: improved openntpd init full zaptel binaries preliminary wanpipe drivers (untested) I did not get an image built for the wrap boards yet, but images for VIA, generic i586 and the Soekris platform are available. http://www.djhsolutions.com/astlinux/ Once again, report back with any feedback on these images (even if it's just "it works fine"). Thanks, Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com |