You can't make such a gateway - you'd need to know the filenames and cryptographic hashes of every file on the gnutella network, and have to insert each one individually. And that's not a gateway.
This is not a C structure. #pragma is an implementation-defined directive according to ISO/IEC 1999:9899. Moreover, it fails to define CHAR, BYTE, or WORD.
Or the sequence of application of mathematical operations, as defined per axioms, which reduces the opposite of a given statement to a contradiction, is a proof.
- it's dynamically linked and resides in/usr/local/bin,
whereas/bin/ksh and/bin/csh are statically linked
(system rescue issues)
Don't use a shell where it dosen't belong. System recovery should be done by sash. If all your utilities are shared libraries, other shells won't help much.
Use tar/bzip2 - I guarentee you'll see signifigant space savings. This is especially important if you haven't upgraded to those newfangled 20mb drives yet...
What, exactly, is this bug? I remember one a while back where you could ptrace an app that had a saved uid of 0 and keep the trace once it ran seteuid(), is this the same?
Just because you can't figure out how to customize your X window manager doesn't mean we should condemn the kernel that it happens to run on.
Why doesn't it come configured half-decently to begin with?
The programmers aren't mind-readers. They don't know what you want.
If you increases resolution to something reasonable, it's not "screwed up and squished." Plus install your 100-dpi fonts, and you're good to go.
Then why doesn't it come like that -- with the proper resolution and decent fonts?
You chose the resolution - you deal with it. It's one of the questions in the X configuration. And, at least for me, the fonts came with it.
let's imagine two linked slider bars: At one end is complication and Custimzability, at the other end is Simplification and Let-Me-Do-It-For-You.
The thing with this is: Windows lets you have the simplification day-to-day if you're lazy or if you're just not good with computers, and has plenty of customisation and complication available for those who want it. With Linux, it's always complicated, even when it tries to fool you into thinking it should be simple.
Most window managers have a wizard to set the desktop - KDE, for example, can be easily set to mimic windows. If your distro dosen't show you that, use another.
Actually, it could be vulnerable to the slashdot effect - sort of. The freenet distribution comes with (iirc) 100 'seed' nodes. These are exported periodically from the hawk.freenetproject.org node. Your node picks 50 of them and uses them as peers. It soon migrates off the seed nodes and onto other nodes. But those first 50 could well be slashdotted.
Slashdot Mirror
You can't make such a gateway - you'd need to know the filenames and cryptographic hashes of every file on the gnutella network, and have to insert each one individually. And that's not a gateway.
Well, the way I see it its biggest innovations are hashes and UDP. These could be added to the existing gnutella protocol.
#pragma pack(1)
typedef struct
{
CHAR szTag[3];
BYTE nFlags;
WORD nSequence;
BYTE nPart;
BYTE nCount;
} GND_HEADER;
This is not a C structure. #pragma is an implementation-defined directive according to ISO/IEC 1999:9899. Moreover, it fails to define CHAR, BYTE, or WORD.
You can't prove it by induction without proving that for all odd n, if n is prime, then n+1 is prime. You just proved it for a given range.
Or the sequence of application of mathematical operations, as defined per axioms, which reduces the opposite of a given statement to a contradiction, is a proof.
Obligatory karme whore: http://www.math.uchicago.edu/~wald/lit/pi_proof.tx t
Now, really, the Traf-O-Data system didn't need to be that secure. No, really! It's isolated, so what could possibly go wrong? *ducks*
Don't use a shell where it dosen't belong. System recovery should be done by sash. If all your utilities are shared libraries, other shells won't help much.
Already been done. ;)
Uhm - remove either emacs or vi and you'll see 2/3 of your userbase vanish. 1/3 was the fanatics for the editor, 1/3 just left on general principles.
Use tar/bzip2 - I guarentee you'll see signifigant space savings. This is especially important if you haven't upgraded to those newfangled 20mb drives yet...
Uh, it might not be a good idea to contradict someone holding that big of a hammer...
Nearly everyone can find it in 7 tries or less...
Slashdot comments at -1, of course. They're the most reliable source of information on the web!
Aliases don't rewrite Return-Path, From, or Reply-To headers - it goes directly to the sender. Which is usually forged.
Grab a few dozen refs, merge them all. You'll use a mix of each list.
If you don't want to be locked out, subscribe to the list :)
If there is one, it'd have to be installed by one of your users. You can't be sure, but you can't do a clean install each time a patch is released :)
What, exactly, is this bug? I remember one a while back where you could ptrace an app that had a saved uid of 0 and keep the trace once it ran seteuid(), is this the same?
Root has all the priviliges and suid-bits you need for a healthy rootkit.
The programmers aren't mind-readers. They don't know what you want.
You chose the resolution - you deal with it. It's one of the questions in the X configuration. And, at least for me, the fonts came with it.
Most window managers have a wizard to set the desktop - KDE, for example, can be easily set to mimic windows. If your distro dosen't show you that, use another.
Actually, it could be vulnerable to the slashdot effect - sort of. The freenet distribution comes with (iirc) 100 'seed' nodes. These are exported periodically from the hawk.freenetproject.org node. Your node picks 50 of them and uses them as peers. It soon migrates off the seed nodes and onto other nodes. But those first 50 could well be slashdotted.