Menu
▾
▴
astlinux-devel — The AstLinux development environment, compilation, etc
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
(41) |
Apr
(35) |
May
(18) |
Jun
(5) |
Jul
(4) |
Aug
(37) |
Sep
(9) |
Oct
(20) |
Nov
(50) |
Dec
(217) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(212) |
Feb
(76) |
Mar
(113) |
Apr
(88) |
May
(130) |
Jun
(54) |
Jul
(208) |
Aug
(223) |
Sep
(112) |
Oct
(63) |
Nov
(131) |
Dec
(103) |
| 2010 |
Jan
(247) |
Feb
(130) |
Mar
(43) |
Apr
(92) |
May
(40) |
Jun
(43) |
Jul
(43) |
Aug
(80) |
Sep
(44) |
Oct
(74) |
Nov
(21) |
Dec
(46) |
| 2011 |
Jan
(36) |
Feb
(11) |
Mar
(21) |
Apr
(33) |
May
(4) |
Jun
(12) |
Jul
(5) |
Aug
(20) |
Sep
|
Oct
(64) |
Nov
(26) |
Dec
(71) |
| 2012 |
Jan
(13) |
Feb
(24) |
Mar
(11) |
Apr
(2) |
May
(10) |
Jun
(5) |
Jul
(13) |
Aug
(7) |
Sep
(26) |
Oct
(22) |
Nov
(17) |
Dec
(16) |
| 2013 |
Jan
(6) |
Feb
(6) |
Mar
(6) |
Apr
(8) |
May
(20) |
Jun
|
Jul
(1) |
Aug
(4) |
Sep
(18) |
Oct
(3) |
Nov
(14) |
Dec
(33) |
| 2014 |
Jan
(26) |
Feb
(6) |
Mar
(69) |
Apr
(10) |
May
|
Jun
(8) |
Jul
(18) |
Aug
(22) |
Sep
(19) |
Oct
(17) |
Nov
|
Dec
(4) |
| 2015 |
Jan
(14) |
Feb
(18) |
Mar
|
Apr
|
May
(26) |
Jun
(8) |
Jul
(9) |
Aug
(10) |
Sep
(15) |
Oct
(2) |
Nov
(30) |
Dec
(33) |
| 2016 |
Jan
(1) |
Feb
(24) |
Mar
(19) |
Apr
(1) |
May
|
Jun
(3) |
Jul
(1) |
Aug
(1) |
Sep
(20) |
Oct
(5) |
Nov
(14) |
Dec
(4) |
| 2017 |
Jan
(15) |
Feb
(35) |
Mar
(10) |
Apr
(9) |
May
(14) |
Jun
(33) |
Jul
(1) |
Aug
(27) |
Sep
(7) |
Oct
|
Nov
(10) |
Dec
(15) |
| 2018 |
Jan
(29) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(11) |
Jun
|
Jul
(1) |
Aug
(8) |
Sep
(11) |
Oct
(22) |
Nov
(9) |
Dec
(13) |
| 2019 |
Jan
(1) |
Feb
(7) |
Mar
(3) |
Apr
(21) |
May
(34) |
Jun
(36) |
Jul
(18) |
Aug
(17) |
Sep
(19) |
Oct
(8) |
Nov
(3) |
Dec
|
| 2020 |
Jan
|
Feb
(4) |
Mar
(8) |
Apr
(29) |
May
(50) |
Jun
(8) |
Jul
(2) |
Aug
(10) |
Sep
(1) |
Oct
(7) |
Nov
(9) |
Dec
(19) |
| 2021 |
Jan
(2) |
Feb
(9) |
Mar
(6) |
Apr
(21) |
May
(13) |
Jun
(11) |
Jul
(2) |
Aug
(1) |
Sep
(3) |
Oct
(26) |
Nov
(2) |
Dec
(16) |
| 2022 |
Jan
(8) |
Feb
(7) |
Mar
(1) |
Apr
(13) |
May
(1) |
Jun
(4) |
Jul
(4) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
| 2023 |
Jan
(2) |
Feb
(3) |
Mar
(16) |
Apr
|
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(13) |
Sep
(8) |
Oct
(6) |
Nov
(4) |
Dec
|
| 2024 |
Jan
(3) |
Feb
(3) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(5) |
Aug
|
Sep
(1) |
Oct
|
Nov
(5) |
Dec
|
| 2025 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
(11) |
May
(1) |
Jun
(9) |
Jul
(18) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
1
|
2
|
3
(7) |
4
|
5
(3) |
6
|
|
7
|
8
(6) |
9
(11) |
10
(7) |
11
(20) |
12
(24) |
13
(3) |
|
14
(6) |
15
(14) |
16
(1) |
17
(2) |
18
(25) |
19
(11) |
20
(9) |
|
21
(10) |
22
(2) |
23
(7) |
24
|
25
(17) |
26
(1) |
27
(5) |
|
28
(3) |
29
(16) |
30
(6) |
31
(1) |
|
|
|
|
From: Michael K. <mk...@we...> - 2008-12-28 00:43:54
|
Hi Philip,
>Or you can try "export LANG=C" before compiling to force the native
>error messages...
that's what I did:
rm -rf build_i586/
export LANG=C
time nice -n20 make
and here are the errors:
------------------------------------------
cp
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile.v2.6
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile
export
MINCLUDES=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include
; export MISDNVERSION=1_1_8; make -C
/home/mk/source-control/astlinux-trunk/build_i586/linux
SUBDIRS=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN
modules CONFIG_MISDN_DRV=m CONFIG_MISDN_DSP=m
CONFIG_MISDN_HFCMULTI=m CONFIG_MISDN_HFCPCI=m CONFIG_MISDN_HFCUSB=m
CONFIG_MISDN_XHFC=m CONFIG_MISDN_HFCMINI=m CONFIG_MISDN_W6692=m
CONFIG_MISDN_SPEEDFAX=m CONFIG_MISDN_AVM_FRITZ=m
CONFIG_MISDN_NETJET=m CONFIG_MISDN_DEBUGTOOL=m
make[2]: Entering directory
`/home/mk/source-control/astlinux-trunk/build_i586/linux-2.6.26.8-astlinux'
CC [M]
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.o
In file included from
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/core.h:10,
from
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:21:
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include/linux/mISDNif.h:791:
error: field 'class_dev' has incomplete type
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include/linux/mISDNif.h:824:
error: field 'class_dev' has incomplete type
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include/linux/mISDNif.h:862:
error: field 'class_dev' has incomplete type
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:
In function 'init_card':
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:889:
warning: passing argument 2 of 'request_irq' from incompatible
pointer type
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:895:
warning: passing argument 2 of 'request_irq' from incompatible
pointer type
make[3]: ***
[/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.o]
Error 1
make[2]: ***
[_module_/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN]
Error 2
make[2]: Leaving directory
`/home/mk/source-control/astlinux-trunk/build_i586/linux-2.6.26.8-astlinux'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN'
make: ***
[/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/.built1]
Error 2
-----------------------------------------------
Michael
--
Email: mailto:mk...@we...
|
|
From: Michael K. <mk...@we...> - 2008-12-27 23:38:28
|
I attach the diff (now as .gz) of the changes in linux.mk
>OK I found something in "target/device/geni586/linux.mk" line 108 and 134
>Now the link is created, but now I got this errors ("Fehler"):
>
>------------------------------------------
>make[1]: Entering directory
>`/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN'
>echo 1_1_8 > VERSION ; \
>
>cp
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile.v2.6
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile
>export
>MINCLUDES=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include
>; export MISDNVERSION=1_1_8; make -C
>/home/mk/source-control/astlinux-trunk/build_i586/linux
>SUBDIRS=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN
>modules CONFIG_MISDN_DRV=m CONFIG_MISDN_DSP=m
>CONFIG_MISDN_HFCMULTI=m CONFIG_MISDN_HFCPCI=m CONFIG_MISDN_HFCUSB=m
>CONFIG_MISDN_XHFC=m CONFIG_MISDN_HFCMINI=m CONFIG_MISDN_W6692=m
>CONFIG_MISDN_SPEEDFAX=m CONFIG_MISDN_AVM_FRITZ=m
>CONFIG_MISDN_NETJET=m CONFIG_MISDN_DEBUGTOOL=m
>make[2]: Entering directory
>`/home/mk/source-control/astlinux-trunk/build_i586/linux-2.6.26.8-astlinux'
> CC [M]
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.o
>In file included from
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/core.h:10,
> from
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:21:
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include/linux/mISDNif.h:791:
>error: field 'class_dev' has incomplete type
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include/linux/mISDNif.h:824:
>error: field 'class_dev' has incomplete type
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include/linux/mISDNif.h:862:
>error: field 'class_dev' has incomplete type
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:
>In function 'init_card':
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:889:
>warning: passing argument 2 of 'request_irq' from incompatible
>pointer type
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:895:
>warning: passing argument 2 of 'request_irq' from incompatible
>pointer type
>make[3]: ***
>[/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.o]
>Fehler 1
>make[2]: ***
>[_module_/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN]
>Fehler 2
>make[2]: Leaving directory
>`/home/mk/source-control/astlinux-trunk/build_i586/linux-2.6.26.8-astlinux'
>make[1]: *** [all] Fehler 2
>make[1]: Leaving directory
>`/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN'
>make: ***
>[/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/.built1]
>Fehler 2
>----------------------------------------
Michael
--
Email: mailto:mk...@we...
------------------------------------------------------------------------------
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
Donations to support AstLinux are graciously accepted via PayPal to
pa...@kr....
--
Email: mailto:mk...@bi... |
|
From: Philip P. <phi...@re...> - 2008-12-27 20:25:54
|
Michael Keuter wrote: >> > /* the folder should be not "linux" but "linux-2.6.26.8-astlinux" */ >> >> Actually, there should be a symbolic link pointing "linux" to the >> specific kernel version. If this was removed, it should be replaced--If >> it was removed, it was only removed in trunk and probably unintentionally >> > > Yes it is only missing in trunk. The 0.6-branch builds correctly. > > >> > BTW where do I set the variable of the Astlinux-version (e.g. >> >>> "trunk-2237") in the build environment? >>> >> that's parsed and set from the current svn version (if you're building >> > >from trunk or a non-tagged branch). > >> Darrick >> > > But all the trunk-images I build are named "astlinux-trunk-" without a number. > That might be a regression introduced in 2196 and fixed in 2239. Looking... > > BTW: What is the best way to preserve the "/root" folder. > Or in which script is the link to /tmp/root created? > I know about "/mnt/kd/rc.local" and "/mnt/kd/ssh_keys" :-), but I > like to have e.g. some files back (.ssh/known_hosts, .links + > .bash_history). > > Michael > > Try this. cp the files you want into a /tmp/ subdirectory (i.e. /tmp/save). rmdir /root mkdir /root copy the files you wanted back from /tmp/save into /root (don't forget the files and directories starting with dot "." like .ssh, etc). You're done. Reboot. |
|
From: Philip P. <phi...@re...> - 2008-12-27 20:23:33
|
Michael Keuter wrote:
> I attach the diff of the changes in linux.mk
>
>
>> OK I found something in "target/device/geni586/linux.mk" line 108 and 134
>> Now the link is created, but now I got this errors ("Fehler"):
>>
I can't open a .zip file. I'll need a .bz2 or .gz file.
-Philip
>> ------------------------------------------
>> make[1]: Entering directory
>> `/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN'
>> echo 1_1_8 > VERSION ; \
>>
>> cp
>> /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile.v2.6
>> /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile
>> export
>> MINCLUDES=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include
>> ; export MISDNVERSION=1_1_8; make -C
>> /home/mk/source-control/astlinux-trunk/build_i586/linux
>> SUBDIRS=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN
>> modules CONFIG_MISDN_DRV=m CONFIG_MISDN_DSP=m
>> CONFIG_MISDN_HFCMULTI=m CONFIG_MISDN_HFCPCI=m CONFIG_MISDN_HFCUSB=m
>> CONFIG_MISDN_XHFC=m CONFIG_MISDN_HFCMINI=m CONFIG_MISDN_W6692=m
>> CONFIG_MISDN_SPEEDFAX=m CONFIG_MISDN_AVM_FRITZ=m
>> CONFIG_MISDN_NETJET=m CONFIG_MISDN_DEBUGTOOL=m
>> make[2]: Entering directory
>> `/home/mk/source-control/astlinux-trunk/build_i586/linux-2.6.26.8-astlinux'
>> CC [M]
>> /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.o
>> In file included from
>> /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/core.h:10,
>> from
>> /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:21:
>> /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include/linux/mISDNif.h:791:
>> error: field 'class_dev' has incomplete type
>> /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include/linux/mISDNif.h:824:
>> error: field 'class_dev' has incomplete type
>> /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include/linux/mISDNif.h:862:
>> error: field 'class_dev' has incomplete type
>> /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:
>> In function 'init_card':
>> /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:889:
>> warning: passing argument 2 of 'request_irq' from incompatible
>> pointer type
>> /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:895:
>> warning: passing argument 2 of 'request_irq' from incompatible
>> pointer type
>> make[3]: ***
>> [/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.o]
>> Fehler 1
>> make[2]: ***
>> [_module_/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN]
>> Fehler 2
>> make[2]: Leaving directory
>> `/home/mk/source-control/astlinux-trunk/build_i586/linux-2.6.26.8-astlinux'
>> make[1]: *** [all] Fehler 2
>> make[1]: Leaving directory
>> `/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN'
>> make: ***
>> [/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/.built1]
>> Fehler 2
>> ----------------------------------------
>>
>
> Michael
>
>
|
|
From: Philip P. <phi...@re...> - 2008-12-27 20:15:59
|
Darrick Hartman wrote: > Michael Keuter wrote: > >>> What issues did you have with trunk? >>> >>> -Philip >>> >> Hi Philip, >> >> after updating to svn rev. 2237 I could reduce the errors to >> "mISDNv1" (which I would need for testing) and "nistnet". >> When I disable then I can compile. >> Here are the error messages: (it's aGerman system: "Fehler" means "error"!) >> ------------------------------------------- >> cp >> /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile.v2.6 >> /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile >> export >> MINCLUDES=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include >> ; export MISDNVERSION=1_1_8; make -C >> /home/mk/source-control/astlinux-trunk/build_i586/linux >> SUBDIRS=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN >> modules CONFIG_MISDN_DRV=m CONFIG_MISDN_DSP=m >> CONFIG_MISDN_HFCMULTI=m CONFIG_MISDN_HFCPCI=m CONFIG_MISDN_HFCUSB=m >> CONFIG_MISDN_XHFC=m CONFIG_MISDN_HFCMINI=m CONFIG_MISDN_W6692=m >> CONFIG_MISDN_SPEEDFAX=m CONFIG_MISDN_AVM_FRITZ=m >> CONFIG_MISDN_NETJET=m CONFIG_MISDN_DEBUGTOOL=m >> make: Entering an unknown directory >> make: *** /home/mk/source-control/astlinux-trunk/build_i586/linux: >> Datei oder Verzeichnis nicht gefunden. Schluss. >> >> /* in english means: file or folder not found. Exit */ >> > > Ja! (I can read Deutsch but not write it so well). > Or you can try "export LANG=C" before compiling to force the native error messages... > >> /* the folder should be not "linux" but "linux-2.6.26.8-astlinux" */ >> > > Actually, there should be a symbolic link pointing "linux" to the > specific kernel version. If this was removed, it should be replaced--If > it was removed, it was only removed in trunk and probably unintentionally > Actually, it was intentional. Makefiles should pass in the path to their Linux environment explicitly. Assuming it's in ~/build_i586/linux (or /usr/src/linux or anywhere else) is wrong. > >> make: Leaving an unknown directory >> make[1]: *** [all] Fehler 2 >> make[1]: Leaving directory >> `/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN' >> make: *** >> [/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/.built1] >> Fehler 2 >> >> >> mkdir -p >> /home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel/.tmp_versions >> ; rm -f >> /home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel/.tmp_versions/* >> make -f scripts/Makefile.build >> obj=/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel >> scripts/Makefile.build:46: *** CFLAGS was changed in >> "/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel/Makefile". >> Fix it to use EXTRA_CFLAGS. Schluss. >> make[3]: *** >> [_module_/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel] >> Fehler 2 >> make[3]: Leaving directory >> `/home/mk/source-control/astlinux-trunk/build_i586/linux-2.6.26.8-astlinux' >> make[2]: *** [all] Fehler 2 >> make[2]: Leaving directory >> `/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel' >> make[1]: *** [sub_dirs] Fehler 2 >> make[1]: Leaving directory >> `/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a' >> make: *** >> [/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/cli/cnistnet] >> Fehler 2 >> ------------------------------------------ >> >> BTW where do I set the variable of the Astlinux-version (e.g. >> "trunk-2237") in the build environment? >> > > that's parsed and set from the current svn version (if you're building > from trunk or a non-tagged branch). > > Darrick > NISTNET is broken and has been in limbo for about 4 years. We should probably turn it off by default. -Philip |
|
From: Michael K. <mk...@we...> - 2008-12-27 14:55:02
|
I attach the diff of the changes in linux.mk
>OK I found something in "target/device/geni586/linux.mk" line 108 and 134
>Now the link is created, but now I got this errors ("Fehler"):
>
>------------------------------------------
>make[1]: Entering directory
>`/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN'
>echo 1_1_8 > VERSION ; \
>
>cp
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile.v2.6
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile
>export
>MINCLUDES=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include
>; export MISDNVERSION=1_1_8; make -C
>/home/mk/source-control/astlinux-trunk/build_i586/linux
>SUBDIRS=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN
>modules CONFIG_MISDN_DRV=m CONFIG_MISDN_DSP=m
>CONFIG_MISDN_HFCMULTI=m CONFIG_MISDN_HFCPCI=m CONFIG_MISDN_HFCUSB=m
>CONFIG_MISDN_XHFC=m CONFIG_MISDN_HFCMINI=m CONFIG_MISDN_W6692=m
>CONFIG_MISDN_SPEEDFAX=m CONFIG_MISDN_AVM_FRITZ=m
>CONFIG_MISDN_NETJET=m CONFIG_MISDN_DEBUGTOOL=m
>make[2]: Entering directory
>`/home/mk/source-control/astlinux-trunk/build_i586/linux-2.6.26.8-astlinux'
> CC [M]
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.o
>In file included from
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/core.h:10,
> from
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:21:
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include/linux/mISDNif.h:791:
>error: field 'class_dev' has incomplete type
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include/linux/mISDNif.h:824:
>error: field 'class_dev' has incomplete type
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include/linux/mISDNif.h:862:
>error: field 'class_dev' has incomplete type
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:
>In function 'init_card':
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:889:
>warning: passing argument 2 of 'request_irq' from incompatible
>pointer type
>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:895:
>warning: passing argument 2 of 'request_irq' from incompatible
>pointer type
>make[3]: ***
>[/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.o]
>Fehler 1
>make[2]: ***
>[_module_/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN]
>Fehler 2
>make[2]: Leaving directory
>`/home/mk/source-control/astlinux-trunk/build_i586/linux-2.6.26.8-astlinux'
>make[1]: *** [all] Fehler 2
>make[1]: Leaving directory
>`/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN'
>make: ***
>[/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/.built1]
>Fehler 2
>----------------------------------------
Michael
--
Email: mailto:mk...@we... |
|
From: Lonnie A. <li...@lo...> - 2008-12-26 05:07:54
|
Trunk's current BusyBox v1.11.2 has a nasty 'vi' bug type 'vi', then / then RETURN Dec 25 22:03:43 pbx user.info kernel: vi[2706]: segfault at 0 ip 08094772 sp bfc6a89c error 4 Dec 25 22:03:43 pbx user.info kernel: in busybox[8048000+6c000] Supposedly, BusyBox 1.12.2 solves this problem. Lonnie |
|
From: Michael K. <mk...@we...> - 2008-12-25 17:57:28
|
>Content-Type: multipart/signed; boundary=Apple-Mail-3-663410932; micalg=sha1; > protocol="application/pkcs7-signature" > >On Dec 25, 2008, at 3:29 AM, Michael Keuter wrote: >>Great idea to include CIFS support. >>I'd like to have that too. >> >>What's about the other way: to mount the Astlinux file system as a >>samba share? >> >>Michael >> > >I get that by using MacFuse and sshfs. Gives me the ability to "drag >and drop" files to or from the AstLinux box from my desktop. > >Am I correct in guessing that sshfs is not available for Windows boxes? > >--Tod Hi Tod, I normally do the same as you but with Macfusion (has Favorites), but sometimes it be handy to have samba (maybe disabled by default). Michael -- Email: mailto:mk...@we... |
|
From: S. E. <ser...@se...> - 2008-12-25 17:42:24
|
Tod Fitch wrote: > On Dec 25, 2008, at 3:29 AM, Michael Keuter wrote: >> Great idea to include CIFS support. >> I'd like to have that too. >> >> What's about the other way: to mount the Astlinux file system as a >> samba share? >> >> Michael >> > > I get that by using MacFuse and sshfs. Gives me the ability to "drag > and drop" files to or from the AstLinux box from my desktop. > > Am I correct in guessing that sshfs is not available for Windows boxes? > > --Tod > sshfs might be available for Windows, but I am personally more interested in having AstLinux mount my Windows share not the other way around. I need this because of a FastAGI script that connects to a FastAGI service on my Windows box that dynamically generates an IVR script and send down dynamically generated voice files in real time. I have it wired up right now with the agi-audiotx extension, where I can send the voice file down through the agi channel. I would much rather be able to mount a share from the AstLinux box and then just send down a file location. If I have to continue writting the files to the AstLinux box, I would need to implement something to clean them up when I am done with them, or risk filling up the file system / memory with un-needed files. -Steve |
|
From: Tod F. <To...@Fi...> - 2008-12-25 17:30:03
|
On Dec 25, 2008, at 3:29 AM, Michael Keuter wrote: > Great idea to include CIFS support. > I'd like to have that too. > > What's about the other way: to mount the Astlinux file system as a > samba share? > > Michael > I get that by using MacFuse and sshfs. Gives me the ability to "drag and drop" files to or from the AstLinux box from my desktop. Am I correct in guessing that sshfs is not available for Windows boxes? --Tod |
|
From: Michael K. <mk...@we...> - 2008-12-25 17:11:46
|
>Michael Keuter wrote:
>>> What issues did you have with trunk?
>>>
>>> -Philip
>>
>> Hi Philip,
>>
>> after updating to svn rev. 2237 I could reduce the errors to
>> "mISDNv1" (which I would need for testing) and "nistnet".
>> When I disable then I can compile.
>> Here are the error messages: (it's aGerman system: "Fehler" means "error"!)
>> -------------------------------------------
>> cp
>>
>>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile.v2.6
>>
>>/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile
>> export
>>
>>MINCLUDES=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include
>> ; export MISDNVERSION=1_1_8; make -C
>> /home/mk/source-control/astlinux-trunk/build_i586/linux
>>
>>SUBDIRS=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN
>> modules CONFIG_MISDN_DRV=m CONFIG_MISDN_DSP=m
>> CONFIG_MISDN_HFCMULTI=m CONFIG_MISDN_HFCPCI=m CONFIG_MISDN_HFCUSB=m
>> CONFIG_MISDN_XHFC=m CONFIG_MISDN_HFCMINI=m CONFIG_MISDN_W6692=m
>> CONFIG_MISDN_SPEEDFAX=m CONFIG_MISDN_AVM_FRITZ=m
>> CONFIG_MISDN_NETJET=m CONFIG_MISDN_DEBUGTOOL=m
>> make: Entering an unknown directory
>> make: *** /home/mk/source-control/astlinux-trunk/build_i586/linux:
>> Datei oder Verzeichnis nicht gefunden. Schluss.
>>
>> /* in english means: file or folder not found. Exit */
>
>Ja! (I can read Deutsch but not write it so well).
>
>> /* the folder should be not "linux" but "linux-2.6.26.8-astlinux" */
>
>Actually, there should be a symbolic link pointing "linux" to the
>specific kernel version. If this was removed, it should be replaced--If
>it was removed, it was only removed in trunk and probably unintentionally
>
> > make: Leaving an unknown directory
>> make[1]: *** [all] Fehler 2
>> make[1]: Leaving directory
>> `/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN'
>> make: ***
>> [/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/.built1]
> > Fehler 2
OK I found something in "target/device/geni586/linux.mk" line 108 and 134
Now the link is created, but now I got this errors ("Fehler"):
------------------------------------------
make[1]: Entering directory
`/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN'
echo 1_1_8 > VERSION ; \
cp
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile.v2.6
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile
export
MINCLUDES=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include
; export MISDNVERSION=1_1_8; make -C
/home/mk/source-control/astlinux-trunk/build_i586/linux
SUBDIRS=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN
modules CONFIG_MISDN_DRV=m CONFIG_MISDN_DSP=m
CONFIG_MISDN_HFCMULTI=m CONFIG_MISDN_HFCPCI=m CONFIG_MISDN_HFCUSB=m
CONFIG_MISDN_XHFC=m CONFIG_MISDN_HFCMINI=m CONFIG_MISDN_W6692=m
CONFIG_MISDN_SPEEDFAX=m CONFIG_MISDN_AVM_FRITZ=m
CONFIG_MISDN_NETJET=m CONFIG_MISDN_DEBUGTOOL=m
make[2]: Entering directory
`/home/mk/source-control/astlinux-trunk/build_i586/linux-2.6.26.8-astlinux'
CC [M]
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.o
In file included from
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/core.h:10,
from
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:21:
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include/linux/mISDNif.h:791:
error: field 'class_dev' has incomplete type
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include/linux/mISDNif.h:824:
error: field 'class_dev' has incomplete type
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include/linux/mISDNif.h:862:
error: field 'class_dev' has incomplete type
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:
In function 'init_card':
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:889:
warning: passing argument 2 of 'request_irq' from incompatible
pointer type
/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.c:895:
warning: passing argument 2 of 'request_irq' from incompatible
pointer type
make[3]: ***
[/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/avm_fritz.o]
Fehler 1
make[2]: ***
[_module_/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN]
Fehler 2
make[2]: Leaving directory
`/home/mk/source-control/astlinux-trunk/build_i586/linux-2.6.26.8-astlinux'
make[1]: *** [all] Fehler 2
make[1]: Leaving directory
`/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN'
make: ***
[/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/.built1]
Fehler 2
----------------------------------------
Michael
--
Email: mailto:mk...@we...
|
|
From: Michael K. <mk...@we...> - 2008-12-25 16:26:31
|
> > /* the folder should be not "linux" but "linux-2.6.26.8-astlinux" */ > >Actually, there should be a symbolic link pointing "linux" to the >specific kernel version. If this was removed, it should be replaced--If >it was removed, it was only removed in trunk and probably unintentionally Yes it is only missing in trunk. The 0.6-branch builds correctly. > > BTW where do I set the variable of the Astlinux-version (e.g. >> "trunk-2237") in the build environment? > >that's parsed and set from the current svn version (if you're building >from trunk or a non-tagged branch). > >Darrick But all the trunk-images I build are named "astlinux-trunk-" without a number. BTW: What is the best way to preserve the "/root" folder. Or in which script is the link to /tmp/root created? I know about "/mnt/kd/rc.local" and "/mnt/kd/ssh_keys" :-), but I like to have e.g. some files back (.ssh/known_hosts, .links + .bash_history). Michael -- Email: mailto:mk...@we... |
|
From: Darrick H. <dha...@dj...> - 2008-12-25 15:58:52
|
Michael Keuter wrote: >> What issues did you have with trunk? >> >> -Philip > > Hi Philip, > > after updating to svn rev. 2237 I could reduce the errors to > "mISDNv1" (which I would need for testing) and "nistnet". > When I disable then I can compile. > Here are the error messages: (it's aGerman system: "Fehler" means "error"!) > ------------------------------------------- > cp > /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile.v2.6 > /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile > export > MINCLUDES=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include > ; export MISDNVERSION=1_1_8; make -C > /home/mk/source-control/astlinux-trunk/build_i586/linux > SUBDIRS=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN > modules CONFIG_MISDN_DRV=m CONFIG_MISDN_DSP=m > CONFIG_MISDN_HFCMULTI=m CONFIG_MISDN_HFCPCI=m CONFIG_MISDN_HFCUSB=m > CONFIG_MISDN_XHFC=m CONFIG_MISDN_HFCMINI=m CONFIG_MISDN_W6692=m > CONFIG_MISDN_SPEEDFAX=m CONFIG_MISDN_AVM_FRITZ=m > CONFIG_MISDN_NETJET=m CONFIG_MISDN_DEBUGTOOL=m > make: Entering an unknown directory > make: *** /home/mk/source-control/astlinux-trunk/build_i586/linux: > Datei oder Verzeichnis nicht gefunden. Schluss. > > /* in english means: file or folder not found. Exit */ Ja! (I can read Deutsch but not write it so well). > /* the folder should be not "linux" but "linux-2.6.26.8-astlinux" */ Actually, there should be a symbolic link pointing "linux" to the specific kernel version. If this was removed, it should be replaced--If it was removed, it was only removed in trunk and probably unintentionally > make: Leaving an unknown directory > make[1]: *** [all] Fehler 2 > make[1]: Leaving directory > `/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN' > make: *** > [/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/.built1] > Fehler 2 > > > mkdir -p > /home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel/.tmp_versions > ; rm -f > /home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel/.tmp_versions/* > make -f scripts/Makefile.build > obj=/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel > scripts/Makefile.build:46: *** CFLAGS was changed in > "/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel/Makefile". > Fix it to use EXTRA_CFLAGS. Schluss. > make[3]: *** > [_module_/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel] > Fehler 2 > make[3]: Leaving directory > `/home/mk/source-control/astlinux-trunk/build_i586/linux-2.6.26.8-astlinux' > make[2]: *** [all] Fehler 2 > make[2]: Leaving directory > `/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel' > make[1]: *** [sub_dirs] Fehler 2 > make[1]: Leaving directory > `/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a' > make: *** > [/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/cli/cnistnet] > Fehler 2 > ------------------------------------------ > > BTW where do I set the variable of the Astlinux-version (e.g. > "trunk-2237") in the build environment? that's parsed and set from the current svn version (if you're building from trunk or a non-tagged branch). Darrick |
|
From: Michael K. <mk...@we...> - 2008-12-25 12:07:39
|
>What issues did you have with trunk? > >-Philip Hi Philip, after updating to svn rev. 2237 I could reduce the errors to "mISDNv1" (which I would need for testing) and "nistnet". When I disable then I can compile. Here are the error messages: (it's aGerman system: "Fehler" means "error"!) ------------------------------------------- cp /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile.v2.6 /home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN/Makefile export MINCLUDES=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/include ; export MISDNVERSION=1_1_8; make -C /home/mk/source-control/astlinux-trunk/build_i586/linux SUBDIRS=/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN/drivers/isdn/hardware/mISDN modules CONFIG_MISDN_DRV=m CONFIG_MISDN_DSP=m CONFIG_MISDN_HFCMULTI=m CONFIG_MISDN_HFCPCI=m CONFIG_MISDN_HFCUSB=m CONFIG_MISDN_XHFC=m CONFIG_MISDN_HFCMINI=m CONFIG_MISDN_W6692=m CONFIG_MISDN_SPEEDFAX=m CONFIG_MISDN_AVM_FRITZ=m CONFIG_MISDN_NETJET=m CONFIG_MISDN_DEBUGTOOL=m make: Entering an unknown directory make: *** /home/mk/source-control/astlinux-trunk/build_i586/linux: Datei oder Verzeichnis nicht gefunden. Schluss. /* in english means: file or folder not found. Exit */ /* the folder should be not "linux" but "linux-2.6.26.8-astlinux" */ make: Leaving an unknown directory make[1]: *** [all] Fehler 2 make[1]: Leaving directory `/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/mISDN' make: *** [/home/mk/source-control/astlinux-trunk/build_i586/misdnv1/.built1] Fehler 2 mkdir -p /home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel/.tmp_versions ; rm -f /home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel/.tmp_versions/* make -f scripts/Makefile.build obj=/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel scripts/Makefile.build:46: *** CFLAGS was changed in "/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel/Makefile". Fix it to use EXTRA_CFLAGS. Schluss. make[3]: *** [_module_/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel] Fehler 2 make[3]: Leaving directory `/home/mk/source-control/astlinux-trunk/build_i586/linux-2.6.26.8-astlinux' make[2]: *** [all] Fehler 2 make[2]: Leaving directory `/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/kernel' make[1]: *** [sub_dirs] Fehler 2 make[1]: Leaving directory `/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a' make: *** [/home/mk/source-control/astlinux-trunk/build_i586/nistnet-3.0a/cli/cnistnet] Fehler 2 ------------------------------------------ BTW where do I set the variable of the Astlinux-version (e.g. "trunk-2237") in the build environment? Michael -- Email: mailto:mk...@we... |
|
From: Michael K. <mk...@we...> - 2008-12-25 12:07:00
|
>One of the things that I have been missing from AstLinux is an easy way >to monitor (at a glance) the performance of a machine. Yeah, I could >ssh into the box, and use top, or iftop, but I would rather have >something included as part of the web interface (preferably something >that kept statistics around for a period of time). I have used m0n0wall >for years, and am used too the cpu and traffic graphs that are included >in its web interface. I have also worked with pfSense, and really like >the RRD graphs that display statistical information of cpu/traffic/etc >and are available from its web interface. > >I noticed that the current feature list >(http://www.astlinux.org/node/31) doesn't mention anything about cpu >and/or traffic graphs. Has anyone put any thought into whether or not >they should eventually be included? I am ready to start working on >getting rrdtool/rrdgraph (or something similar) setup, but didn't want >to waste my time if this wasn't something that others would find useful. > >Should I continue investigating rrdtool, or has someone thought of a >better tool that could be integrated? > >-Steve That would be a nice feature to have. As Bryce mentioned, that's a cool feature of M0n0wall/Askozia. BTW the correct URL for Askozia is www.askozia.com. You could contact Lonnie about integrating it into the webinterface. I attached 2 screenshots of the Live network traffic and Live CPU load. (It works only when the particular page is open.) Michael -- Email: mailto:mk...@we... |
|
From: Michael K. <mk...@we...> - 2008-12-25 12:06:18
|
>Being able to mount a CIFS (i.e. Samba/Windows) share would really >help me with some IVR scripts that I am writting. It would really >come in handy for transferring files to/from AstLinux as well. I >noticed that support for CIFS (i.e. samba shares) is not currently >enabled in either the kernel or busybox. I tested adding it to >both, and re-building, and it doesn't change the final image size >hardly at all. Was there a reason it was purposely left out, or has >no one else needed it yet? > >If there are no objections could a developer please commit the >attached svn diff (to trunk) for me? Besides the CIFS changes, this >diff file also includes the previously requested USB/Serial changes >that Michael Keuter had requested, as well as an update of the >webinterface from 1.3.05 to 1.3.06. > >By the way... the above CIFS changes have been tested on one of my >tests machines (i.e. I can properly mount and read files from a >Windows share) > >Thanks, >Steve Great idea to include CIFS support. I'd like to have that too. What's about the other way: to mount the Astlinux file system as a samba share? Michael -- Email: mailto:mk...@we... |
|
From: Bryce C. <br...@rh...> - 2008-12-25 07:06:54
|
Steve,Speaking of m0n0wall and pfSense, you might take a look at Askozia PBX<http://www.askozia.org>(not to take attention away from Astlinux). It's based on m0n0wall and is an Asterisk setup akin to Astlinux. Regards, Bryce Chidester On Wed, Dec 24, 2008 at 23:51, S. Erisman <ser...@se...> wrote: > One of the things that I have been missing from AstLinux is an easy way > to monitor (at a glance) the performance of a machine. Yeah, I could > ssh into the box, and use top, or iftop, but I would rather have > something included as part of the web interface (preferably something > that kept statistics around for a period of time). I have used m0n0wall > for years, and am used too the cpu and traffic graphs that are included > in its web interface. I have also worked with pfSense, and really like > the RRD graphs that display statistical information of cpu/traffic/etc > and are available from its web interface. > > I noticed that the current feature list > (http://www.astlinux.org/node/31) doesn't mention anything about cpu > and/or traffic graphs. Has anyone put any thought into whether or not > they should eventually be included? I am ready to start working on > getting rrdtool/rrdgraph (or something similar) setup, but didn't want > to waste my time if this wasn't something that others would find useful. > > Should I continue investigating rrdtool, or has someone thought of a > better tool that could be integrated? > > -Steve > > > ------------------------------------------------------------------------------ > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > Donations to support AstLinux are graciously accepted via PayPal to > pa...@kr.... > |
|
From: S. E. <ser...@se...> - 2008-12-25 06:52:08
|
One of the things that I have been missing from AstLinux is an easy way to monitor (at a glance) the performance of a machine. Yeah, I could ssh into the box, and use top, or iftop, but I would rather have something included as part of the web interface (preferably something that kept statistics around for a period of time). I have used m0n0wall for years, and am used too the cpu and traffic graphs that are included in its web interface. I have also worked with pfSense, and really like the RRD graphs that display statistical information of cpu/traffic/etc and are available from its web interface. I noticed that the current feature list (http://www.astlinux.org/node/31) doesn't mention anything about cpu and/or traffic graphs. Has anyone put any thought into whether or not they should eventually be included? I am ready to start working on getting rrdtool/rrdgraph (or something similar) setup, but didn't want to waste my time if this wasn't something that others would find useful. Should I continue investigating rrdtool, or has someone thought of a better tool that could be integrated? -Steve |
|
From: S. E. <ser...@se...> - 2008-12-25 06:35:45
|
Philip A. Prindeville wrote: > Michael's USB serial support was added a couple of days ago. You might > need to sync up to that commit #. > > Yeah... I did sync up, but it looks like the changes were only made to the net5501 device in the trunk and not the geni586 device. > As for USB_SERIAL_OPTION... it's not what you think. > > Yep... just looked at what that was... I agree... not needed. ;) -Steve > -Philip > > > S. Erisman wrote: > >> Being able to mount a CIFS (i.e. Samba/Windows) share would really >> help me with some IVR scripts that I am writting. It would really >> come in handy for transferring files to/from AstLinux as well. I >> noticed that support for CIFS (i.e. samba shares) is not currently >> enabled in either the kernel or busybox. I tested adding it to both, >> and re-building, and it doesn't change the final image size hardly at >> all. Was there a reason it was purposely left out, or has no one else >> needed it yet? >> >> If there are no objections could a developer please commit the >> attached svn diff (to trunk) for me? Besides the CIFS changes, this >> diff file also includes the previously requested USB/Serial changes >> that Michael Keuter had requested, as well as an update of the >> webinterface from 1.3.05 to 1.3.06. >> >> By the way... the above CIFS changes have been tested on one of my >> tests machines (i.e. I can properly mount and read files from a >> Windows share) >> >> Thanks, >> Steve >> > > > ------------------------------------------------------------------------------ > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > |
|
From: S. E. <ser...@se...> - 2008-12-25 06:31:49
|
Philip A. Prindeville wrote:
> Stephen Erisman wrote:
>
>> I have recently compiled some interesting results while timing builds
>> on different machines.
>>
>> I currently have 3 test build machines that I have been using (all
>> Ubuntu 8.10 at this point)
>>
>> The first (at home) is running as a Virtual Machine on Hyper-V
>> (Windows Server 2008). The host machine is a dual socket with 2x
>> Opteron 2214 (each is a 2.2 GHz dual-core) with 8GB ram and 4x 500GB
>> 7200rpm SATA drives in a chipset RAID-5 array (pretty slow). The
>> ubuntu virtual machine is set up with 1 core, 1GB ram, and 1 20GB
>> virtual hard drive. Here are the compile times that are reported with
>> a 'time make all runfs': (fyi... all times assume that the
>> toolchain_build_i586 directory is already built, but that the
>> build_i586 directory doesn't yet exist)
>>
>> real 193m1.038s
>> user 76m2.397s
>> sys 69m51.630s
>>
>> The second machine (at work) is also running as a Virtual Machine on
>> Hyper-V, but with different hardware. The host machine is a dual
>> socket with 2x Xeon x5355 (each is a 2.66 GHz quad-core) with 32 GB
>> ram, and 8x15k rpm SAS drives on a hardware RAID-5 array. Again, the
>> ubuntu virtual machine is set up with 1 core, 1GB ram, and 1 20GB
>> virtual hard drives. Here are the compile times for the same scenario
>> as above:
>>
>> real 114m30.526s
>> user 36m5.799s
>> sys 55m54.806s
>>
>>
>> The third machine (at home) is a dedicated Ubuntu machine with an Core
>> 2 Duo 2.0 GHz (dual core), 2GB ram (laptop style cpu and ram), and 2x
>> 36GB 10k rpm SCSI drives on a hardware RAID-0 (striping) array
>> (Adaptec 2110s PCI card). This setup is by far the fastest, (I
>> suspect) largely because ubuntu has access to 2 cores. Here are the
>> compile times for the same scenario as above:
>>
>> real 45m14.989s
>> user 40m20.847s
>> sys 10m51.017s
>>
>>
>> I am interested in what build machine configurations other developers
>> have and what kind of compile times you see with your respective
>> setups. I had hoped that my first machine would have been faster (I
>> prefer to keep things virtual), but the builds were getting to be too
>> painfully slow. At some point I would like to upgrade this machine to
>> 2x quad-cores and have a true hardware raid controller, but I haven't
>> been able to justify the cost yet. Hyper-V also has a limitation that
>> Linux guests can only be assigned 1 core (Windows guests can have up
>> to 4-cores). Maybe I will switch to VMWare on Linux for the host to
>> overcome this limitation. Has anyone else messed around with
>> virtualized build servers? If so, what other virtualization platforms
>> have people tried? Alternatively, I may build a permanent dedicated
>> build server, but I wanted to get an idea of what hardware others were
>> running with before purchasing anything. It would also be interesting
>> to see how build times are effected by disk speed vs. cpu speed.
>>
>> Anyone care to share their results?
>>
>> -Steve
>>
>
>
By the way... I did some tests on a Fedora 10 (x86) virtual machine with
a similar setup to the Ubuntu 8.10 virtual machine on my work test
machine. I expected it to be about the same as the Ubuntu image (being
on the same hardware), and still haven't investigated why it was
slower. Maybe it was just a one-time fluke. Anyway, here are the numbers:
real 144m17.379s
user 44m57.974s
sys 55m10.905s
> I'm trying to set up a build server for the project developers to use.
>
> It's a Phenom 9950 Quad core @2.66GHz, 8GB memory, and 4X500GB (150Mb/s)
> SATA RAID5 array (as per previous message).
>
Nice! I have been looking at the new 45nm Shanghi Opterons to upgrade
my home machine, but haven't decided to spend the money yet ;) I will
probably get a Phenom some time next year as well.
> I see builds of build_i586 taking 43 minutes, but that's because I do a
> "-j1" since I'm aware of certain race conditions in the Makefiles.
>
>
If you can elaborate on your ideas of how to fix this maybe I can help
implement the fixes.
> But then building the same target on a Toshiba laptop with a 1GHz
> Centrino and 1GB of memory took about the same amount of time... I'm
> thinking that we're not using parallelization as much as we could be,
> and that the downloads that Asterisk does of the various sound files
> (even if they've been previously fetched) slows us down a lot.
>
>
I can probably help out here too... but I will be out of town for the
next week and a half, so not till early next year. Still, let me know
if you have any ideas and I can see about implementing some of them.
-Steve
|
|
From: Philip A. P. <phi...@re...> - 2008-12-25 06:30:58
|
Michael's USB serial support was added a couple of days ago. You might need to sync up to that commit #. As for USB_SERIAL_OPTION... it's not what you think. -Philip S. Erisman wrote: > Being able to mount a CIFS (i.e. Samba/Windows) share would really > help me with some IVR scripts that I am writting. It would really > come in handy for transferring files to/from AstLinux as well. I > noticed that support for CIFS (i.e. samba shares) is not currently > enabled in either the kernel or busybox. I tested adding it to both, > and re-building, and it doesn't change the final image size hardly at > all. Was there a reason it was purposely left out, or has no one else > needed it yet? > > If there are no objections could a developer please commit the > attached svn diff (to trunk) for me? Besides the CIFS changes, this > diff file also includes the previously requested USB/Serial changes > that Michael Keuter had requested, as well as an update of the > webinterface from 1.3.05 to 1.3.06. > > By the way... the above CIFS changes have been tested on one of my > tests machines (i.e. I can properly mount and read files from a > Windows share) > > Thanks, > Steve |
|
From: S. E. <ser...@se...> - 2008-12-25 06:20:10
|
I recently went through the effort to test out Fedora 10, and thought I
would document the steps needed to prepare a fresh install as an
AstLinux build machine.
These steps have been proven on a fresh install of Fedora 10 Desktop (x86)
1. Open up a terminal
2. Type 'su root' and then enter your root password.
3. Type the following commands answering 'Y' when it asks for permission
to install
yum install subversion
yum install make
yum install gcc
yum install nasm
yum install autoconf
yum install gettext
yum install texinfo
yum install bison
yum install flex
yum install wget
yum install byacc
yum install patch
yum install zlib-devel
4. Type 'exit' to stop being a root user.
5. Close the terminal
Now you should be set-up to follow the rest of the steps as detailed at:
http://www.astlinux.org/node/24
Hope this helps someone at some point...
-Steve
|
|
From: S. E. <ser...@se...> - 2008-12-25 06:08:54
|
Being able to mount a CIFS (i.e. Samba/Windows) share would really help me with some IVR scripts that I am writting. It would really come in handy for transferring files to/from AstLinux as well. I noticed that support for CIFS (i.e. samba shares) is not currently enabled in either the kernel or busybox. I tested adding it to both, and re-building, and it doesn't change the final image size hardly at all. Was there a reason it was purposely left out, or has no one else needed it yet? If there are no objections could a developer please commit the attached svn diff (to trunk) for me? Besides the CIFS changes, this diff file also includes the previously requested USB/Serial changes that Michael Keuter had requested, as well as an update of the webinterface from 1.3.05 to 1.3.06. By the way... the above CIFS changes have been tested on one of my tests machines (i.e. I can properly mount and read files from a Windows share) Thanks, Steve |
|
From: Philip A. P. <phi...@re...> - 2008-12-23 23:04:09
|
Stephen Erisman wrote: > Philip A. Prindeville wrote: >> S. Erisman wrote: >> >>> Philip A. Prindeville wrote: >>> >>>> S. Erisman wrote: >>>> >>>>> By the way, I installed Fedora 10 (x86) earlier today and like it so >>>>> far. I haven't done a full build using it yet though. >>>>> >>>>> Thanks, >>>>> Steve >>>>> >>>>> >>>> FC10, huh? That's pretty bleeding edge... >>>> >>>> -Philip >>>> >>>> >>> Yeah, it installed and seemed to work fine (although really slow) as a >>> virtual machine. >>> >>> I ran into issues trying to get it run outside of the virtual machine >>> however. It doesn't seem to like the raid controller that this >>> particular server has (Adaptec 2110S). It installs fine, but then >>> can't find the correct volume when it reboots. I might try it on >>> something else later. >>> >>> Ubuntu 8.10 installed and runs very nicely on the same hardware. I >>> think I have resolved my build weirdness on the Ubuntu machine, so I >>> will probably just stick with that for now. >>> >>> -Steve >>> >> >> RAID controller???? :-) >> >> Most people install it on a P4 class machine with a 500MB IDE (not even >> EIDE) disk drive, and an Intel ICH controller. :-) >> >> Try something more pedestrian. :-) >> >> Anyone else get a chance to run a recent build of trunk on a generic PC >> platform? >> >> -Philip >> > 500MB IDE??? How is that possible? The build_i586 directory alone is > in the gigabytes. You must be referring to the AstLinux appliance > machine? I was talking about setting up the build server, not the > appliance. For the appliance, I have been using Neoware thin clients > with small industrial disk-on-modules (i.e. 256MB) and they have been > working perfectly. My comments above were about not getting Fedora 10 > installed on my test build server with the hardware raid controller > (even though it should be supported) > > -Steve Oh, you were talking about your build machine... your host. I was talking about your target machine... never mind. I'm feeling your pain: I ordered a Promise FastTrak TX4650 PCI-e SATA RAID5 controller, which they claimed was supported in-the-box for FC9, but it's actually not. So I'm sending it back and getting a 3Ware 9650SE instead. -Philip |
|
From: Philip A. P. <phi...@re...> - 2008-12-23 23:04:06
|
Stephen Erisman wrote: > I have recently compiled some interesting results while timing builds > on different machines. > > I currently have 3 test build machines that I have been using (all > Ubuntu 8.10 at this point) > > The first (at home) is running as a Virtual Machine on Hyper-V > (Windows Server 2008). The host machine is a dual socket with 2x > Opteron 2214 (each is a 2.2 GHz dual-core) with 8GB ram and 4x 500GB > 7200rpm SATA drives in a chipset RAID-5 array (pretty slow). The > ubuntu virtual machine is set up with 1 core, 1GB ram, and 1 20GB > virtual hard drive. Here are the compile times that are reported with > a 'time make all runfs': (fyi... all times assume that the > toolchain_build_i586 directory is already built, but that the > build_i586 directory doesn't yet exist) > > real 193m1.038s > user 76m2.397s > sys 69m51.630s > > The second machine (at work) is also running as a Virtual Machine on > Hyper-V, but with different hardware. The host machine is a dual > socket with 2x Xeon x5355 (each is a 2.66 GHz quad-core) with 32 GB > ram, and 8x15k rpm SAS drives on a hardware RAID-5 array. Again, the > ubuntu virtual machine is set up with 1 core, 1GB ram, and 1 20GB > virtual hard drives. Here are the compile times for the same scenario > as above: > > real 114m30.526s > user 36m5.799s > sys 55m54.806s > > > The third machine (at home) is a dedicated Ubuntu machine with an Core > 2 Duo 2.0 GHz (dual core), 2GB ram (laptop style cpu and ram), and 2x > 36GB 10k rpm SCSI drives on a hardware RAID-0 (striping) array > (Adaptec 2110s PCI card). This setup is by far the fastest, (I > suspect) largely because ubuntu has access to 2 cores. Here are the > compile times for the same scenario as above: > > real 45m14.989s > user 40m20.847s > sys 10m51.017s > > > I am interested in what build machine configurations other developers > have and what kind of compile times you see with your respective > setups. I had hoped that my first machine would have been faster (I > prefer to keep things virtual), but the builds were getting to be too > painfully slow. At some point I would like to upgrade this machine to > 2x quad-cores and have a true hardware raid controller, but I haven't > been able to justify the cost yet. Hyper-V also has a limitation that > Linux guests can only be assigned 1 core (Windows guests can have up > to 4-cores). Maybe I will switch to VMWare on Linux for the host to > overcome this limitation. Has anyone else messed around with > virtualized build servers? If so, what other virtualization platforms > have people tried? Alternatively, I may build a permanent dedicated > build server, but I wanted to get an idea of what hardware others were > running with before purchasing anything. It would also be interesting > to see how build times are effected by disk speed vs. cpu speed. > > Anyone care to share their results? > > -Steve I'm trying to set up a build server for the project developers to use. It's a Phenom 9950 Quad core @2.66GHz, 8GB memory, and 4X500GB (150Mb/s) SATA RAID5 array (as per previous message). I see builds of build_i586 taking 43 minutes, but that's because I do a "-j1" since I'm aware of certain race conditions in the Makefiles. But then building the same target on a Toshiba laptop with a 1GHz Centrino and 1GB of memory took about the same amount of time... I'm thinking that we're not using parallelization as much as we could be, and that the downloads that Asterisk does of the various sound files (even if they've been previously fetched) slows us down a lot. -Philip |
8 messages has been excluded from this view by a project administrator.
