Mandrake product lifetime
This should interest Mandrake users. The company has published a policy regarding how long they will support each version of Mandrake with security updates. The short answer is that if you have anything earlier than 9.0, you should consider updating. If you have 7.*, it's already not being updated. More details here: http://www.mandrakelinux.com/en/productlifetime.php3 BTW - I read that there should be KDE 3.1 RPMs for Mandrake 9.0 withion a few days. Apparently Mandrake Club members already have access to this. -- Shlomo Solomon http://come.to/shlomo.solomon Sent by KMail (KDE 3.0.5a) on LINUX Mandrake 9.0 To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Mandrake product lifetime
áéåí ùéùé, 7 áôáøåàø 2003, 12:30, shlomo solomon ëúá: > This should interest Mandrake users. The company has published a policy > regarding how long they will support each version of Mandrake with security > updates. The short answer is that if you have anything earlier than 9.0, > you should consider updating. If you have 7.*, it's already not being > updated. More details here: > > http://www.mandrakelinux.com/en/productlifetime.php3 > > > BTW - I read that there should be KDE 3.1 RPMs for Mandrake 9.0 withion a > few days. Apparently Mandrake Club members already have access to this. or you can get other rpms from here: ftp://ftp.ibiblio.org/pub/Linux/distributions/contrib/texstar/linux/distributions/mandrake/9.0/KDE-3.1/ - diego To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Mandrake product lifetime
On Friday 07 February 2003 15:11, Diego Iastrubni wrote: > áéåí ùéùé, 7 áôáøåàø 2003, 12:30, shlomo solomon ëúá: > > BTW - I read that there should be KDE 3.1 RPMs for Mandrake 9.0 withion a > > few days. Apparently Mandrake Club members already have access to this. > > or you can get other rpms from here: > > ftp://ftp.ibiblio.org/pub/Linux/distributions/contrib/texstar/linux/distrib >utions/mandrake/9.0/KDE-3.1/ Here's the README.txt from that URL: These are TEST rpms built on a stock Mandrake 9.0 system. They have not been tested on any other computer but my own. Please use at your own risk. If they blow up your computer dont blame me. I prefer to wait for the **official** RPMs ;-) -- Shlomo Solomon http://come.to/shlomo.solomon Sent by KMail (KDE 3.0.5a) on LINUX Mandrake 9.0 To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: Mandrake product lifetime
On Friday, Feb 7, 2003, at 12:30 Asia/Jerusalem, shlomo solomon wrote: BTW - I read that there should be KDE 3.1 RPMs for Mandrake 9.0 withion a few days. Apparently Mandrake Club members already have access to this. There is an unofficial version already out for some time here: http://ftp.ibiblio.org/pub/Linux/distributions/contrib/texstar/linux/ distributions/mandrake/9.0/KDE-3.1/ worked well for me (mdk 9) = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
xkb handling in upcoming 4.3.0
Looks like keyboard handling in xfree 4.2.99.4 (STB 4.3.0) has changed. Couldn't get it to work the old way using: Option "XkbLayout" "il" Option "XkbOptions" "grp:switch,grp:shift_toggle,grp_led:scroll" and KDE's keyboard applet doesn't work. Got the keyboard layout handling to work using: Option "XkbCompat" "group_led" Option "XkbSymbols" "us(pc104)+il+group(ctrl_shift_toggle)+group(switch)" kxkb is still not working (using kde cvs). -- Meir Kriheli MKsoft systems http://www.mksoft.co.il = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Fwd: Re: OT: PROG question: regarding returning errors in libraries
--- Forwarded message --- From: Voguemaster <[EMAIL PROTECTED]> To: guy keren <[EMAIL PROTECTED]> Subject: Re: OT: PROG question: regarding returning errors in libraries Date: Fri, 07 Feb 2003 15:52:36 +0200 Well, I can only speak from my exprience. When I wrote a mail relay server, I've used a model where each module defines it's functions and the error codes they can generate. For example, the module that handles all TCP related issues contain several wrapper functions and these functions are returning predefined error codes to the calling function. This is part 1 of the error reporting scheme. Part 2 is all about logging errors but i'll get there soon enough. As for the caller, I've implemented a way to take the error code and generate a specific string from it, much like perror does for standard library errors. In addition I've included the optional user string to be added, along with another string that is automatically pre-added that actually represents the function name. The function names are also predefined in my header files and there is a lookup function that returns the function name per ID that you pass to it. Using this I could also write a nice logging mechanism that tells when an error occured (say, a broken pipe when sending data to the TCP socket) or some other condition occured and sends the info either to syslog or to some specific log files. So to sum up, the method I've used is predefined function error codes per function, per module. In addition, function IDs that can be added to the error string that can be generated with a function that behaves much like perror (or GetLastError if you'd like). Thinking back, I might've used a scheme more closely related to exception handling, but for plain C. The only annoying thing with my scheme is that there are literally LOTS of error IDs and you have to be very careful when you assign new ones. You don't want collisions naturally. Also, adding a bunch of functions to a library is also annoying since you need new IDs and add the necessary names to your lookup function etc.. Eli i wonder what people here have to add regarding these models, or regarding other models (again - for the "C" language) they have used, or wanted to try to use. if you comment - please state if you're talking about somehting you used, something you've started using lately, or something you didn't yet use. or if its soemthing you've read about somewhere. and please be fair - i.e. when you describe your magnificent no-problem error reporting system, please also state what are the bad parts of it - where it was annoying, what in it would you improve if you had the time, or if you had an idea how to do, etc. thanks, -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: xkb handling in upcoming 4.3.0
Great, you made my day... On Fri, Feb 07, 2003 at 01:41:12PM +, Meir Kriheli wrote: > Got the keyboard layout handling to work using: > > Option "XkbCompat" "group_led" > Option "XkbSymbols" "us(pc104)+il+group(ctrl_shift_toggle)+group(switch)" This also works for me with cygwin's XWin.exe on Windows 2000. Although xdpyinfo says "XFree86 version: 4.2.0" the group-toggle never work with the other (older) Option-specification. Still the LED remains dark but I think that's because XWin.exe doesn't honor 'Option "Xleds" "1 2 3 4"' yet. Anyway, how did you find this out? All documentation related to the XKEYBOARD extension, which I found so far, was either cryptic or outdated. Thanks, Daniel = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: xkb handling in upcoming 4.3.0
Meir Kriheli wrote: Looks like keyboard handling in xfree 4.2.99.4 (STB 4.3.0) has changed. Couldn't get it to work the old way using: Option "XkbLayout" "il" Option "XkbOptions" "grp:switch,grp:shift_toggle,grp_led:scroll" and KDE's keyboard applet doesn't work. Got the keyboard layout handling to work using: Option "XkbCompat" "group_led" Option "XkbSymbols" "us(pc104)+il+group(ctrl_shift_toggle)+group(switch)" kxkb is still not working (using kde cvs). -- Meir Kriheli MKsoft systems http://www.mksoft.co.il I got it working using setxkbmap --> setxkbmap -option grp:switch,grp:shift_toggle,grp_led:scroll us,il The syntex changed a little, now you must pass "us,il" to setxkbmap because passing only "il" will lock the keyboard to hebrew (how useless). = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: xkb handling in upcoming 4.3.0
Hi U can just change the line Option "XkbLayout" "il" to: Option "XkbLayout" "il,us" work for me. Have a nice day Barak B. On Friday 07 February 2003 13:41, Meir Kriheli wrote: > Looks like keyboard handling in xfree 4.2.99.4 (STB 4.3.0) has changed. > > Couldn't get it to work the old way using: > > Option "XkbLayout" "il" > Option "XkbOptions" "grp:switch,grp:shift_toggle,grp_led:scroll" > > and KDE's keyboard applet doesn't work. > > Got the keyboard layout handling to work using: > > Option "XkbCompat" "group_led" > Option "XkbSymbols" "us(pc104)+il+group(ctrl_shift_toggle)+group(switch)" > > > kxkb is still not working (using kde cvs). > > -- > Meir Kriheli > MKsoft systems > http://www.mksoft.co.il > > = > To unsubscribe, send mail to [EMAIL PROTECTED] with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail [EMAIL PROTECTED] = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: OT: PROG question: regarding returning errors in libraries
On Fri, Feb 07, 2003 at 05:54:38PM +0200, Oleg Goldshmidt wrote: > Interesting topic. Maybe more suitable for hackers-il, as > non-Linux-specific? Maybe we need programming-il? > and __LINE__ (and if you only care about gcc than you can also use > __FUNCTION__) then the trace is easy to follow. __func__ is standard in C99, IIRC. Not supported in older gcc's, though. > .. If you are really adventurous and *really* consistent about naming > stuff you can in principle squeeze it into a macro call like > > VERIFY(foo(bar),rc,CLEAN_UP); > > but I think that would be too clever for your own good, and trades > readability for danger. I use this style ONLY in testing code, where special handling is required for almost every functions that fails. In regular code, it's misleading and prone to error. Also, be very wary of assert(foo(bar) == rc); The entire expression will only be compiled in for debug mode. Unless you never plan to have your code called in non-debug mode, this is a time bomb waiting to happen. > Finally, moving away from C to C++ and the likes, I intuitively > dislike exceptions. I generally feel somewhat uncomfortable about > them, because of their non-locality. It seems to me that it is much > easier to forget to catch something or forget that something deep down > the stack could throw an exception, compared to the explicit return > code. This, however, may be completely baseless and misguided. Java fixes this, FSVO "fix", by adding the exception specification (throws...) to the function's signature. C++ does this as well, except that the default is "throws anything", IIRC, in order to remain compatible with C. Exceptions (and their primitive origins, setjmp/longjmp) are useful when you write a parser or any other input driven engine, and you want to handle all errors deep down in parsing in one place. Returning errors from 5 levels of funtions is cumbersome and error prone (enough for one caller to forget to check the callee's return value and take appropriate action). > Another thing for general purpose library writers: never, under any > circumstances, abort! Always percolate return codes to the Amen! HIH indeed, Muli. -- Muli Ben-Yehuda http://www.mulix.org http://syscalltrack.sf.net = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: xkb handling in upcoming 4.3.0
Am Freitag 07 Februar 2003 20:46 schrieb Barak Bloch: > Hi > U can just change the line > Option "XkbLayout" "il" > to: > Option "XkbLayout" "il,us" > > work for me. Does putting more than two groups work? Like in Option "XkbLayout" "il,us,ru" Regards, Andre. -- == # Andre E. Bar'yudin # # Phone: (972)-54-882-026 ICQ: 48036924 # # Home page: http://www.cs.huji.ac.il/~baryudin/ # == = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: xkb handling in upcoming 4.3.0
On Friday 07 February 2003 15:41 pm, Meir Kriheli wrote: > Looks like keyboard handling in xfree 4.2.99.4 (STB 4.3.0) has changed. > > Couldn't get it to work the old way using: > > Option "XkbLayout" "il" > Option "XkbOptions" "grp:switch,grp:shift_toggle,grp_led:scroll" You should add your primary keyboard, so instead of il, it should be: us, il Thanks, Hetz = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: xkb handling in upcoming 4.3.0
Hetz Ben Hamo wrote: On Friday 07 February 2003 15:41 pm, Meir Kriheli wrote: Looks like keyboard handling in xfree 4.2.99.4 (STB 4.3.0) has changed. Couldn't get it to work the old way using: Option "XkbLayout" "il" Option "XkbOptions" "grp:switch,grp:shift_toggle,grp_led:scroll" You should add your primary keyboard, so instead of il, it should be: us, il Thanks, Hetz Did you, by any chance, have a chance to test Wine's Hebrew support with this new setting? Wine has this annoying habit of translating each character pressed into a virtual key, and then looking it up in the exact same table used for translating into virtual key. This means, however, that any major change to the keyboard layout (such as, for example, removing the QWERTY primary keyboard and being left with just the former secondary IL) will break it's support. Shachar -- Shachar Shemesh Open Source integration consultant http://www.consumer.org.il/sun/ = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: xkb handling in upcoming 4.3.0
> Did you, by any chance, have a chance to test Wine's Hebrew support with > this new setting? Wine has this annoying habit of translating each > character pressed into a virtual key, and then looking it up in the > exact same table used for translating into virtual key. This means, > however, that any major change to the keyboard layout (such as, for > example, removing the QWERTY primary keyboard and being left with just > the former secondary IL) will break it's support. Well, I used XFree pre 4.3.0 in RH 8.1 beta 4 - and I cannot run wine with it (due to the glibc problems, and LD_ASSUME_KERNEL didn't help me much). Thanks, Hetz = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
How to type Hebrew in RedHat 8.0? Hard to RTFM due to broken links
I have installed RedHat 8.0, and I would like to be able to type and read both English and Hebrew. Like a good and nice RTFMer, I surfed to the IGLU FAQ. The question "Where can I find information about Hebrew support in Linux?" in http://www.iglu.org.il/faq/cache/48.html leads to broken links in "HebLocale page" and "Heb-gtk". So can a kind soul, who got Hebrew to work under Gnome, please come up and post a working URL to an HOWTO, which describes what he did? Thanks, --- Omer My opinions, as expressed in this E-mail message, are mine alone. They do not represent the official policy of any organization with which I may be affiliated in any way. WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: How to type Hebrew in RedHat 8.0? Hard to RTFM due to broken links
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Try this one out: http://jem.ascender.com/eitan/ Shabat shalom, Katriel On Friday 07 February 2003 21:24, Omer Zak wrote: > I have installed RedHat 8.0, and I would like to be able to type and read > both English and Hebrew. > Like a good and nice RTFMer, I surfed to the IGLU FAQ. > The question "Where can I find information about Hebrew support in Linux?" > in http://www.iglu.org.il/faq/cache/48.html leads to broken links in > "HebLocale page" and "Heb-gtk". > > So can a kind soul, who got Hebrew to work under Gnome, please come up and > post a working URL to an HOWTO, which describes what he did? > Thanks, > --- Omer > My opinions, as expressed in this E-mail message, are mine alone. > They do not represent the official policy of any organization with which > I may be affiliated in any way. > WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html > > > = > To unsubscribe, send mail to [EMAIL PROTECTED] with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail [EMAIL PROTECTED] - -- +katrielëúøéàì+ pgp key: traum.org.il/gpg.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+REtkDWy+Hv/461sRAvw1AKDG1Fci5YzB/ujSQL8DAMsjFge5dACdEUAD /X9mtkGf+Nxcf8U0s3ozlRg= =5CQu -END PGP SIGNATURE- To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
Re: xkb handling in upcoming 4.3.0
Hetz Ben Hamo wrote: On Friday 07 February 2003 15:41 pm, Meir Kriheli wrote: Looks like keyboard handling in xfree 4.2.99.4 (STB 4.3.0) has changed. Couldn't get it to work the old way using: Option "XkbLayout" "il" Option "XkbOptions" "grp:switch,grp:shift_toggle,grp_led:scroll" You should add your primary keyboard, so instead of il, it should be: us, il Thanks, Hetz Thanks, I'll check it out. BTW, Is it wrong using the other way, which worked for me ? reminder: Option "XkbCompat" "group_led" Option "XkbSymbols" "us(pc104)+il+group(ctrl_shift_toggle)+group(switch)" Cheers -- Meir Kriheli http://mksoft.co.il = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
