Re: problem typing hebrew in KDE 2.0

2001-02-12 Thread Aharon Schkolnik
Hi. I am also in the middle of trying to set up Hebrew on RedHat 7.0 with XFree86 4.0.2. Please answer some of my questions so that I may benefit from what you have already accomplished. Also, if in the meantime you have gotten it to work completely, please let me know how. Thanks. > "S

Re: A question about a small "makaf"

2001-02-12 Thread Tzafrir Cohen
On Mon, 12 Feb 2001, Hetz Ben Hamo wrote: > Hi, > > With all the respect, Mati... > > "teaching people" is surely won't help around with this case at all. We still > live in a country that the majority of people use Windows and people blame their > PC that it's not working enough while the actu

Re: problem typing hebrew in KDE 2.0

2001-02-12 Thread Tzafrir Cohen
On Sat, 10 Feb 2001, Hetz Ben Hamo wrote: > Before you run your application, (or you can just set it whether you want > to), add: LANG=iw_IL > > So, if you want to type in hebrew in kedit for example, then do: > > LANG=iw_IL kedit > > Hetz > > > On Saturday 10 February 2001 21:20, Sy Stang

Re: Stupid Bezeq

2001-02-12 Thread Eran Tromer
Gilad Ben-Yossef wrote: > Have anyone noticed, in their hot pursuit of ADSL, how Bezeq in an > obvious ingenious fashion, > chose to make the entire 10.0.0.0/8 A class unusable for mere mortals? There is no need to surrender the whole 10.x.x.x network to the ADSL modem. I have just verified that

Re: kickstart

2001-02-12 Thread Ely Levy
actually I like kickstart much better..:-) you can also check pxe/ghost for fast installing linux kickstart doesn't support any other OS ofcourse bsd has it's own kickstart what exaclly are you trying to do? Ely Levy System group Hebrew University Jerusalem Israel On Sun, 11 Feb 2001, Hetz Be

Re: Stupid Bezeq

2001-02-12 Thread Alex Shnitman
Hi, Schlomo! On Mon, Feb 12, 2001 at 02:52:43PM +0200, you wrote the following: > Well, but the lo network (127.0.0.1) is usually defined with a netmask of > 127.255.255.255 which would break your suggestion. You probably meant netmask 255.0.0.0. But you misread his suggestion. 172.16.0.0/12 is

Re: Stupid Bezeq

2001-02-12 Thread Schlomo Schapiro
Well, but the lo network (127.0.0.1) is usually defined with a netmask of 127.255.255.255 which would break your suggestion. Schlomo On Sun, 11 Feb 2001, Joseph Teichman wrote: > > - Original Message - > From: "Schlomo Schapiro" <[EMAIL PROTECTED]> > To: "Gilad Ben-Yossef" <[EMAIL PROT

Re: A question about a small "makaf"

2001-02-12 Thread matial
In answer to Hetz's note (attached below), I suggest NOT to depart from the standards, for the following reasons: 1) Any hack is likely to help some and harm some. 2) According to the Microsoft NLS person, MS intends to get in line with the standard (Unicode). It will be quite funny if Linux

Re: Stupid Bezeq

2001-02-12 Thread Joseph Teichman
- Original Message - From: "Schlomo Schapiro" <[EMAIL PROTECTED]> To: "Gilad Ben-Yossef" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, February 11, 2001 3:29 PM Subject: Re: Stupid Bezeq > Well, now you know why it is better to pick 192.168.*.* for private > networks, even

Re: Stupid Bezeq

2001-02-12 Thread Dani Arbel
Shlomo, It is a routing problem. If you have a few network interfaces on the router (either eth , ppp, vpn or whatever), and one has the 10.0.0.0/8 assigned to it, none of the other can use ip numbers in that range, or route to other 10 net numbers. Dani On Mon, 12 Feb 2001, Schlomo Schapiro wrot

Re: A question about a small "makaf"

2001-02-12 Thread Hetz Ben Hamo
Hi, With all the respect, Mati... "teaching people" is surely won't help around with this case at all. We still live in a country that the majority of people use Windows and people blame their PC that it's not working enough while the actual problems are at their Windows, and they're PC is perfe