On Fri, 10 Jan 2003 18:50:01 +0200 Buchan Milne <[EMAIL PROTECTED]> wrote:
I've been working on a physical project all day, and I must say that if the rest of this thread is as civil as what I've read so far, I *am* impressed and encouraged by the responses... but the main point is being missed: the stability of the 9.x series... > Chmouel Boudjnah wrote: > > Pierre Fortin <[EMAIL PROTECTED]> writes: > > > >>5. Installation of LinModem support was more troublesome than in 8.2 > >-->while not delivered in a Mandrake distro, at least ensuring that a > >new>distro does not make installation of LinModem s/w more difficult is > >>important to winning new users. > > > > this is something that are out of our hands. > > > > Bad answer. Mandrake 9.0 Workstation DVD has Rockwell HCF and HSF > winmodem drivers, but no Lucent Technologies Winmodem drivers. > > There are rpms availble on the net, and the sources (weird script to > build only binary RPM for some reason) which works just fine out the > box. I don't recall the details; but there were several pre-reqs before getting that script to work... I think the problems were due to missing -devel rpms, which is strange since I did request a "development" install... Again, this is not a 9.0 support request, rather a request for extra care before releasing 9.1... > Pierre, I don't know if you still have a Mandrakeclub account or ever > did, but you may want to vote for the ltmodem (assuming that's the one > you have) entry that I made for 9.0/i586. I was one of the first to contribute, before the "Club", and was a Club member until a couple of weeks ago... since I have not renewed for the reasons stated, I don't wish to freeload -- my account *may* still be active; but I've reverted to a "convince me, I'm a new user" mode... > > > >>6. CD filesystem got confused (displaying "??????" for each filename > >and>permission denied) requiring a reboot (there's that fscking word > >again) > > > > Easier fix is to eject and reinsert media ... That doesn't work after the system has been running for a while... > > that supermount suckness, try disable it. Even that doesn't work when the system gets pissy. I'm still puzzled as to how the system is architected... it would seem that how is filesysem is *mounted* should make no difference to how the files are *accessed*. Wouldn't it make sense to say supermount can't mount/umount than to say it can't access, re-access, read, whatever, an already mounted filesystem...?? > When Andrei has posted patches that fix these issues, and Danny has a > 2.4.16-19.6mdk which uses these patches, which fixes all the issues for > me? Please, if Mandrake is going to have supermount enabled by default, > it *must* work reliably on every machine anyone can test on for every > device it's used for. > > RH has a working solution (automount), and they're not supposed to be a > desktop distro (or weren't). Maybe they know how to separate mounting from access...? > BTW, 700MB ISOs and stuffed supermount on iffy drives (such as a > 3-year-old 2x2x6 CD-RW and a 4-year-old 24x CDROM that works fine for > most other things) really cripples a Mandrake installation. There's no > way you can install RPMs from the discs, you have to copy the ones you > can access to disk, and install them there. and that is precisely what newcomers to Mandrake will not have the skills or inclination to figure out... > Installation would *not* have complete if I didn't have a full 9.0 tree > on my laptop so I could do a network install on the affected machine. > > Please, consider going to 4*650MB instead of 3*700MB. Otherwise Mandrake > 9.1 will cost me R300 extra (half a club membership!) per old single > machine I support. Rather than repeat my past comments on the cost of blank CDs vs my time, how about saying it this way: a blank CD costs less than one minute of salaried time and several minutes to burn (I can be doing something else while it's burning); but pissing around with a burning process that goes through the motions and produces blank CDs costs a whole lot more. > > > >>7. Sound stopped working (lsof showed several apps accessing sound) -- > >>rebooted to fix. > > > > > > which sound card. Whatever is in a ThinkPad A20m Sound Driver:3.8.1a-980706 (ALSA v0.9.0rc2 emulation code) Sound Fusion CS46xx at 0xf4122000/0xf4000000, irq 11 Audio -- 0: CS46xx (DUPLEX) Synth -- not enabled MIDI -- 0: CS46xx > And via which sound API (OSS/Alsa) and via which sound daemon (arts, > esnd) and how were they launched? My thinkpad 600X seems fine ... > (oss/arts AFAIK). ALSA -- mine was fine too for a while... and fine after a reboot... sounding way too much like M$... > Buchan What I'm driving at is that while most of the previous releases have been relatively stable, 9.0 has not, and I fear for 9.1 if all the testing is done strictly on the current cooker basis where reboots may happen too often to give the new release time to warm up, let alone really "cook"... Pierre
