Re: usermin/webmin
On Fri, Sep 21, 2007 at 09:04:36PM +0200, Hans-J. Ullrich wrote: > webmin and usermin were kicked off a long time ago, because of a lot of bugs > and errors. How are things handled ? Do you look after some time, if things > have changed, to get those packages back again ? Well the build system for webmin is a pain (well mainly the lack of one), and the debian package was a real mess before. I am not surprised no one wanted to maintain it anymore. I am not a fan of webmin, it's messy internal spagetti code style, the many required checks for which type of system it is on in order to deal with that distributions (and version) ways of doing things, or how darn slow that bloated perl code is, or how it is so tied to it's own web server that trying to run it on another web server doesn't work, etc. I do work with it a lot though since it is what the product I work on uses as its configuration interface (although heavily modified in some places). -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
usermin/webmin
Dear maintainers, webmin and usermin were kicked off a long time ago, because of a lot of bugs and errors. How are things handled ? Do you look after some time, if things have changed, to get those packages back again ? Regards Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot sequence and network (madwifi)
2007/9/21, Hans-J. Ullrich <[EMAIL PROTECTED]>: > Am Freitag 21 September 2007 schrieb Martin Marcher: > > 2007/9/21, Hans-J. Ullrich <[EMAIL PROTECTED]>: > iface ath0 inet dhcp > wireless_mode managed > wireless_essid myessid > wireless_key TOPSECRET > wireless_ap auto > wireless_keymode open weren't that wireless-* options? I just left work and are visiting my parents so I don't have my debian box near me just a first thing to check -- http://noneisyours.marcher.name http://feeds.feedburner.com/NoneIsYours -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Opinion question (Core2 Duo)
On Fri, Sep 21, 2007 at 09:48:01AM -0400, Lennart Sorensen wrote: > On Tue, Sep 18, 2007 at 06:29:31PM -0400, Douglas A. Tutty wrote: > > > Where would you go for floating point? Last time I looked, Cray used > > Opterons as nodes in its supercomputers. > > True, but in terms of memory bandwidth the opteron is very good, and > hypertransport allows them to pop fpga's and other custom logic chips > into cpu sockets and have amazing acess to the main cpus and memory at > quite low cost. After all if you can turn your key calculation into a > hardware operation in an fpga, a general purpose cpu generally has no > hope of competing. Now we just need fpga's to become as comodity as Opterons, then get the kernel to use them. :)) Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Opinion question (Core2 Duo)
On Tue, Sep 18, 2007 at 06:29:31PM -0400, Douglas A. Tutty wrote: > Is there a free alternative to GCC? Not that I know of. > Where would you go for floating point? Last time I looked, Cray used > Opterons as nodes in its supercomputers. True, but in terms of memory bandwidth the opteron is very good, and hypertransport allows them to pop fpga's and other custom logic chips into cpu sockets and have amazing acess to the main cpus and memory at quite low cost. After all if you can turn your key calculation into a hardware operation in an fpga, a general purpose cpu generally has no hope of competing. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot sequence and network (madwifi)
Am Freitag 21 September 2007 schrieb Martin Marcher: > 2007/9/21, Hans-J. Ullrich <[EMAIL PROTECTED]>: > > When I manually configure the cards, using "/etc/init.d/network restart", > > the card is seeing the accesspoint (98 percent at the first time, at 2 > > percent I have to do it twice) and the dhcpclient is giving the IP as > > required. > > > > Conditions: > > I have two network cards, one wired (eth0) with a fixed IP (but not > > connected), and the wlan card (ath0) obtaining an IP with dhcp. > > Hint: both network card are configured, to access to the same gateway. > > > > Checked: All modules are loaded properly at boot, before obtaining an IP > > > > Checked: Without done an "/etc/netwiork/interfaces restart", a manually > > command "dhcpclient 192.168.1.1 ath0" does not work. Error message is: > > Device not known. > > > > Checked: ifconfig is telling me all devices, wifi0 and ath0 are > > available. > > > > So, what is the difference between the behaviour at first boot, and the > > behaviour doing an "/etc/init.d/networking restart" ? > > how does /etc/network/interfaces and your wpa config (if you use it) look? > > martin > > -- > http://noneisyours.marcher.name > http://feeds.feedburner.com/NoneIsYours Hi Martin, this is my /etc/network/interfaces auto lo eth0 ath0 usb0 iface lo inet loopback iface eth0 inet static address 192.168.1.20 netmask 255.255.255.0 broadcast 192.168.0.255 gateway 192.168.1.1 Accesspoint # # iface eth1 inet static # wireless_mode Master # wireless_essid any # wireless_keymode open # wireless_channel 3 # address 192.168.5.1 # netmask 255.255.255.0 # broadcast 192.168.5.255 # gateway 192.168.5.1 at home ## iface ath0 inet dhcp wireless_mode managed wireless_essid myessid wireless_key TOPSECRET wireless_ap auto wireless_keymode open on the road ## # iface ath0 inet dhcp # wireless_mode managed # wireless_essid any # wireless_key off # wireless_ap auto # wireless_keymode open # Work network configuration # iface eth0 inet static # address 195.37.206.71 # netmask 255.255.255.224 # broadcast 195.37.206.255 # gateway 195.37.206.65 mapping hotplug script grep map usb0 iface usb0 inet static address 192.168.129.200 pointopoint 192.168.129.201 netmask 255.255.255.0 # network 192.168.129.0 # broadcast 192.168.129.255 snap - You guess it, I do not populate my secret key. Anyway, I am still using WEP, as my AP is too old, to support WPA. This is no problem for me, as in case of the defective HF-PA it is only sending with 10mW, which is enough for sending within my living rooms, but too low to send into the far(!) world. Regards Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot sequence and network (madwifi)
2007/9/21, Hans-J. Ullrich <[EMAIL PROTECTED]>: > When I manually configure the cards, using "/etc/init.d/network restart", > the card is seeing the accesspoint (98 percent at the first time, at 2 percent > I have to do it twice) and the dhcpclient is giving the IP as required. > > Conditions: > I have two network cards, one wired (eth0) with a fixed IP (but not > connected), and the wlan card (ath0) obtaining an IP with dhcp. > Hint: both network card are configured, to access to the same gateway. > > Checked: All modules are loaded properly at boot, before obtaining an IP > > Checked: Without done an "/etc/netwiork/interfaces restart", a manually > command "dhcpclient 192.168.1.1 ath0" does not work. Error message is: Device > not known. > > Checked: ifconfig is telling me all devices, wifi0 and ath0 are available. > > So, what is the difference between the behaviour at first boot, and the > behaviour doing an "/etc/init.d/networking restart" ? how does /etc/network/interfaces and your wpa config (if you use it) look? martin -- http://noneisyours.marcher.name http://feeds.feedburner.com/NoneIsYours -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
boot sequence and network (madwifi)
Hello all, I try to understand some things, maybe you can help me. The Problem: I discovered, that never(!) at first boot the wlan card is getting an IP by the accesspoint. And at first boot, the access point is never seen by the system, and thus dhcpclient cannot give an IP to the card. When I manually configure the cards, using "/etc/init.d/network restart", the card is seeing the accesspoint (98 percent at the first time, at 2 percent I have to do it twice) and the dhcpclient is giving the IP as required. Conditions: I have two network cards, one wired (eth0) with a fixed IP (but not connected), and the wlan card (ath0) obtaining an IP with dhcp. Hint: both network card are configured, to access to the same gateway. Checked: All modules are loaded properly at boot, before obtaining an IP Checked: Without done an "/etc/netwiork/interfaces restart", a manually command "dhcpclient 192.168.1.1 ath0" does not work. Error message is: Device not known. Checked: ifconfig is telling me all devices, wifi0 and ath0 are available. So, what is the difference between the behaviour at first boot, and the behaviour doing an "/etc/init.d/networking restart" ? It would be nice, if you can help me to understand. Regards Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
