This is nothing more than a red herring. If somebody has physical access to your box, then your security has been breached. Passwords aren't going to protect you from having your hard drive removed. An encrypted filesystem, however, will.
Well, they couldn't be exact about it due to the dynamic nature of the database. However, I don't think the estimate is derived directly from the database.
More likely, there is a whole other system which watches pages coming in and increases counters based on keywords, and has a rough idea how the main query engine works.
1. I can't really comment, I've only watched it be installed. I would agree that NetBSD is the hardest, the installer doesn't really seem to flow. Personally I would prefer to just receive a shell when I put the CD in. I can fsck, disklabel, fstab, and untar all by msyelf, thank you very much.
2. OpenBSD and NetBSD are definitely a lot slower than FreeBSD. NetBSD feels a lot less responsive than FreeBSD. Both take much longer to boot. I believe the reason is simply that speed hacks are hard to port and are potentially insecure.
3. My original post was going to address OpenBSD desktops, but I decided not to. Using OpenBSD as a desktop is sort of like using a weed whacker to mow your lawn, then saying "Weed whackers do just fine in any other role!" Maybe so, but there are better solutions available.
4. This wasn't a maintainence thing. As I recall, it was the sshd thing. It got hit right away (as the sshd vulnerability was being announced) by a script which hit all our boxes. The irony is that the FreeBSD boxes were not vulnerable, because of patches to OpenSSH made by the FreeBSD developers. This is actually something of a recurring theme with FreeBSD: major application is vulnerable except for the one shipped with FreeBSD, due to local patches. Personally I trust the network security of FreeBSD better than I do OpenBSD, but I believe it would be easier for a user to break root on a FreeBSD box than an OpenBSD one.
You will want to start with FreeBSD. It is the most general purpose and Linux-like. The installer doesn't hold your hand, but it is easy to get used to. Statistically, you will never go back to Linux. From here you can then try OpenBSD and NetBSD. They are a lot slower and more limited, and are really meant for niche applications. For example, OpenBSD might be a better choice for a firewall.
Amusingly, at my workplace, we run more FreeBSD boxes than OpenBSD, and have never had a FreeBSD box taken. There has been at least one incident involving an OpenBSD box.
Even today, you can still get to a C: prompt under Windows XP, which means a disk operating system is hiding there no matter what Microsoft wants us to believe.
Er, sorry? Creating GUIs in MSVC is a tremendous pain in the ass, only slightly less so if you use MFC or WTL.
One could put together a Notepad clone in under five minutes in Delphi. It would take at least an hour or more in MSVC, writing out MessageProc or DialogProcs and such.
It is worth trying, especially if you fumble around trying to create GUIs in MSVC. If you know what to look for, you can pick out apps written in Delphi pretty easily.
Listen, if my Television was manufactured by NBC, they should not have the power to not carry CBS, ABC, PBS, etc. They should be forced to carry all stations, within reason, that fit the standards.
And why's that? I suppose Windows is also unfairly monopolising the OS market by only running MZs?
-o options A comma-separated string of any of the following options may be specified (with ``no'' prepended as necessary):
packet Use the disk packet (BIOS Int 0x13 extensions) interface, as as opposed to the legacy (CHS) interface, when doing disk I/O. This allows booting above cylinder 1023, but requires specific BIOS support. The default is `nopacket'.
You've only proven my point, by thinking exactly what the compiler has. However, if you follow the code up (it's a bit spaghetti-like, computing the number of columns and stuff) you will see that numrows cannot be zero.
numrows = num / numcols; if (num % numcols) ++numrows;
Because the default/bin/ls is lowest common denominator. As for a waste of time...
[root@visor:/usr/src/bin/ls]/usr/bin/time make Warning: Object directory not changed from original/usr/src/bin/ls cc -O -pipe -DCOLORLS -Wall -Wformat -c cmp.c cc -O -pipe -DCOLORLS -Wall -Wformat -c ls.c cc -O -pipe -DCOLORLS -Wall -Wformat -c print.c print.c: In function `printcol': print.c:253: warning: `base' might be used uninitialized in this function cc -O -pipe -DCOLORLS -Wall -Wformat -c util.c cc -O -pipe -DCOLORLS -Wall -Wformat -static -o ls cmp.o ls.o print.o util.o -lm -ltermcap gzip -cn ls.1 > ls.1.gz 1.59 real 0.35 user 0.12 sys
Slashdot Mirror
Err... more likely, the administrator can access the user's key.
Is it? That sucks. I'd have thought the password would be part of the key.
This is nothing more than a red herring. If somebody has physical access to your box, then your security has been breached. Passwords aren't going to protect you from having your hard drive removed. An encrypted filesystem, however, will.
sh
Slammer_Worm is WICKED SICK!!!!!!
sh
PS. damn lameness filter.
Well, they couldn't be exact about it due to the dynamic nature of the database. However, I don't think the estimate is derived directly from the database.
More likely, there is a whole other system which watches pages coming in and increases counters based on keywords, and has a rough idea how the main query engine works.
sh
1. I can't really comment, I've only watched it be installed. I would agree that NetBSD is the hardest, the installer doesn't really seem to flow. Personally I would prefer to just receive a shell when I put the CD in. I can fsck, disklabel, fstab, and untar all by msyelf, thank you very much.
2. OpenBSD and NetBSD are definitely a lot slower than FreeBSD. NetBSD feels a lot less responsive than FreeBSD. Both take much longer to boot. I believe the reason is simply that speed hacks are hard to port and are potentially insecure.
3. My original post was going to address OpenBSD desktops, but I decided not to. Using OpenBSD as a desktop is sort of like using a weed whacker to mow your lawn, then saying "Weed whackers do just fine in any other role!" Maybe so, but there are better solutions available.
4. This wasn't a maintainence thing. As I recall, it was the sshd thing. It got hit right away (as the sshd vulnerability was being announced) by a script which hit all our boxes. The irony is that the FreeBSD boxes were not vulnerable, because of patches to OpenSSH made by the FreeBSD developers. This is actually something of a recurring theme with FreeBSD: major application is vulnerable except for the one shipped with FreeBSD, due to local patches. Personally I trust the network security of FreeBSD better than I do OpenBSD, but I believe it would be easier for a user to break root on a FreeBSD box than an OpenBSD one.
I enjoyed your sig.
sh
You will want to start with FreeBSD. It is the most general purpose and Linux-like. The installer doesn't hold your hand, but it is easy to get used to. Statistically, you will never go back to Linux. From here you can then try OpenBSD and NetBSD. They are a lot slower and more limited, and are really meant for niche applications. For example, OpenBSD might be a better choice for a firewall.
Amusingly, at my workplace, we run more FreeBSD boxes than OpenBSD, and have never had a FreeBSD box taken. There has been at least one incident involving an OpenBSD box.
sh
I can run cygwin bash, too.
sh
Your penis size is directly proportional to the amount of spam you receive.
sh
Er, sorry? Creating GUIs in MSVC is a tremendous pain in the ass, only slightly less so if you use MFC or WTL.
One could put together a Notepad clone in under five minutes in Delphi. It would take at least an hour or more in MSVC, writing out MessageProc or DialogProcs and such.
sh
It is worth trying, especially if you fumble around trying to create GUIs in MSVC. If you know what to look for, you can pick out apps written in Delphi pretty easily.
I used it primarily for about five years.
sh
I believe he means pixel/vertex shaders and such. There's lots of docs at nvidia's developer site.
sh
Anybody else notice this guy is responsible for at least three fifths of the noise on Slashdot?
sh
I mean like a DX/4, silly-buns. Why've you still got a paperweight like that?
sh
It was possible to convince Quake to run OK on a 486 DX.
I love slagging the build engine as much as the next guy, but it is worthy of mention that it was written by a 17 year old Ken Silverman.
sh
You're missing the point of my question. Why shouldn't the NBC TV only display NBC stations? It's an NBC TV.
sh
And why's that? I suppose Windows is also unfairly monopolising the OS market by only running MZs?
sh
man boot0cfg
sh
Surely you mean, "were bored until they finished Halo"?
sh
Oh, alright then.Those from the Southern US are a lot more likely to pronounce it "sauth".
sh
Not too bright, huh. The joke was intentional.
sh
Dude. How many times am I going to have to follow the code up to explain that that condition is impossible?
sh
You've only proven my point, by thinking exactly what the compiler has. However, if you follow the code up (it's a bit spaghetti-like, computing the number of columns and stuff) you will see that numrows cannot be zero.
sh
Follow the logic:
307: if (f_sortacross)
308: base = 0;
309: for (row = 0; row < numrows; ++row) {
310: endcol = colwidth;
311: if (!f_sortacross)
312: base = row;
It is obvious how a compiler may think base could be used uninitialised, but clearly it never is.
sh
Because the default /bin/ls is lowest common denominator. As for a waste of time...
I can afford the 1.59 seconds.
sh