But seriously: please keep calm, nobody said we will never support it
We currently working on a V4 version with full PI/AMD K6 support, but it will definitley not included in 4.000 because of some lib dependences. Please check regular the announcement forum for news and release dates for a PI/K6 enabled V4.
It's good to hear that K6's will be supported, I was just about to post on the hackers forum "how can I slipstream my own kernel into ASL"
Dumb question: I am running ASL 3.2 up2date'ing it's little heart out, will I reboot one day and find it won't get back on its feet? Or is everyone talking about ASL v4?
Dumb Question #2: When v4 is ready to support K6-2's will I need to reconfigure my whole system, or can it just upgrade, also will my existing home liscence grandfathered over or do I need to get another?
PS[:D]on't forget the little guy astaro it's the linux way to be efficient as possible and with my 3 computer network my K6-2 200MHz is 90-99% too much CPU already.
I've successfully installed and am now running 4.107 with a PI and 164Mb RAM (see below). I was able to import backup files from my previous 3.207 installation.
I have all the spam filtering turned on and will be hitting the HTTP and DNS Proxy very hard using grub (http://grub.org) within the coming days.
I did have some problems initially not being able to login to the webadmin. I had imported settings specifying webadmin_port = 8888. I didn't see it listening so I cleared this setting (/etc/wfe/conf/settings), restarted the system and was then able to login via webadmin. Changing the webadmin_port within webadmin was accepted and is working fine.
Although everything seems to be functioning fine, my system is logging the following in /var/log/mdwlog about every 3 seconds:
################## #AN ERROR OCCURED #mdw_deamon.pl: modules::File::md5sum() => No arguments given! # Function has been called in package main at mdw_deamon.pl line 1099. # 2003/05/17 05:23:17 # modules::Error::Error # modules::File::md5sum
Use of uninitialized value in string eq at mdw_deamon.pl line 1100. Use of uninitialized value in string eq at mdw_deamon.pl line 1100. ---- log_end ---- ---- cpuinfo ----- vendor_id : GenuineIntel cpu family : 5 model : 4 model name : Pentium MMX stepping : 3 cpu MHz : 199.971
just installed 4.107 on my VIA EPIA6000M (C3 600 MHz CPU, 256 MB RAM, 20 GB Fujitsu Notebook HDD) based Astaro box. No Problems during the setup, my Backup (from 3.018) has been imported correctly. Onboard NIC and my second NIC (Intel EtherExpress 100/S+) are working without any flaws.
Speed of the WUI is really impressive, i can't notice any difference to WUI on our office astaro box (Pentium 4 2.0 GHz). Even the DHCP page that took ages (up to 3 minutes) to load with 3.018 tooks now less a second to be displayed. So far i didn't encountered any Problems!
I have installed on a Compaq G3 P4 with Compaq 5si controller. Setup went with out a hitch and booted fine. The box has 2 broadcom NIC's and the system has them as this: Internal (Standard ethernet interface) on eth0 ([unknown vendor / unknown chipset] )
thanks for your anwer. I use the 4.107 Beta Version. I use a test license and a orginal license. Same Problem. about 30 minutes i cant log in in the webadmin. it says "license expired". The i stop the licens manager and start it. it works, but only for 30 minutes....
Using an ASUS TX97, K6-2 400, 256 mb SDRAM, Maxtor 90650U2 6.8gb and WD28400 8.5gb, Realtek 8139 internal NIC, Realtek 8029 external NIC, ACPI on. After all is said and done, ASL 4.107 is working flawlessly, but with comments:
1. CD Boot Hang.
During first install on the Maxtor 90650U2, the CD would start to boot, but after pressing Enter at the "boot:" prompt, boot would hang at "Loading Initrd". Observed this hang for about five minutes before rebooting using ctrl-alt-delete. Tried several times. Number of dots following "Loading Initrd" varied when hang occurred on various tries. Finally pressed "F1" at the "boot:" prompt, typed "classic", and the boot/install proceeded normally, but read on.
After running 4.107 for several days on the Maxtor 90650U2, I decided to install 4.107 on the WD28400 for a backup. On this install, there were no hangs at "Loading Initrd". Started boot four times with no hangs. Reinstalled the Maxtor 90650U2 and started the CD boot, and still no hangs with four tries.
I suspect my CD Drive is dirty/failing, but thought I would report this "problem" anyway.
2 Install.
I use only the basic firewall; i.e. no dhcp server, PPTP, QOS, VPN, or proxies. I do set up the dns and smpt proxies for my local dhcp/dns/mail server, but then disable them.
Backup from ASL 4.004 restored to 4.107 flawlessly.
I schedule both Up2date services and automatic backup. These work flawlessly.
MAC spoofing as in ASL 3.2 works.
3. Webmin Site Certificate.
On new installs, after restoring from backup, I had to "Save" the "Certificate Information" before I could successfully "Import the Certificate into Browser" (Windows 2000, Internet Explorer 6). This might be in the ASL manual - I've never needed nor been inclined to read it.
4. Shutdown (AT Power Supply):
Using "shutdown -h now" the beeps start about five seconds before "Power Down." prompt appears on the display. Beeps start at the second "Remounting / read only" prompt. This prompt is followed by the "flushing ide devices: hda hdc" and "Power Down." prompts. This probably is mostly cosmetic, but I am reporting it nonetheless.
now i did ran into a problem. The Proxy is not working for http when in Transparent mode. HTTPS is working fine . I double checked everything (DNS works fine, DNS proxy is turned on, pinging a host by hostname via "net tools" works fine) but can't find anything. But as soon as i switch the http proxy to transparent mode alle clients can only access https sides, no http anymore. The HTTP Proxy log file is empty. [:(]
Due to some strange behavior of my old ASL 3.2 instalation I decided to upgrade our company ASL box to version 4.107. Eventhough it is not recomanded to use Beta versions in working production enviroment I made it on purposse to see the difference.
Since 3 days I had no problem with NICs, so new NIC kernel drivers are working OK. Users are working without any problem. Restore of configuration from 3.218 worked as it gets!
With version 3.2 I had in the night when logs were written, quite some problems and I always got up to 7 mails about process taking to much memory. Now those mails are gone, eventhough nothing changed on network.
At the end I have to say that version 4.107 is working for me without problem at full rate and can be easily used.
