I'm about to get my hands on a few of these NVRs from March Networks. Apparently there are a couple thousand of cameras controlled by these puppies elsewhere in the company. Spoke to a few technical people at March and they seem to know what they are doing. Unrelated to how well the perform, but kind of nice to hear for me as a geek, is that the actual NVR/DVRs are based on an embedded linux distro and can be managed via SSH. Also, they have an Enterprise Security Manager which allows you to authenticate users against external sources like AD, which is nice for an enterprise. I'll be banging on these devices in a couple weeks.
This is precisely why many people have opted to migrate off OpenBSD to other open-source alternatives. Now that pf has been fully integrated into FreeBSD 5.3, I really don't have a compelling reason to use OpenBSD anymore.
I'm not sure how they'll overlay a *story* on the run-n-gun freneticism of an FPS like Doom, but Mexican director Guillermo del Toro from Hellboy, Blade II, and Mimic might have the right gut feel for the horror aspect of the game. He's really into bloodsucking creatures with giant mandibles that don't let go.
This is pointless though, as most script kiddies will launch their latest 31337 spl0it against any host, without bothering to check if its the right OS, or even running the service they are trying to exploit.
I agree in theory, but working at a financial services company with significant investment in Unix, specifically Solaris and HP-UX, the perspective is quite a bit different. This is due to the fact that we have literally _thousands_ of third-party and homegrown apps for various financial systems. Some of these have been written by consultants, contractors, other folks who have since moved on, etc. Without doing proper integration testing, you are fscked, because it becomes almost impossible to know what apps you might impact. So basically, everyone is behind the curve in this area. Like the other poster said, I have no love for MS, but every sysadmin must deal with patching whether they like it or not, and accept the fact that they'll almost always be behind the curve.
CTF is the sole reason to attend Defcon. If you are a security admin responsible for firewalls, VPNs, and most importantly IDS systems, plugging into the CTF network is a fantastic learning experience. Mostly cause its the most malicious traffic you are ever likely to see in one place. Don't bring your work laptop;) I like to start up services on my *nix box, start snort, and see who knocks on my door.
i had been using 2.4.[789] for the past month or two on my stinkpad, and noticed some horrible swappage, especially after the system had been up for several days, with terrible interactive performance. After upgrading to 2.4.13, the problems all seem to have mysteriously vanished -- so I'm glad Linus decided to take the risk with the new VM. Hopefully we can approach something like a stable kernel. sheesh.
I have seen this problem too -- I _need_ NTFS fer chissakes, and 2.4.7 seemed
to work fine. I get the same compilation problem with unistr.c:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.9/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -march=i586 -DNTFS_VERSION=\"1.1.16\" -c -o unistr.o unistr.c
unistr.c: In function `ntfs_collate_names':
unistr.c:99: warning: implicit declaration of function `min'
unistr.c:99: parse error before `unsigned'
unistr.c:99: parse error before `)'
unistr.c:97: warning: `c1' might be used uninitialized in this function
unistr.c: At top level:
unistr.c:118: parse error before `if'
unistr.c:123: warning: type defaults to `int' in declaration of `c1'
unistr.c:123: `name1' undeclared here (not in a function)
unistr.c:123: warning: data definition has no type or storage class
unistr.c:124: parse error before `if'
make[3]: *** [unistr.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.9/fs/ntfs'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.9/fs/ntfs'
make[1]: *** [_subdir_ntfs] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.9/fs'
make: *** [_dir_fs] Error 2
BSD is very much alive and well.
Re: ipfilter licensing, the only regrettable part is that Theo ripped IPF out without having a viable replacement for OpenBSD. I also think that Darren Reed has a right to license HIS code anyway that he damn well pleases. I expect a lot of those folks to. like myself, to switch to FreeBSD for my firewalling needs. What sucks is that used to be able to build a FW/VPN gateway in about 30 minutes with OpenBSD. sigh.
A-fscking-right. OpenBSD's installer is by far the simplest, when my mail/dns server died at work, it took all of 30 minutes from inserting the 2.8 CD to having my system back up and running again. Its a no bull install.
I think all the hubbub about XML-RPC and SOAP
is nice and all.. but as the above poster pointed out, it is a security administrator's nightmare. Unless we as security admins have some way to filter/strip out this info from the HTTP stream, we are going to have a new class of nasty attacks upon us.
I think thats a nifty idea. but the real
question is: does it work with Linux or
*BSD? Probably somebody could hack up the USB filesystem (like used for the support of Sony Cybershot camers under linux)
I second that. Chase works, albeit slowly because
of all the JSP crap. But I can do everything
I need to do without m$.
Oh yeah, Etrade works too!
As someone previously mentioned though, if we had
a browser that didn't suck it would be kinda nice.
I agree. I think this whole KDE/GNOME flamewar
does not contribute anything to evolve X11 desktops for the Unix community and only succeeds in dividing two excellent and innovative groups of developers. I'm sick of hearing this crap, if you want to use GPLed stuff, do so, if you want to use commercial stuff, do so. Just relax people.
Yeah, the book is kinda outdated, but I still
consider it "the book" that really turned me
onto the power of Linux and what I could do
with the system. I haven't looked at the 3rd
edition, but I would recommend it to anyone
who is curious about Linux.
>Firstly, the display screen is on the inside of >the phone when closed. This means that callerID >is useless to you when you answer the phone by >flipping the > case open. Also, while robust when closed, the >damn thing snaps repeatedly when dropped while >open.
Just thought I'd mention that you can change the behavior of "answer when open", so that you can open the phone and preview the number before answering. Its annoying thats not the default.
I'm using the StarTAC ST7760. Very happy with it, call clarity, battery life, tiny size (wear as a pager), etc. As other people have said though, worry about service coverage and quality first, then the phone.
Slashdot Mirror
I'm about to get my hands on a few of these NVRs from March Networks. Apparently there are a couple thousand of cameras controlled by these puppies elsewhere in the company. Spoke to a few technical people at March and they seem to know what they are doing. Unrelated to how well the perform, but kind of nice to hear for me as a geek, is that the actual NVR/DVRs are based on an embedded linux distro and can be managed via SSH. Also, they have an Enterprise Security Manager which allows you to authenticate users against external sources like AD, which is nice for an enterprise. I'll be banging on these devices in a couple weeks.
This is precisely why many people have opted to migrate off OpenBSD to other open-source alternatives. Now that pf has been fully integrated into FreeBSD 5.3, I really don't have a compelling reason to use OpenBSD anymore.
I'm not sure how they'll overlay a *story* on the run-n-gun freneticism of an FPS like Doom, but Mexican director Guillermo del Toro from Hellboy, Blade II, and Mimic might have the right gut feel for the horror aspect of the game. He's really into bloodsucking creatures with giant mandibles that don't let go.
And this is what I got:
Search ErrorMSN Search is temporarily unable to process your request.
Please try again in a few minutes.
EID: f:1658889542 - 1041:1041:10004:1059
HC: 71d61b14
for any project, IT or otherwise: you can only pick any 2 of [cheap|fast|good]. Think about it.
This is pointless though, as most script kiddies will launch their latest 31337 spl0it against any host, without bothering to check if its the right OS, or even running the service they are trying to exploit.
Obscurity != Security
I agree in theory, but working at a financial services company with significant investment in Unix, specifically Solaris and HP-UX, the perspective is quite a bit different. This is due to the fact that we have literally _thousands_ of third-party and homegrown apps for various financial systems. Some of these have been written by consultants, contractors, other folks who have since moved on, etc. Without doing proper integration testing, you are fscked, because it becomes almost impossible to know what apps you might impact. So basically, everyone is behind the curve in this area. Like the other poster said, I have no love for MS, but every sysadmin must deal with patching whether they like it or not, and accept the fact that they'll almost always be behind the curve.
I don't think they've quite finished with breaking it: http://www.securiteam.com/windowsntfocus/5WP0O1P9F A.html
With something like 30-40% of m$ customers still running WinNT, is this responsible corporate citizenship?
CTF is the sole reason to attend Defcon. If you are a security admin responsible for firewalls, VPNs, and most importantly IDS systems, plugging into the CTF network is a fantastic learning experience. Mostly cause its the most malicious traffic you are ever likely to see in one place. Don't bring your work laptop ;) I like to start up services on my *nix box, start snort, and see who knocks on my door.
vmware 3 appears to work on my 2.4.13 machine w/ no problems.
i had been using 2.4.[789] for the past month or two on my stinkpad, and noticed some horrible swappage, especially after the system had been up for several days, with terrible interactive performance. After upgrading to 2.4.13, the problems all seem to have mysteriously vanished -- so I'm glad Linus decided to take the risk with the new VM. Hopefully we can approach something like a stable kernel. sheesh.
I have seen this problem too -- I _need_ NTFS fer chissakes, and 2.4.7 seemed
to work fine. I get the same compilation problem with unistr.c:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.9/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -march=i586 -DNTFS_VERSION=\"1.1.16\" -c -o unistr.o unistr.c
unistr.c: In function `ntfs_collate_names':
unistr.c:99: warning: implicit declaration of function `min'
unistr.c:99: parse error before `unsigned'
unistr.c:99: parse error before `)'
unistr.c:97: warning: `c1' might be used uninitialized in this function
unistr.c: At top level:
unistr.c:118: parse error before `if'
unistr.c:123: warning: type defaults to `int' in declaration of `c1'
unistr.c:123: `name1' undeclared here (not in a function)
unistr.c:123: warning: data definition has no type or storage class
unistr.c:124: parse error before `if'
make[3]: *** [unistr.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.9/fs/ntfs'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.9/fs/ntfs'
make[1]: *** [_subdir_ntfs] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.9/fs'
make: *** [_dir_fs] Error 2
BSD is very much alive and well. Re: ipfilter licensing, the only regrettable part is that Theo ripped IPF out without having a viable replacement for OpenBSD. I also think that Darren Reed has a right to license HIS code anyway that he damn well pleases. I expect a lot of those folks to. like myself, to switch to FreeBSD for my firewalling needs. What sucks is that used to be able to build a FW/VPN gateway in about 30 minutes with OpenBSD. sigh.
A-fscking-right. OpenBSD's installer is by far the simplest, when my mail/dns server died at work, it took all of 30 minutes from inserting the 2.8 CD to having my system back up and running again. Its a no bull install.
I think all the hubbub about XML-RPC and SOAP is nice and all.. but as the above poster pointed out, it is a security administrator's nightmare. Unless we as security admins have some way to filter/strip out this info from the HTTP stream, we are going to have a new class of nasty attacks upon us.
I think thats a nifty idea. but the real question is: does it work with Linux or *BSD? Probably somebody could hack up the USB filesystem (like used for the support of Sony Cybershot camers under linux)
I second that. Chase works, albeit slowly because of all the JSP crap. But I can do everything I need to do without m$. Oh yeah, Etrade works too! As someone previously mentioned though, if we had a browser that didn't suck it would be kinda nice.
I agree. I think this whole KDE/GNOME flamewar does not contribute anything to evolve X11 desktops for the Unix community and only succeeds in dividing two excellent and innovative groups of developers. I'm sick of hearing this crap, if you want to use GPLed stuff, do so, if you want to use commercial stuff, do so. Just relax people.
Yeah, the book is kinda outdated, but I still
consider it "the book" that really turned me
onto the power of Linux and what I could do
with the system. I haven't looked at the 3rd
edition, but I would recommend it to anyone
who is curious about Linux.
>Firstly, the display screen is on the inside of >the phone when closed. This means that callerID >is useless to you when you answer the phone by >flipping the
> case open. Also, while robust when closed, the >damn thing snaps repeatedly when dropped while >open.
Just thought I'd mention that
you can change the behavior of "answer when open",
so that you can open the phone and preview the number before answering. Its annoying thats not
the default.
I'm using the StarTAC ST7760. Very happy with it, call clarity, battery life, tiny size (wear as a pager), etc. As other people have said though, worry about service coverage and quality first, then the phone.