August 2001 - openSUSE Edu - openSUSE Mailing Lists

icewm
by Paul Sutton 14 Aug '01

14 Aug '01

Hi following recent discussion of icewm, I decided to install on my AMD 500 with 128mb memory, I am currently using rhl 7,1 with the 2.4.2 kernel (i think) optimised for the k6 processor, anyway after installing and typing the starting icewm script (.Xclients) which comes with the online documents, and set this to 755. I can't seem to start by default, at present I can goto failsafe which is a xscreen with an xterm from here I can type icewm. The only problem here is that if I then close the xterm down it kills icewm at the same time, (I know why this is), Can someone please point me in the direction of the file to edit in order to set icewm to default for a normal user, with the login it remembers the last window manager used by a particular user, (for root it can stay as kde), thanks Paul Sutton

2 1

RE: [suse-linux-uk-schools] kde applications
by Ian.lynch2 14 Aug '01

14 Aug '01

>===== Original Message From phil(a)dialsolutions.co.uk ===== >On Monday 13 August 2001 19:56, Michael Brown wrote: > >> KDE applications now start up via kdeinit. KDE utilises a support >> environment which includes the DCOP inter-application communications >> program and the ksycoca configuration cache. These are normally started >> up when KDE itself starts, so KDE applications will launch quickly when >> started from KDE. When you start a KDE application from outside KDE, it >> has to start up the support environment first, which is what is causing >> the added delay under IceWM. > >The trick I'm looking for is probably getting the kde support environment up >and running as the desktop boots so that the KDE apps can take advantage of >Sycoca etc. Anyone know how? > >> As far as magic tricks go, my best recommendation is to use the old, >> small-memory machines as thin-client terminals. This will enable you to >> run virtually whatever applications you want, without worrying about the >> memory footprint. Of course, you will need a thin-client server, but for >> the amount of time you seem to be investing in trimming the memory >> footprint you could buy a thin-client server and pay to have it supported. > >If I can work out how to do this and make the information on how to do it >freely available, I hope that the results of my work will benefit any >interested school. Therefore, I am happy to ignore the fact that we could >have bought a rack full of servers if I'd been charging for my time! > >> Just for reference, on the system that IRL/Fen Systems just put in to >> Woodlands Junior School in Kent, StarOffice starts in around three seconds >> flat. >That's 3 times quicker than my 1200MHz AMD machine does it! Yes I was pleasantly surprised when I first saw it in comparison with my AMD 500 running the Windows version of StarOffice at home. In fact I was so impressed I have junked Windows at home altogether in favour of Linux but unfortunately NTL have not maintained my cable connection since Sunday so I'm on Twigger for my NTL E-mail! And my profile on Windows2ooo has corupted at work so its B*%&^$*y computers. regards, -- IanL

1 0

kde applications
by Phil Driscoll 14 Aug '01

14 Aug '01

On the small (32Mb/200Mhz) machines I am setting up, I would like to be in a position to run KOffice programs. Certainly KWord is becoming a well featured application, and it runs fine in the small memory environment. As you may remember, I am using IceWM in order to reduce the memory overhead of the window manager. Just starting KDE puts me into 12Mb of swap, wheras IceWM leaves me several Mb free/cache. Now to the problem. Although KWord runs ok it takes ages to get going (40 seconds) under IceWM, although if I run it under KDE on the same machine, in spite of the crazy amount of disk sqapping going on, it actually starts up in under 10 seconds. Non-KDE applications, such as AbiWord and Gimp, start up in a couple of seconds regardless of WM. Does anyone know what magic tricks I can perform to effect the speedup under IceWM? Cheers -- Phil Driscoll

3 6

Code Red
by Alex Brett 13 Aug '01

13 Aug '01

I am not good enough with scripts to do this but could someone write a script that can analyse an apache log, and generate a list of all ip addresses that have tried to access default.ida (the way code red infects) - I want to have a list so I can then go to the servers and contact the webmasters and tell them that there system is infected as the UK Tech webserver seems to be getting hit once every minute or so! Anyone got any ideas how to do this? Alex Brett rebuke(a)uktech.eu.org

3 2

Squid & Igear
by Groom, Mike 10 Aug '01

10 Aug '01

Hello from a new correspondent. We need to use Squid with a router which accesses the LEA proxy server. The LEA has a proxy with an authentication process based on IGear software. We need to get squid to allow our (Windows) clients to receive Igear's requests for authentication. At the moment they are blocked by Squid. Does the LEA need to reconfigure Igear for us or can we make some changes locally to Squid to overcome the problem? Has anyone got an answer please. Any advice would be much appreciated. Thanks. Mike Groom Network Support Technician (for schools)

2 1

still receiving mail
by CJC 09 Aug '01

09 Aug '01

just checking!

1 0

Re: Worms
by Paul Munro 04 Aug '01

04 Aug '01

Talking of "worms", my Dell Laptop suffered the Sircam32.exe worm this week! This is quite a nasty one that sits in your registry under HKEY_LOCAL_MACHINE/Software/Sircam and also your Recycle folder, and then sends out itself by using e-mail addresses in your contacts/addresses/inbox--in some cases sending out an attached file from your hard drive (which it did in my case). It sent out 276 e-mails from my machine before I knew anything about it :0 Another good reason to switch my laptop to Linux ;-) Paul

1 0

code red
by Steve Riley 03 Aug '01

03 Aug '01

And as appears to be becoming common to other users, my (Smoothwall) firewall was probed 25 on 2/8 and over thirty times today 3/8. Steve Riley (Nottingham)

1 0

code red
by Phil Driscoll 02 Aug '01

02 Aug '01

In case anyone is interested, I've been reviewing the web logs on my ADSL connected Linux box at home and on my production web server which lives at Legend in Bradford (and is an NT4 box running IIS - although patched up to the eyeballs and not running index server - and also, before anyone comments, will be replaced by a Linux box next week!). My linux box here runs with a packet filter, but has an open port 80 which I need for work. It was attacked 9 times on the 19th July and 35 times in the last day. The figures for the NT box were 24 times on 19th July, and 28 times during the last day. For anyone wanting to check their own weblogs, an attack is characterised by a request for /default.ida with a very long query string. Cheers -- Phil Driscoll

2 1