We have found and fixed 2 significant bugs, and we think that it's worth a maintenance release.

Bug1 : for computers without any optical device, where the fstab was altered upon reboot.

Bug2 : for computers with multiple network interfaces where some interfaces were not correctly configured at startup.

The complete changelog between 4.6 and 4.6.1 includes :

-----< June 06 2007 >---- UDEV TOOLS BUGFIX -------

[ap] Updated udevtools-1.0-i486-48.1.tgz (bugfix for configs without any optical device)

-----< June 05 2007 >---- ALSA -------

[ap] Updated alsa-utils-1.0.14-i486-48.1.tgz (new major stable version)
[l] Updated alsa-lib-1.0.14-i486-48.1.tgz (new major stable version)
[l] Updated alsa-oss-1.0.14-i486-48.1.tgz (new major stable version)

-----< June 04 2007 >---- FIREFOX -------

[a] Updated reiserfsprogs-3.6.19-i486-2.tgz
[ap] Updated gutenprint-5.1.2-i486-48.1.tgz (number of bug fixes and improved quality on newer Epson printers, and fixes zenbuild ).
[ap] Updated systemtools-4.8-i486-48.1.tgz (added anti-spoofing support to xnetconf)
[l] Updated libmpcdec-1.2.6-i486-48.1.tgz (Fix an infinite loop regression from 1.2.3 and Fix possible noise at the beginning of files)
[n] Updated nfs-utils-1.1.0-i486-2.tgz
[n] Updated network-scripts-4.8-i486-48.1.tgz (bugfix in rc.inet1, thanks fromylop)
[xap] Updated firefox-2.0.0.4-i686-48.1.tgz (Security fixes)

You can download it from the following locations :
http://zen-repo.meticul.eu/i486/zenwalk ... -4.6.1.iso
http://zenwalk.linuxish.net/i486/zenwal ... -4.6.1.iso
ftp://ftp.nux.ipb.pt/pub/dists/zenwalk/ ... -4.6.1.iso

Cheers
JP

Thanks Jp...

So still we have to follow Snapshot for toolchain doc before upgrading right  As well is it safe to go for an upgrade

I hate to break my system and re-install once again.... 

I successfully walked someone through it without any docs, so yes, you can upgrade . Remember: glibc first .

For those of us who did a clean install of 4.6, can we just grab the updates via netpkg? Or is a clean install of 4.6.1 recommended?
EDIT: It seems the updates via netpkg are sufficient. Is that true?

I'm at -current and I'm good so far.

Yes.

What??
You mean, i should first install Glibc package from Snapshot and then install rest from current, i mean i should follow Snapshot for toolchain in simple words...Right??

I feel that, Zenwalk dev team (Jp especially) is hurrying up to releases the new ver very fast. I dont thin thats necessary. Take your time and release a good upto date stable, less buggy distro. Even the same issue i see with Ubuntu team as well. Every 6 months a new release, will have a chance to induce much of the unstability or bugs, or even might miss some new features.

So what i wish to say for Jp + teams is, just a lil bit of more time and give out a good stable one plus alot of new features induced into it???

P.S: The current ver are really kool...

@Zenwalk addict:  I agree, but remember, (http://en.wikipedia.org/wiki/Murphy's_law)



@(dev team): its cool  Think: Zen

Yes buddy, how much time you take, some or the other way a bug will get in. I am not talking about that. I just said, dont run very very fast you might fall into a pit...Thats what i said...Instead of releasing every new ver for 4-5 monts, make it 6-7. That way, we can reduce lets say a 10 bugs as usual into 4-5 bugs...Thats what i meant.

Again, Wiki.zenwalk.org snapshot for toolchain article page isnt working. In short, wiki site isnt working...Why?? Is it the problem of the server, or is it down for maintenance??

The site is down because the the Zenwalk Live site was attacked for the second time in a week (the wiki and Zenwalk Live's site are on the same machine). We are going to move the wiki to another machine asap so it will come back up. In the meantime I will make life hard for the attacker and will rebuild the Zenwalk Live site hardened.

Also, there is NO software (Zenwalk packages) on the attacked machine so Zenwalk's package repositories are untouched in case you are curious. Our sites are on many different machines.



Michael

If you upgrade from 4.6 to 4.6.1 then there's no Glibc story - just upgrade as the "Current" Changelog goes. Borromini was talking of the past ... are you upgrading from 4.4.1 ?

Best regards,
Claus

Thank you for the kind words.  On the point of release schedule, I don't agree that delay equates to fewer bugs.  The first bug fixed in 4.6 had been in the betas, unreported, for more than 4 weeks; who knows how much longer it might have stayed there?  It was reported within 4 days of the 4.6 release, and fixed the same day.

Longer beta testing (with relatively few users) is nowhere near as effective as more users in flushing out bugs.  In this case, the bug was waiting for a user with multiple network cards.

You are right that if a dev feels rushed, he is likely to create more bugs in the first place; but below a certain pressure, more time equates to more code, with its own helping of bugs.  The 4.6 release schedule was much less frantic than in the pre-4.4 era, and I think JP has found the right balance.

...  markc

i understand thats why i said:



again, Think: Zen 
Carl