users October 2005

users@lists.fedoraproject.org

716 participants
1217 discussions

Running KDE on VNC
by Mark Brummett 01 Nov '05

01 Nov '05

I have an issue where, when I have both Gnome and KDE installed as my windows, I would like to select one on or the other. I've gone through several different websites telling me to change some settings in the startup script, with no luck. It always launches Gnome. Here is the configuration logging in with Gnome. #!/bin/sh # Uncomment the following two lines for normal desktop: unset SESSION_MANAGER exec /etc/X11/xinit/xinitrc [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources xsetroot -solid grey vncconfig -iconic & xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" & twm & I've changed the last line to startkde, but no luck. I've done several other things. Thanks for any help in advance. MB

5 6

nvidia or ati ?
by Mihamina Rakotomandimby 01 Nov '05

01 Nov '05

Hi, I am going ti buy a brand new computer, and would like to know if it is better either to have a nVidia or an ATI graphic card. -- Administration & Formation à l'administration de serveurs dédiés: http://www.google.fr/search?q=aspo+infogerance+serveur

28 50

RE: Security, Hacking & Social Engineering Presentation.
by Styma, Robert E (Robert) 01 Nov '05

01 Nov '05

> > The topics I'm going to cover, in no particular order, are: > > - Sniffers > - Viruses > - Port Scanning > - Fingerprinting > - Unnecessary open ports > - Bad software configuration (web servers, databases, mail > servers...) > - SQL injections > - Buffer Overflows > - Use of google as a information gathering tool. > - Firewalls > - DOS attacks > - Brute force attacks > - Cryptography. > - Cross site scripting > - Man-in-the-middle > - Intrusion Detection Systems > - Honeypots > - Identity Spoofing > - Social Engineering > - Gathering information from trash/rubbish > - Physical security in buildings. Access to the building, cable > sniffing, secure ID's... > - And more.... ;-) > With this list of topics, How many days long is this presentation going to be?

11 15

RE: gcc not compiling
by Styma, Robert E (Robert) 31 Oct '05

31 Oct '05

void main(... vs int main(... The standard specifies "int main(...". I agree that what happens with void main becomes compiler dependent. > #include <stdio.h> > void main () { > printf("\nHello World!\n"); > } > $ gcc -o foo foo.c > foo.c: In function `main': > foo.c:2: warning: return type of 'main' is not `int' > $ ./foo In the example, the compiler warning MAY have indicated that it was overriding the void with in. Since the original poster was new coder, best that they learn the approved syntax. int main(int argc, char *argv[]) The syntax: int main(int argc, char **argv) works, but most of the C books I have seen recommend the *argv[] version. Bob Styma

7 7

(no subject)
by mskinnym＠aim.com 31 Oct '05

31 Oct '05

________________________________________________________________________ Check Out the new free AIM(R) Mail -- 2 GB of storage and industry-leading spam and email virus protection.

1 0

Re: Linux killer!
by akonstam＠trinity.edu 31 Oct '05

31 Oct '05

On Mon, Oct 31, 2005 at 03:25:55PM -0500, Claude Jones wrote: > On Monday 31 October 2005 9:25 am, akonstam(a)trinity.edu wrote: > > On Sun, Oct 30, 2005 at 06:33:34PM -0500, Claude Jones wrote: > > > On Sun October 30 2005 9:26 am, akonstam(a)trinity.edu wrote: > > > > > My recipe was pretty simple. I installed mplayer, mplayerplug-in, > > > > > mplayer-gui, some skins, and the all-codecs package from the mplayer > > > > > site. As I recall, I used Synaptic and the atrpms repo to install the > > > > > software, and I downloaded the codecs directly from mplayer's site > > > > > and unpacked them in /usr/lib/win32 - > > > > > > > > What is interesting is that I can't see any of the CNN videos unless I > > > > put the codecs in /usr/local/lib/win32 > > > > > > We must have acquired our packages from different sources. That folder > > > doesn't even exist on my machine... > > > > You create it. > If you have some special reason for responding to me privately, I don't mind, > but in general, I'd prefer you just respond on list. I don't mind public > corrections - I was thinking about one aspect of the issue, and not another > when I wrote the above - but, presumably, if I did it, someone else could as > well. > > I don't really understand why there's such a difference in people's > experiences with mplayer - it's still a bit of a mystery to me. I figured out > a method that worked on two different distros, about 4 months ago; it's been > used on many installations since, and it has always succeeded. Yet, others > seem to be having these problems. > -- There is no significance to my responding to you privately. I just hit reply and the e-mail went were it was supposed to go, I think the note I received came form you personally, not from the list. As to mplayer it comes from different repos and is different evidently. Mine comes form the livna repo. Another machine in out system has mplayer from the grey-sector.repo. The two distributions act differently and have different version numbers for the components. Other mplayer sources no doubt exist. Another variable is that I think the codecs are illegal in the US so they tens to come form sources outside the US. ======================================================================= When some people discover the truth, they just can't understand why everybody isn't eager to hear it. ------------------------------------------- Aaron Konstam Computer Science Trinity University telephone: (210)-999-7484

2 2

Re: Spurious keyboard repeats with Kernel 1532
by Gavin Graham 31 Oct '05

31 Oct '05

Andy Green wrote: >Gavin Graham wrote: >>I logged this as bugzilla #171554 but no one has taken notice of it so I >>want to check if anyone else here has seen this issue. It seems to >>affect nForce-4 chipset MB's. > >Sounds similar to this: >https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=55223 >-Andy >>does 2.6.14 in updates-testing fix the problem?. Comment on the report >>regards >>Rahul Hi All, Still no joy with 2.6.14-1633. I get the same symptoms. Gavin

1 0

up2date failing to connect to RHN
by Steven Stromer 31 Oct '05

31 Oct '05

My RHN up2date icon has suddenly decided to become a greyed out question mark. It is generating the error: Error: <ProtocolError for xmlrpc.rhn.redhat.com/APPLET:502 Proxy Error> I do not run a proxy. I understand that accidentally selecting 'register' when asked may cause the greyed out icon symptom, but I can find no better information than this. If anyone can give assistance, I'd appreciate it! Steven Stromer

3 2

RE: gcc not compiling
by Styma, Robert E (Robert) 31 Oct '05

31 Oct '05

> On Mon, Oct 31, 2005 at 01:30:44PM -0600, STYMA, ROBERT E (ROBERT) wrote: > > The syntax: > > int main(int argc, char **argv) > > works, but most of the C books I have seen recommend > > the *argv[] version. > > I meant to comment that these two different notations are functionally > identical; an array name is nothing more than a pointer. For example, > if we have the following code: > > #include <stdio.h> > void main (void){ > > char foo[] = "This is a string\n"; > char *bar = foo; > > /* these expressions all print "T\n" */ > printf("%c\n", foo[0]); > printf("%c\n", *bar); > printf("%c\n", bar[0]); > printf("%c\n", *foo); > > /* these expressions all print "i\n" */ > printf("%c\n", foo[2]); > printf("%c\n", *(bar + 2)); > printf("%c\n", bar[2]); > printf("%c\n", *(foo + 2)); > } > > The results may surprise programming students: > > $ gcc -o ptr ptr.c > ptr.c: In function `main': > ptr.c:2: warning: return type of 'main' is not `int' > [ddm@archonis ~] > $ ./ptr > T > T > T > T > i > i > i > i > > > In reality, foo[x] is just "syntactic sugar" for *(foo + x). This > is called pointer math, and works properly regardless of the size and > type of foo, so long as it was declared properly before being used. > > [I'm very bored today...] BTW, this is only for the benefit of the original poster. Maybe he will remember this tidbit when the prof gets to parameters and arrays. I agree, char **a, and char *a[] are equivalent. It only a style issue. Students sometimes take this too literally can can get in trouble. The equivalency is really only in parameter passing because arrays are passed as the address of the array. That effectively results in pass by reference instead of pass by value for the array. >From a lecture I used to give (titled: C Gun, Bullet, and Foot): file1.c char external_str[20] = "hello world"; file2.c extern char *external_str; "If you were to link these two files together and then access via the reference in file2.c, the generated code would take the first 4 bytes of the string, assume they were and address, and attempt to go there and get the data. And that would be exactly where your program would go." That last line would always get a chuckle after about 5 seconds. Bob Styma

1 0

Spurious keyboard repeats with Kernel 1532
by Gavin Graham 31 Oct '05

31 Oct '05

Hi, I logged this as bugzilla #171554 but no one has taken notice of it so I want to check if anyone else here has seen this issue. It seems to affect nForce-4 chipset MB's. Description of problem: Since upgrading from 2.6.13-1.1526 to 2.6.13-1.1532, I get random (and long keyboard repeats. The only way to stop this from happening is to turn off the Gnome setting for keybaord repeats. The problem is deeper than this though. After turning off the keyboard repeats,I tried playing an mp3 and the sound was choppy. This has never happened prior to the kernel update. This made my think that something was hogging resources to I started Gnome-System-Monitor and strangely enough, every time I moved a window, the CPU graph would just slip across the screen instead of just scrolling left once per second. It would seem that there is I/O racing issues this kernel. I downgraded back to 2.6.13-1.1526 and all my problems went away!!! This is a heads up that something in that kernel is not right. Version-Release number of selected component (if applicable): Kernel-2.6.13-1.1532 How reproducible: Always Steps to Reproduce: 1. Get yourself a AUSUS A8N-E Motherboard 2. Upgrade to 2.6.13-1.1532 3. Start typing away in GNOME This may affect nForce Motherboards,I dont know as this is the only one I could test on. Actual Results: I/O racing. Bad performance. Expected Results: No Keyboard repeats and normal priority threads.

3 4

← Newer
1
...
6
7
8
9
10
11
12
...
122
Older →

Jump to page: