Re: [expert] Blackdown's jdk in RPM?
Thanks for the tips. I 'll go the tarball way I think. Yet another package that would shine in mandrake, BTW MK Le mer, 22 sep 1999, TA Ruhland a écrit : >Fabien Deschodt wrote: >> >> > Hi! >> > >> > Is there a RPM release of Blackdown's JDK somewhere around? >> > >> >> Yes, on http://rufus.w3.org/linux/RPM/ , but it is only for libc5. >> I had to take the tarball for glibc. >> >Personally, I had some difficulty getting a RPM to work, so went the >tarball route and it installed very easily and has run without any >problems.
[expert] Blackdown's jdk in RPM?
Hi! Is there a RPM release of Blackdown's JDK somewhere around?
Re: [expert] xemacs not reading saved config
I since traced the problem to an error inside the .emacs file, seems that when it encounters such the customization/initialization just dies with an error message and no more parsing. Deleting the old .emacs (from pre-venus times) and starting anew the configuration fixed the thing. Le sam, 18 sep 1999, Mike Fieschko a écrit : >>>> "Max" == Max Klohn <[EMAIL PROTECTED]> writes: > >Max> Hi, Anyone got an idea why xemacs does save its >Max> customizations in an .emacs file, but utterly fails to read >Max> from it when it is started the next time? > >Well, mine does. And if I make changes to .emacs and want the changes >to take effect without closing and restarting xemacs, I use M-x >load-file. thanks for the tip > >What changes to .emacs are you trying? What version xemacs? the one that comes with venus, of course > >Are you certain that changes have been made to .emacs? definitely (btw if you make the same change repeatedly it keeps adding it to the file...) > >It makes a nice mail and news reader, with vm and gnus, respectively. indeed. MK
[expert] xemacs not reading saved config
Hi, Anyone got an idea why xemacs does save its customizations in an .emacs file, but utterly fails to read from it when it is started the next time? MK
[expert] gv issue
Hi, I think there is a stability issue to address with gv, the ghostscript viewer, as distributed in cooker and venus (gv-3.5.8-8mdk). While trying it with the examples given in /usr/share/ghostscript/examples it mostly segfaults. Going back to the red hat (gv-3.5.8-7) improves things, most of the files are viewable. MK
RE: [expert] 6.1 Helios observations -time drifts-
Le jeu, 16 sep 1999, Ken Wilson a écrit : >Time drift is not necessarily a bug but a normal fact of life in >computing. It may be the product of numerous interrupts. The more >processes you have running over a period of time the more opportunities >for interrupts to occur, the greater the time drift. That is why timed >exists, and also utilities that will periodically fetch time from a >reliable source, i.e. the atomic clock in Boulder, and set the current >time for the box holding the timed server and serving the rest of the >network. Well, something definitely "changed" since I upgraded to Mandrake. I never had such wide time drifts with RH 5.2. With 4 weeks uptime, my machine is off by one hour. I dont't know how to further trace the problem. This is why I am asking the list. > >We are getting into way too much bashing. This thread should really be >named '6.1 Helios observations (Bug reports the sequel)'. In deference >to Gael I think we should be 100%, or as close as possible, sure >something is a bug and not just our own error or failure to get up to >speed on a process/problem before reporting same. I am 100% sure of this one. SAME hardware before + the very same daemons running with RH 5.2=no time drifts. I have now three servers up and running and they all drift. I do not whish to purchase a serial interface to a radio clock (which BTW could come more expensive than another distro) until I am resonably convinced this is not a software glitch. I am willing to stick with Mandrake, especially since getting used to a new distro's quirks is somewaht a PITA, as long as I see some issues are being addressed. Now how could I tackle this? I could run a cron job to resynch the clock with the hardware clock, but isn't the whole purpose of the software clock to be supposedly more precise than the hardware one? Any other (better) ideas? > >Maybe we could all drop this thread until we see what the actual release >turns out like. I definitely disagree with this. I think we need answers _before_ the new release if we want it to be better and more stable. Without this, releasing is just riding an ephemere fashion wave. The "distro of the day" kind of users will fade away, what remains, is the quality (or lack thereof) of the fixes & patches. MK
Re: [expert] 6.1 Helios observations
Le mar, 14 sep 1999, Gael Duval a écrit : >Al Smith wrote: >> >> Funny talking about 6.2 and 6.1 isn't even out of the gates yet and 6.0 >> is full of bugs... > >full of bugs? really? I don't see so much excepted the famous "can't >unmount /" at shutdown, which has been fixed. Aw Come on Gael, don't exagerate in the other way... There _are_ still some serious bugs (who wants a server with a time drift for example) that neeed to be addressed. Most people aren't bashing you. Yours isn't a professional answer, you cannot hope to have CUSTOMERS and/or POTENTIAL CUSTOMERS paying for a distro and then tell them something like "sod off" at the first complaint. Very bad policy. > I'd like you guys not to >keep on bashing us like that: it's totally useless and by the way, if >you feel bad with Mandrake, why don't you leave and use another >distribution? > >Greets, > > Gael. >-- >< Gael DUVAL - [EMAIL PROTECTED] > >< Mandrake 6.1beta on http://www.linux-mandrake.com/cassini>
Re: [expert] Why are bugs not fixed ?
Hi all,
Congrats for the distro, guys. I fully adopted it.
Speaking of bugs, I still see very noticeable clock derives in the different
machines I have installed Mandrake 6.0. I am _not_ running timed.
That question was already raised but I haven't seen a definitive fix proposed
Anyone got a solution for that?
Greetings,
Max
Le lun, 13 sep 1999, Patrick Putteman a écrit :
>And I can only add:
>
>Congrats to Gael, Chmoel, and all the others of the Mandrake team... Those
>we hear and those who remain silent...
>
>Great job guys ;o)))
>
>Patrick Putteman
>Internet Support Manager
>Net 7 (Member of the Advalvas Group)
>www.net7.be
>- Original Message -
>From: Gael Duval <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Monday, September 13, 1999 5:56 PM
>Subject: Re: [expert] Why are bugs not fixed ?
>
>
>> Harald Schreiber wrote:
>> >
>> > Axalon Bloodstone <[EMAIL PROTECTED]> writes:
>> > Have a look at
>> > http://www.mail-archive.com/expert@linux-mandrake.com/msg02325.html
>> >
>> > There you can see that I have sent a bug report to this mailing list
>> > regarding missing header files in package inn-devel. The bug
>> > report is dated July, 28th, 1999, nearly six weeks ago.
>> > All I got was a silly answer by Chmouel Boudnah from which I learned
>> > that he is too stupid to read my bug report. By the way,
>> > Red Hat has fixed this problem in RedHat 6.1 Beta (Lorax).
>> >
>> > And have a look at
>> > http://www.linux-mandrake.com/bugs/db/ix/full.html
>> >
>> > As you can see not a single bug report has been resolved in the
>> > last two weeks. I think it is ridiculous to release a new
>> > Distribution within the near future without processing the
>> > bug reports of the users. This is the release policy of
>> > playing kiddies, but not of a serious Linux distributor.
>>
>> Please stop bashing us like that, it's useless - we are currently
>> building all the distribution ("Mandrake based on Red Hat" is totally
>> outdated) and have many projects for the future release. Chmouel and
>> the other programmers here do a great job for the distribution, work
>> 80 hours a week and many packages are better than in other Linux
>> distributions. Making a Linux distribution is a really hard work but
>> we improve everyday, and nevertheless, most bugs are fixed. I believe
>> the 6.1 release will know a great success.
>>
>> Thanx.
>>
>> Gael.
>> --
>> < Gael DUVAL - [EMAIL PROTECTED] >
>> < Mandrake 6.1beta on http://www.linux-mandrake.com/cassini>
>>
Re: [expert] Re: 3dfx device drivers
before the su type xhost local:all to allow x connexions by oher local users MK Le sam, 28 aoû 1999, Brian a écrit : >The reason for it all is that using root login is kinda dangerous .. >this can mess up badly. I want to use my own username on my machine. I >dont play quake yet but i do have a few other 3dfx games i would like to >play without logging in as root . I tried su to root and running the >game that way but it always complains that root has no access to bman's >x display (as well as with any X apps i run while logged in as bman and >su 'd to root in a terminal) > >Xlib: connection to ":0.0" refused by server >Xlib: Invalid MIT-MAGIC-COOKIE-1 key > >Gtk-WARNING **: cannot open display: :0
