The backlight, the speed. I wanted a 2000, keyboard, pouch for them and then the fatest flashcard I could buy.... however, my wallet had other ideas! ; )
What I really do dislike about the 120 is the readability. At night I get a sore neck trying to hold it at the right angle with respect to my eyes and the light and in daylight no matter what I did, readability ranged from nil to poor.
Speech recognition was what I was really hoping Apple would perfect in a smallish unit like a Newton. Imagine driving along and then having it take down a message to send via email, a reply to another email which it just read back to you having just received it!
I don't use it much anymore, and wish I could load some ARM Linux onto it! (As long as I could revert back to Newton!) I wish they would open source Newton!!!!
I can't see the page to the Newton dissing, but...
I own an Apple Newton MP120 and I saw the first Newton in action. The simple fact is, that Apple showed this to the World and brought it to market before it was ready, and then, it was too expensive.
However, my MP120 is FAR easier to use than any other stylus input PDA I've ever used, and with the handwriting recognition set to printing (with cursive off), and with a little initial setting up to my style and then a little effort to actually write properly versus my usual chicken scrawl, it gives me 95% acuracy plus.
And, I can write anywhere! Not just some silly little box and char at a time with alien characters.
From my point of view, the Palm is a phenomenon, perhaps the public never got beyond the first bad press of the Newton. I only wish the 120 had a backlight.
BSD popularity inversly proportional to Linux...
on
Is BSD Dying?
·
· Score: 1
Popularity?
I've been using Linux since Red Hat 5.0 was available. Since then I've used it, SuSE, Corel, Mandrake and Debian. I also tried OpenBSD 2.5.
OpenBSD seems so professional, I don't see why it should die out. If FreeBSD and NetBSD is comparable to OpenBSD, then I think they are very quiet acheivers that don't get anywhere near the attention they deserve.
Now, I have settled on Debian and OpenBSD. And I have been buying the official OpenBSD CD's since 2.5 because they really deserve MY support for their efforts and commitment to building a high quality OS bent on awesome security and performance and what's more, I use it!
With all the hype that Linux is getting, and now that it is in reach of geek wanna'bes who probably could'nt install an old Slackware system to save their lives, many suffering from Amiga type syndromes probably don't want to hear that another system that sounds or looks a bit scarey to them, might actually be better in many respects.
My mind is as open as my OSes of choice, I love OpenBSD and Debian and won't get into a dick measuring contest with anyone between the camps because they're both good in their respects.
Many "Stable" Linux distro's tend to have an alpha feel to some of the functions as Linux with all it's hype in the press, seems to get pushed hard to compete with the less stable stuff from Redmond, whereas something like OpenBSD goes for quality before quantity and acheives it with high honours.
They both have their place, and I can't see someone with the passion or ability of Theo de Raadt just up and saying, "ahh fuck it, if ya can't beat em...", because as far as the goals of OpenBSD goes... it can't be beat, especially by some distro like Red Hat.
"With so few genes, it may be the case that the emergent properties of the combinations of genes, as much as the genes themselves, are contributing to our complexity."
Probably the case. Perhaps like binary?
Every additional bit added to a binary number doubles the resolution of that number.
8 bit gives 256 discrete steps, 9 bit gives 512, 16 bit gives 65536, etc.
Perhaps that theory is true. The interaction between different genes giving different effects.
An open source programmer is like a cowboy in the wild west, trying to stake out his claim to some land. He is not conserned with being innovative in this context, but in stealing land from those already present, be it other cowboys or native americans. This is the truth as I see it.
You need glasses then.
As far as owning land goes, only one person or a group of willing people can own a portion of land and do what they like with it. The key is that the land is tangible and they are in agreement.
But with Open Source, the "land" could be concepts or code that overlaps into other areas of interest for many people with similar or different views on what they want from the concept or code, creating relationships between the different camps between hate and admiration. The most important part here is that what they are dealing with is NOT tangible. It is a digital perfect copy of something the creator wishes to give away for freedom for others to enhance for the good of all and possibly even allow the use of for no cost of legal tender. Hell, they usually even allow the charging of legal tender for it by anyone who wishes to do so whilst keeping the code within the same model of sharing.
The point is though, that Open Source allows sharing of concepts and code that does not lessen the value of that code to the original person or group that shared it.
In fact, the sharing makes that concept or code much better due to many others being able to build on it and give back those enhancements to the Open Source community.
Microsoft has a bent view on this, they claim to perceive the concepts and code to be tangible property that once taken, looses value.
It does! It looses value to them if their concepts or code are "stolen".
But Open Source feeds itself. It does not need to steal concepts and code to continue to get better. The way Microsoft has done in the past, with their join us or die practices.
In actual fact, one of the biggest dampeners of software innovation in the World, is Microsoft themselves.
Open Source is the exact opposite and does not need to steal intelectual property from cavemen to succeed. It is on the whole, a pure community of like minded people happily sharing their talents in a completely legal fashion for the good of all.
I was working for a company providing IT products and "solutions" in 1994. It was the typical set up, money hungry arseholes running the company, paying big bucks to fast talking clueless arseholes to market crap products and sometimes good products to the wrong people, every now and then, they'd get it right. Because these products were mostly NEC and Cubix, they had "genuine part numbers", which meant if they were IDE hard drives, CPU's or RAM, they were usually more than twice the price of EXACTLY the same product that could be purchased elsewhere.
Of course, this companies support dept was staffed by geeky kinda guys that really did know their shit, had pride in their work and cared for the customer. Naturally, these people had practically no say in the direction of the company and where not paid anywhere near what the marketting dept was getting.
After numerous customers complaining to me that they were sold products that were "not working" (not appropriate), I could'nt take it any more, I suggested they were given the wrong solutions, suggested appropriate ones and twice suggested where to buy hardware at half our price....
I was fired.
The World seems to be full of loud people of very ordinary ability and few quiet people that really know their stuff who rarely get heard over these arseholes. Bullshit, makes the World go round because it's full of morons who know how to manipulate lesser morons. It seems the gifted can only sit back and watch this bustle of stupidity.
(I'm not suggesting that this reflects anything about NEC or Cubix, we just sold their stuff).
This has nothing to do with a graphical logon screen, this is a graphic that displays very shortly after the kernel boots, making the boot procedure look really cool (see the Matrix theme?).
I've been using the graphical logon screen here and there since Red Hat 5.0, though now I'm a Debian kinda guy.
I was working for a stock exchange in 1997, supporting some systems developers. They were working on year 2000 issues long before the nightly news was proclaiming disaster. They had both production and development systems, on the development systems they could show that the Y2K bug would cause an absolute disaster on the productions systems had the Y2K bugs not been fixed before Y2K.
The over hype helped strike fear into programmers and IT managers that helped to clear the major problems up.
There were real bugs on the day that caused a little trouble, but critical systems received critical attention well before 2000.
If I hear one more "there was no Y2K bug" arsehole...
0.1A to 0.2A through your heart and you're most likely dead.
Students often learn that it is the "current that kills you and not the voltage" and then completely forget to apply ohms law to the risks. Many people forget that you need a high enough voltage to allow a lethal current to flow through a person, given the resistance between the entry and exit points of current flow.
There are so many factors that raise or lower the risk of death. How oily, wet or dry your hands are. If wet, what type of liquid. Will the entry and exit points cause current to flow through your heart, brain or otherwise disrupt or damage your central nervous system or other major organs?
It is an expression and the expression is "you have another thing coming".
It means, you are going to get something but it will not be what you are expecting. It usually implies that what you are going to get will be a rude shock to you and probably quite the opposite of what you want.
I could'nt give a rats arse what that web site states. (hey there's another expression!):)
Besides all this, surely we all knew what inKubus meant, and that is what is important. Are we really here to compare expressions, grammar or spelling in an international forum?
* Ridiculous law passes... Descent hackers that find holes continue to find them, but have no avenue to advertise them... Good, honest IT admins are thus kept in the dark about insecurities in their systems... the general community suffers as malicious hackers continue to do what they do.
* Ridiculous law is seen as it is and does not pass, Descent hackers find holes and alert the World, the IT admins patch the holes on good systems that are easy to patch with timely patches becoming available (read OSS OSes)... those systems continue to become more and more secure, whilst systems based on security by obscurity get worse and worse.
I think as the ammount of energy that manages to get through the skull is irrelevant with the power that the handsets emmit. The only thing it will do is ever so slight heating.
There have been about a zillion studies done on the effects of radiation on animal tissue going way back before I was born, they all find that ionizing radiation can alter tissue enabling cancers and they all fail to find evidence of non-ionizing radiation causing the same.
In my books, this is pretty hard evidence that non-ionizing radiation either does not elevate cancer risk at all or at least if it does, it is unmeasurably low.
Cell phones, microwaves, etc are non-ionizing.
Forget about the "dangers" of mobile phones and concentrate on the real dangers! The giver of all life on Earth, our Sun. Hell the monitor you are looking at now most likely is more dangerous giving out miniscule amounts of X-Rays. And the food we eat is most likely the biggest killer of all (besides all the crazies that smoke, etc).
If they find evidence to the contrary, I might start worrying, for now, it is media blown up hype.
I have contracted for about 6 sites that use Windows NT server from 3.51 to 4.0. Inspite of itself nothing! I watch the memory usage on these servers slowly go up day by day, until they just plain lock or BSOD.
It may take weeks or months, but they crash.
I've been to a few non MCSE NT courses and an MCSE course to appease the bosses, and the subject of out-of-hours reboots always come up. Admins rebooting NT servers on regular out-of-hours basis is a very accepted "administration" task. That seems to be the method of getting long term stability out of NT.
I've had Win9x crash so many times it is now a joke with myself, all my friends and collegues of every workplace I contract for. NT is MUCH better, but still no angel.
Linux and the free BSD's have NEVER EVER crashed on me.
BTW, the contracts I have done include the three.au companies that have the largest WANS in.au. 1-3. They also used Digital Unix and VMS that I never witnessed crash.
My point is not to support Linux by comparing it to DEC Unix and VMS, my point is to enforce the fact that MS may be flashy, but they have yet to show that they are mission critical stable. The fact that Linux *IS* more stable than MS NT I think shows well what a big joke MS really is.
You can't say RH7 is crap, therefore Linux is crap.
MS has never earned the right to be in these farms period.
What about data that is cached? Does Linux immediately write data to disk or cache it? I know also from my 3 years with Linux (RH, Caldera, Mandrake and now Debian) that if I don't unmount my floppy before I eject it, I don't get what I want on that disk.
So if this is the same for fixed disks, I'd be careful with that reset button. You might have egg on your face along with egg on Tux face in the eyes of the ignorant.
If the site is important to the users of the site, then they should remember their passwords.
One day whilst looking for the POSIX utils for NT4 , I found that I could only download them from M$ if I were registered or some such crap.
They had this "give me a clue" type set up, where you would type in your username and it would return the word you specified to be the "clue word" should you forget your password.
Whilst typing in random male and female names, I came across some guy whos clue word was "DEC"...
:)
In like Flynn.
I wanted "touch" for NT as I had some Workstations that were playing up and I found that had last modified file dates that were much older than the created date. M$ POSIX utils touch did'nt help, and they were promptly deleted.
But it was fun to break a security system that was designed for idiots by idiots to support idiotic softwares.
With all the stability troubles friends of mine have had with Cyrix CPU's, I'd rather wait for their Transmeta units. Should run a whole lot cooler too.
http://abcnews.go.com/service/Help/abc_contactus.h tml Fred Moody, needs to consider a few FACTS that he obviously has no idea about: Linux is an open source Kernel. Because it is open source, bugs are found and fixed much easier and quicker. The open source community has nothing to hide. They don't covertly repair bugs THAT NEVER make it onto the Bug Traq list via binary only "service packs". With open source comes open and honest announcements of possible security risks. No hiding behind unreliable i386 binaries hoping security by obscurity gets them through to the next service pack with it's new bugs. Many "vulnerabilities" in Linux are so vaguely considered "dangerous" that it often turns out to be a bit over-hyped and is fixed well before anyone thinks of a good way to exploit it, much less find a system that can be exploited and then carry the exploit out before that bug is fixed within days or hours. But THESE make it onto those lists making Linux look so God awfull in the eyes of the blind. MS runnaway market leader, therefore most bugs is OK? They are the RUNAWAY MARKETING LEADER, that is why they have so many bugs. "Linux is arguably the worst operating-system product in history" Then why the fuck is Hotmail STILL not M$ powered FUCK WIT? This kinda shit makes me see red. I could punch this fuck in the face for being such a stupid arsehole. Here's the tally so far for Microsofts SHIT... I know the following appears to not all be "Microsoft Products", but bear in mind that practically ALL OF IT is built on M$ libraries, being a big contributor to the vulnerabilities... Just for this year Fred... 2000-07-12: Sun Java Web Server Vulnerability 2000-07-11: BB4 Technologies Big Brother Directory Traversal Vulnerability 2000-07-11: NAI VirusScan/NetShield AutoUpgrade Executable Verification Vulnerability 2000-07-11: Microsoft Excel 97 / 2000 Register.ID Vulnerability 2000-07-11: WFTPD Denial of Service Vulnerability 2000-07-11: Microsoft SQL Server Enterprise Manager Password Disclosure Vulnerability 2000-07-10: Blackboard CourseInfo 4.0 Plaintext Administrator Password Vulnerability 2000-07-08: Guild FTPD File Existence Disclosure Vulnerability 2000-07-07: Microsoft SQL Server 7.0 Stored Procedure Vulnerability 2000-07-05: LocalWEB HTTP Buffer Overflow Vulnerability 2000-07-04: Microsoft FrontPage 2000 Server Extensions Path Disclosure Vulnerability 2000-07-04: Microsoft FrontPage 2000 Server Extensions DoS Vulnerability 2000-06-30: Microsoft Windows 2000 Telnet Server DoS Vulnerability 2000-06-30: Microsoft Windows 2000 Remote CPU-overload Vulnerability 2000-06-30: Sybergen Secure Desktop 2.1 Multiple Vulnerabilities 2000-06-30: Sybergen Sygate Denial of Service Vulnerability 2000-06-29: iMesh.Com iMesh 1.02 Buffer Overflow Vulnerability 2000-06-29: Microsoft Windows 9x ARP Spoofing Vulnerability 2000-06-27: Microsoft Internet Explorer 5.01 and Access 2000 / 97 VBA Code Execution Vulnerability 2000-06-27: Floosietek FTGate Mail Server Vulnerability 2000-06-27: Microsoft Internet Explorer 5.01 and Excel/Powerpoint 2000 ActiveX Object Execution Vulnerability 2000-06-27: SapporoWorks WinProxy Buffer Overflow Vulnerability 2000-06-26: Fortech Proxy+ Telnet Gateway Vulnerability 2000-06-25: LeafDigital LeafChat 1.7 DoS Vulnerability 2000-06-24: Microsoft Internet Explorer and Outlook/Outlook Express Remote File Write Vulnerability 2000-06-22: Allaire JRun 2.3.x Sample Files Vulnerability 2000-06-22: NetworkICE BlackICE High UDP Port Block Delay Vulnerability 2000-06-21: BEA Systems WebLogic Server and Express Source Code Disclosure Vulnerability 2000-06-19: Network Associates Net Tools PKI Server 1.0 Buffer Overflow Vulnerability 2000-06-19: Network Associates Net Tools PKI Server 1.0 Unauthenticated Access Vulnerability 2000-06-19: WebBBS Web Server Multiple Buffer Overflow Vulnerability 2000-06-16: Alt-N MDaemon 2.8.5.0 UIDL DoS Vulnerability 2000-06-16: Small HTTP Server Buffer Overflow Vulnerability 2000-06-15: HM Software S to Infinity Multiple Vulnerabilities 2000-06-15: AnalogX SimpleServer WWW 1.05 DoS Vulnerability 2000-06-15: Microsoft Windows 2000 Windows Station Access Vulnerability 2000-06-14: Norton Antivirus for MS Exchange 'Fail-Open' State Vulnerability 2000-06-14: Network Associates PGP Certificate Server Unresolveable IP Address DoS Vulnerability 2000-06-14: Norton Antivirus for MS Exchange Buffer Overflow Vulnerability 2000-06-13: Mindstorm Networks SmartFTP Daemon 0.2 Directory Traversal Vulnerability 2000-06-10: Multiple Vendors HTTP Redirect Java Applet Vulnerability 2000-06-10: Multiple Vendors java.net.URLConnection Applet Direct Connection Vulnerability 2000-06-08: Lilikoi Ceilidh 2.60 Multiple Vulnerabilities 2000-06-08: Multiple Vendor JSP Source Code Disclosure Vulnerability 2000-06-08: Microsoft Windows NT 4.0 Remote Registry Request Dos Vulnerability 2000-06-08: McAfee VirusScan 4.03 Alert File Vulnerability 2000-06-07: Computer Associates eTrust Intrusion Detection System DoS Vulnerability 2000-06-07: i-drive Filo 1.0.0.1 Buffer Overflow Vulnerability 2000-06-07: Computer Associates eTrust Intrusion Detection System Weak Encryption Vulnerability 2000-06-06: Microsoft IE NavigateComplete2 Cross Frame Access Vulnerability 2000-06-06: EType EServ Logging Buffer Overflow Vulnerability 2000-06-05: Microsoft Windows NT 4.0 PDC/BDC Synchonization Reused Keystream Vulnerability 2000-06-05: Microsoft Windows NT 4.0 / 2000 SMB Write Request DoS Vulnerability 2000-06-05: Microsoft Windows NT 4.0 / 2000 Ignored SMB Response DoS Vulnerability 2000-06-05: Microsoft Outlook / Exchange Blank Headers DoS Vulnerability 2000-06-05: Microsoft IE SSL Certificates Vulnerability 2000-06-05: Microsoft Windows NT 4.0 Machine Account Creation Vulnerability 2000-06-04: PassWD 1.2 Weak Encryption Vulnerability 2000-06-01: Multiple Vendor xterm (and derivatives) Denial of Service Vulnerability 2000-06-01: Microsoft Windows 2000 Default 40-bit Encrypted Protected Store Vulnerability 2000-06-01: Sambar Server 4.3 Buffer Overflow Vulnerability 2000-06-01: Concatus IMate Web Mail Server 2.5 Buffer Overflow Vulnerability 2000-05-30: ITHouse Mail Server 1.04 Buffer Overflow Vulnerability 2000-05-30: Microsoft SQL Server DTS Password Disclosure Vulnerability 2000-05-30: Microsoft Media Service DoS Vulnerability 2000-05-30: Microsoft SQL Server 7.0 System Administrator Password Disclosure Vulnerability 2000-05-29: ICQ Web Front Remote DoS Attack Vulnerability 2000-05-25: Omnis Studio 2.4 Weak Database Field Encryption Vulnerability 2000-05-25: Network Associates WebShield SMTP Configuration Modification Vulnerability 2000-05-25: Microsoft Windows NT 4.0 HostAnnouncement DoS Vulnerability 2000-05-25: Network Associates WebShield SMTP 4.5.44 Buffer Overflow Vulnerability 2000-05-25: Microsoft Windows Computer Browser Reset Vulnerability 2000-05-24: Alt-N MDaemon Mail Server DoS Vulnerability 2000-05-24: Pacific Software Carello File Duplication and Source Disclosure Vulnerability 2000-05-24: HP Web JetAdmin Directory Traversal Vulnerability 2000-05-24: HP Web JetAdmin 6.0 Printing DoS Vulnerability 2000-05-24: Rockliffe MailSite 4.2.1.0 Buffer Overflow Vulnerability 2000-05-23: Danware NetOp Remote Control Unauthenticated File Transfer Vulnerability 2000-05-19: Multiple Vendor Fragmented IP Packets DoS Vulnerability 2000-05-19: Nite Server FTPd Multiple DoS Vulnerabilities 2000-05-18: Axent NetProwler Malformed IP Packets DoS Vulnerability 2000-05-18: Lotus Domino Server ESMTP Buffer Overflow Vulnerability 2000-05-17: MS IE ActiveX Combined Component Attributes Vulnerability 2000-05-17: NetworkICE ICECap Manager Default Username and Password Vulnerability 2000-05-17: Microsoft IE DocumentComplete() Cross Frame Access Vulnerability 2000-05-15: Qualcomm Eudora Pro Long Filename Attachment Vulnerability 2000-05-15: Seattle Lab Emurl 2.0 Email Account Access Vulnerability 2000-05-13: Microsoft Active Movie Control Filetype Vulnerability 2000-05-12: Microsoft Outlook 98 / Outlook Express 4.x Long Filename Vulnerability 2000-05-11: NTMail Server 5.x Proxy Access Vulnerability 2000-05-11: Microsoft IIS 4.0/5.0 Malformed Filename Request Vulnerability 2000-05-11: Microsoft IIS 4.0/5.0 Malformed File Extension DoS Vulnerability 2000-05-11: Bugzilla 2.8 Unchecked Existing Bug Report Vulnerability 2000-05-11: Microsoft IE Cookie Disclosure Vulnerability 2000-05-11: Microsoft Office 2000 UA Control Vulnerability 2000-05-11: Microsoft Windows 2000 Default SYSKEY Configuration Vulnerability 2000-05-10: Microsoft IIS 4.0/5.0 Malformed.htr Request Vulnerability 2000-05-09: Microsoft SQL Server Xp_sprintf buffer overflow 2000-05-08: AOL Instant Messenger Path Disclosure Vulnerability 2000-05-06: Microsoft IIS shtml.exe Path Disclosure Vulnerability 2000-05-05: Gossamer Threads DBMan Information Leakage Vulnerability 2000-05-05: Netwin DNews News Server Buffer Overflow Vulnerability 2000-05-04: Netwin Dmailweb Server utoken Buffer Overflow Vulnerability 2000-05-04: InterScan VirusWall uuencoded Filename Buffer Overflow Vulnerability 2000-05-03: id Software Quake3Arena Directory Traversal Vulnerability 2000-05-03: L-Soft Listserv 1.8 Web Archives Buffer Overflow Vulnerability 2000-05-02: FileMaker Pro 5.0 Web Companion Software Multiple Vulnerabilities 2000-05-02: Microsoft Windows 9x NetBIOS NULL Name Vulnerability 2000-05-01: Cassandra NNTPServer v1.10 Buffer Overflow Vulnerability 2000-04-28: Eudora 4.2/4.3 Warning Message Circumvention Vulnerability 2000-04-25: Symantec pcAnywhere Port Scan DoS Vulnerability 2000-04-24: Spectra Container Editor Preview Object Security Vulnerability 2000-04-21: Atrium Software Mercur Mail Server 3.2 Directory Traversal Vulnerability 2000-04-21: Microsoft Windows Long Filename Extension Vulnerability 2000-04-20: Windows NT 4.0 / 2000 cmd.exe Buffer Overflow Vulnerability 2000-04-20: Windows 2000 Active Directory Object Attribute Vulnerability 2000-04-19: MS Frontpage Image Mapper Buffer Overflow Vulnerability 2000-04-19: MS Frontpage htimage.exe File Existence Disclosure Vulnerability 2000-04-19: MS IE 5.01 JSObject Cross-Frame Vulnerability 2000-04-17: Panda Security 3.0 Multiple Vulnerabilities 2000-04-16: Microsoft Internet Explorer for Macintosh getImage and classloader Vulnerabilities 2000-04-16: Microsoft Internet Explorer for Macintosh java.net.URLConnection Vulnerability 2000-04-14: MS IIS FrontPage 98 Extensions Buffer Overflow Vulnerability 2000-04-14: MS IIS FrontPage 98 Extensions Filename Obfuscation Vulnerability 2000-04-12: Microsoft NT 4.0 OffloadModExpo Registry Permissions Vulnerability 2000-04-12: AVM KEN! 1.3.10 Directory Traversal Vulnerability 2000-04-12: Microsoft IIS 4.0/5.0 Escaped Characters Vulnerability 2000-04-10: PCAnywhere Denial of Service Vulnerability 2000-04-06: Symantec pcAnywhere Weak Encryption Vulnerability 2000-04-06: Ipswitch IMail Server 5.x/6.x DoS Vulnerability 2000-04-03: Microsoft Excel XML Vulnerability 2000-04-03: Allaire Forums "rightAccessAllForums" Vulnerability 2000-04-03: Real Networks RealPlayer 6/7 Location Buffer Overflow Vulnerability 2000-03-31: SalesLogix eViewer DoS Vulnerability 2000-03-31: MS Index Server '%20' ASP Source Disclosure Vulnerability 2000-03-30: Microsoft IIS UNC Mapped Virtual Host Vulnerability 2000-03-30: NT / Windows 2000 TCP/IP Printing Service DoS Vulnerability 2000-03-29: ICA Weak Encryption Vulnerability 2000-03-27: GeoCel WindMail Remote File Read Vulnerability 2000-03-25: AnalogX SimpleServer:WWW 1.03 DoS Vulnerability 2000-03-22: Fastraq Mailtraq 1.1.4 Multiple Path Vulnerabilities 2000-03-21: vqSoft vqServer 1.9.9 Plaintext Password Vulnerability 2000-03-21: vqSoft vqServer 1.9.9 Directory Traversal Vulnerability 2000-03-20: Microsoft IIS 4.0 Chunked Transfer Encoding Buffer Overflow Vulnerability 2000-03-17: Norton AntiVirus for Internet Email Gateways Buffer Overflow Vulnerability 2000-03-17: Netscape Enterprise Server Directory Indexing Vulnerability 2000-03-17: Microsoft Windows Media License Manager DoS Vulnerability 2000-03-16: Atrium Software Mercur WebView WebMail-Client Buffer Overflow Vulnerability 2000-03-16: Trend Micro OfficeScan Unauthenticated CGI Usage Vulnerability 2000-03-15: Oracle Web Listener Batch File Vulnerability 2000-03-14: Atrium Software Mercur Mail Server 3.2 Multiple Buffer Overflows Vulnerability 2000-03-14: NT Automated Tasks / Drive Mappings Vulnerability 2000-03-14: Microsoft SQL Weak Password Encryption Vulnerability 2000-03-09: NT User Shell Folders Vulnerability 2000-03-08: Microsoft SQL Server Non-Validated Query Vulnerability 2000-03-08: Microsoft IIS UNC Path Disclosure Vulnerability 2000-03-06: Microsoft Clip Art Buffer Overflow Vulnerability 2000-03-05: Rit Research Labs "The Bat!" X-BAT-FILES Vulnerabilities 2000-03-04: Microsoft Windows 95/98 MS-DOS Device Name DoS Vulnerability 2000-03-01: Realsecure DoS Attack Subversion Vulnerability 2000-03-01: MS IE HTML Help Shortcut Vulnerability 2000-03-01: Realsecure CGI Attack Subversion Vulnerability 2000-02-29: Serv-U FTP Server Path Disclosure Vulnerability 2000-02-28: HP OpenView OmniBack DoS Vulnerability 2000-02-26: Trend Micro OfficeScan DoS Vulnerabilities 2000-02-24: InterAccess TelnetD Server 4.0 Terminal Configuration Vulnerability 2000-02-24: Sambar Server Batch CGI Vulnerability 2000-02-23: Microsoft Windows Media Services Handshake Sequence DoS Vulnerability 2000-02-21: InterAccess TelnetD Server 4.0 Buffer Overflow Vulnerability 2000-02-21: MS Site Server Commerce Edition Input Validation Vulnerability 2000-02-19: Microsoft Signed ActiveX Active Setup Vulnerability 2000-02-18: Microsoft Windows autorun.inf Vulnerability 2000-02-15: Microsoft Windows 2000 Install Unprotected ADMIN$ Share Vulnerability 2000-02-15: Multiple Vendor SNMP World Writeable Community Vulnerability 2000-02-14: ArGoSoft FTP Server 1.0 Multiple Buffer Overflow Vulnerabilities 2000-02-11: Netopia Timbuktu Pro 2.0 DoS Vulnerability 2000-02-10: Internet Anywhere Mail Server Connection Overload Vulnerability 2000-02-10: SNMP Trap Watcher 1.16 DoS Vulnerability 2000-02-10: Internet Anywhere Mail Server RETR DoS Vulnerability 2000-02-09: NT IIS ASP VBScript Runtime Error Viewable Source Vulnerability 2000-02-04: Microsoft Windows Shortcut Vulnerability 2000-02-03: surfCONTROL SuperScout Content Filtering Bypass Vulnerability 2000-02-03: MS Frontpage htimage.exe Path Leak Vulnerability 2000-02-02: NT IIS idq.dll Directory Traversal Vulnerability 2000-02-01: NT LsaQueryInformationPolicy() Domain SID Leak Vulnerability 2000-02-01: Rightfax Webclient Predictable Session Number Vulnerability 2000-02-01: NT Recycle Bin Pre-created Folder Vulnerability 2000-02-01: MS Outlook Express 5 Javascript Email Access Vulnerability 2000-01-31: Allaire Spectra 1.0 invoke.cfm Unauthenticated RAS Access Vulnerability 2000-01-31: Microsoft Java Virtual Machine getSystemResource Vulnerability 2000-01-27: SyGate Non-Authenticated Remote Administration Vulnerability 2000-01-26: NT Index Server Directory Traversal Vulnerability 2000-01-21: NT RDISK Registry Enumeration File Vulnerability 2000-01-20: Microsoft East Asian Word Conversion Vulnerability 2000-01-13: NT LPC Privilege Escalation Vulnerability 2000-01-07: Microsoft Internet Explorer Security Zone Settings Lag Vulnerability 2000-01-05: IMail IMonitor status.cgi DoS Vulnerability 2000-01-04: Microsoft CIS IMAP Buffer Overflow Vulnerability 2000-01-04: Allaire Spectra 1.0 Webtop Vulnerability 2000-01-04: Allaire Spectra Data Indexing DoS Vulnerability MORON
They took multiple shots at very short, regular intervals, just like a real "movie" camera, except instead of these shots coming through one lens that pans around the object, they came through many lenses sequentually.
I was led to beleive it was more than one shot per lens (more than one panning cycle), if so, this is my idea of a movie camera. The frame rate of individual cameras is irrelevent as all the cameras make up the virtual panning camera.
The manual for the handheld GSM Nokia 2110e states, (loosely quoted) "Do not operate phone near head"! No joke. PS. I've read many places that only ionising radiation could cause cancer? Who's research can we believe?
Slashdot Mirror
Oh man how I wanted a 2000!
The backlight, the speed. I wanted a 2000, keyboard, pouch for them and then the fatest flashcard I could buy.... however, my wallet had other ideas! ; )
What I really do dislike about the 120 is the readability. At night I get a sore neck trying to hold it at the right angle with respect to my eyes and the light and in daylight no matter what I did, readability ranged from nil to poor.
Speech recognition was what I was really hoping Apple would perfect in a smallish unit like a Newton. Imagine driving along and then having it take down a message to send via email, a reply to another email which it just read back to you having just received it!
I don't use it much anymore, and wish I could load some ARM Linux onto it! (As long as I could revert back to Newton!) I wish they would open source Newton!!!!
I can't see the page to the Newton dissing, but...
I own an Apple Newton MP120 and I saw the first Newton in action. The simple fact is, that Apple showed this to the World and brought it to market before it was ready, and then, it was too expensive.
However, my MP120 is FAR easier to use than any other stylus input PDA I've ever used, and with the handwriting recognition set to printing (with cursive off), and with a little initial setting up to my style and then a little effort to actually write properly versus my usual chicken scrawl, it gives me 95% acuracy plus.
And, I can write anywhere! Not just some silly little box and char at a time with alien characters.
From my point of view, the Palm is a phenomenon, perhaps the public never got beyond the first bad press of the Newton. I only wish the 120 had a backlight.
Popularity?
I've been using Linux since Red Hat 5.0 was available. Since then I've used it, SuSE, Corel, Mandrake and Debian. I also tried OpenBSD 2.5.
OpenBSD seems so professional, I don't see why it should die out. If FreeBSD and NetBSD is comparable to OpenBSD, then I think they are very quiet acheivers that don't get anywhere near the attention they deserve.
Now, I have settled on Debian and OpenBSD. And I have been buying the official OpenBSD CD's since 2.5 because they really deserve MY support for their efforts and commitment to building a high quality OS bent on awesome security and performance and what's more, I use it!
With all the hype that Linux is getting, and now that it is in reach of geek wanna'bes who probably could'nt install an old Slackware system to save their lives, many suffering from Amiga type syndromes probably don't want to hear that another system that sounds or looks a bit scarey to them, might actually be better in many respects.
My mind is as open as my OSes of choice, I love OpenBSD and Debian and won't get into a dick measuring contest with anyone between the camps because they're both good in their respects.
Many "Stable" Linux distro's tend to have an alpha feel to some of the functions as Linux with all it's hype in the press, seems to get pushed hard to compete with the less stable stuff from Redmond, whereas something like OpenBSD goes for quality before quantity and acheives it with high honours.
They both have their place, and I can't see someone with the passion or ability of Theo de Raadt just up and saying, "ahh fuck it, if ya can't beat em...", because as far as the goals of OpenBSD goes... it can't be beat, especially by some distro like Red Hat.
The BSD's are going nowhere but forward.
"With so few genes, it may be the case that the emergent properties of the combinations of genes, as much as the genes themselves, are contributing to our complexity." Probably the case. Perhaps like binary? Every additional bit added to a binary number doubles the resolution of that number. 8 bit gives 256 discrete steps, 9 bit gives 512, 16 bit gives 65536, etc. Perhaps that theory is true. The interaction between different genes giving different effects.
You need glasses then.
As far as owning land goes, only one person or a group of willing people can own a portion of land and do what they like with it. The key is that the land is tangible and they are in agreement.
But with Open Source, the "land" could be concepts or code that overlaps into other areas of interest for many people with similar or different views on what they want from the concept or code, creating relationships between the different camps between hate and admiration. The most important part here is that what they are dealing with is NOT tangible. It is a digital perfect copy of something the creator wishes to give away for freedom for others to enhance for the good of all and possibly even allow the use of for no cost of legal tender. Hell, they usually even allow the charging of legal tender for it by anyone who wishes to do so whilst keeping the code within the same model of sharing.
The point is though, that Open Source allows sharing of concepts and code that does not lessen the value of that code to the original person or group that shared it.
In fact, the sharing makes that concept or code much better due to many others being able to build on it and give back those enhancements to the Open Source community.
Microsoft has a bent view on this, they claim to perceive the concepts and code to be tangible property that once taken, looses value.
It does! It looses value to them if their concepts or code are "stolen".
But Open Source feeds itself. It does not need to steal concepts and code to continue to get better. The way Microsoft has done in the past, with their join us or die practices.
In actual fact, one of the biggest dampeners of software innovation in the World, is Microsoft themselves.
Open Source is the exact opposite and does not need to steal intelectual property from cavemen to succeed. It is on the whole, a pure community of like minded people happily sharing their talents in a completely legal fashion for the good of all.
He can get rockets, guns and explosives without crypto, so what the hell could stop him getting an OpenBSD CD set?
Does the US media actually beleive that all the Worlds crypto is made in USA?
Banning crypto now is not going to make the CD's and systems of all the "bad guys" just disappear or stop working.
I would'nt be surprised if he had Russian and US crypto hardware at his disposal.
What's he gonna do? "Oh US crypto is a munition again, I better not break any international laws and aquire some!"
Banning crypto will ONLY prevent law abiding people from getting or using it.
I was working for a company providing IT products and "solutions" in 1994. It was the typical set up, money hungry arseholes running the company, paying big bucks to fast talking clueless arseholes to market crap products and sometimes good products to the wrong people, every now and then, they'd get it right. Because these products were mostly NEC and Cubix, they had "genuine part numbers", which meant if they were IDE hard drives, CPU's or RAM, they were usually more than twice the price of EXACTLY the same product that could be purchased elsewhere. Of course, this companies support dept was staffed by geeky kinda guys that really did know their shit, had pride in their work and cared for the customer. Naturally, these people had practically no say in the direction of the company and where not paid anywhere near what the marketting dept was getting. After numerous customers complaining to me that they were sold products that were "not working" (not appropriate), I could'nt take it any more, I suggested they were given the wrong solutions, suggested appropriate ones and twice suggested where to buy hardware at half our price.... I was fired. The World seems to be full of loud people of very ordinary ability and few quiet people that really know their stuff who rarely get heard over these arseholes. Bullshit, makes the World go round because it's full of morons who know how to manipulate lesser morons. It seems the gifted can only sit back and watch this bustle of stupidity. (I'm not suggesting that this reflects anything about NEC or Cubix, we just sold their stuff).
Who cares?
Linux will always have options to suit all.
What OS is "best" for these people that want a comfortable computing experience and why is Linux not suitable or elligible to be made suitable?
This has nothing to do with a graphical logon screen, this is a graphic that displays very shortly after the kernel boots, making the boot procedure look really cool (see the Matrix theme?).
I've been using the graphical logon screen here and there since Red Hat 5.0, though now I'm a Debian kinda guy.
I was working for a stock exchange in 1997, supporting some systems developers. They were working on year 2000 issues long before the nightly news was proclaiming disaster. They had both production and development systems, on the development systems they could show that the Y2K bug would cause an absolute disaster on the productions systems had the Y2K bugs not been fixed before Y2K.
The over hype helped strike fear into programmers and IT managers that helped to clear the major problems up.
There were real bugs on the day that caused a little trouble, but critical systems received critical attention well before 2000.
If I hear one more "there was no Y2K bug" arsehole...
Students often learn that it is the "current that kills you and not the voltage" and then completely forget to apply ohms law to the risks. Many people forget that you need a high enough voltage to allow a lethal current to flow through a person, given the resistance between the entry and exit points of current flow.
There are so many factors that raise or lower the risk of death. How oily, wet or dry your hands are. If wet, what type of liquid. Will the entry and exit points cause current to flow through your heart, brain or otherwise disrupt or damage your central nervous system or other major organs?
http://www.elmwoodelectric.com/fatalcurrent.html
It is an expression and the expression is "you have another thing coming".
:)
It means, you are going to get something but it will not be what you are expecting. It usually implies that what you are going to get will be a rude shock to you and probably quite the opposite of what you want.
I could'nt give a rats arse what that web site states. (hey there's another expression!)
Besides all this, surely we all knew what inKubus meant, and that is what is important. Are we really here to compare expressions, grammar or spelling in an international forum?
Content is what is important.
* Ridiculous law passes... Descent hackers that find holes continue to find them, but have no avenue to advertise them... Good, honest IT admins are thus kept in the dark about insecurities in their systems... the general community suffers as malicious hackers continue to do what they do.
* Ridiculous law is seen as it is and does not pass, Descent hackers find holes and alert the World, the IT admins patch the holes on good systems that are easy to patch with timely patches becoming available (read OSS OSes)... those systems continue to become more and more secure, whilst systems based on security by obscurity get worse and worse.
I think as the ammount of energy that manages to get through the skull is irrelevant with the power that the handsets emmit. The only thing it will do is ever so slight heating.
There have been about a zillion studies done on the effects of radiation on animal tissue going way back before I was born, they all find that ionizing radiation can alter tissue enabling cancers and they all fail to find evidence of non-ionizing radiation causing the same.
In my books, this is pretty hard evidence that non-ionizing radiation either does not elevate cancer risk at all or at least if it does, it is unmeasurably low.
Cell phones, microwaves, etc are non-ionizing.
Forget about the "dangers" of mobile phones and concentrate on the real dangers! The giver of all life on Earth, our Sun. Hell the monitor you are looking at now most likely is more dangerous giving out miniscule amounts of X-Rays. And the food we eat is most likely the biggest killer of all (besides all the crazies that smoke, etc).
If they find evidence to the contrary, I might start worrying, for now, it is media blown up hype.
Have you actually USED Linux?
.au companies that have the largest WANS in .au. 1-3. They also used Digital Unix and VMS that I never witnessed crash.
I have contracted for about 6 sites that use Windows NT server from 3.51 to 4.0. Inspite of itself nothing! I watch the memory usage on these servers slowly go up day by day, until they just plain lock or BSOD.
It may take weeks or months, but they crash.
I've been to a few non MCSE NT courses and an MCSE course to appease the bosses, and the subject of out-of-hours reboots always come up. Admins rebooting NT servers on regular out-of-hours basis is a very accepted "administration" task. That seems to be the method of getting long term stability out of NT.
I've had Win9x crash so many times it is now a joke with myself, all my friends and collegues of every workplace I contract for. NT is MUCH better, but still no angel.
Linux and the free BSD's have NEVER EVER crashed on me.
BTW, the contracts I have done include the three
My point is not to support Linux by comparing it to DEC Unix and VMS, my point is to enforce the fact that MS may be flashy, but they have yet to show that they are mission critical stable. The fact that Linux *IS* more stable than MS NT I think shows well what a big joke MS really is.
You can't say RH7 is crap, therefore Linux is crap.
MS has never earned the right to be in these farms period.
What about data that is cached? Does Linux immediately write data to disk or cache it? I know also from my 3 years with Linux (RH, Caldera, Mandrake and now Debian) that if I don't unmount my floppy before I eject it, I don't get what I want on that disk.
So if this is the same for fixed disks, I'd be careful with that reset button. You might have egg on your face along with egg on Tux face in the eyes of the ignorant.
If the site is important to the users of the site, then they should remember their passwords.
One day whilst looking for the POSIX utils for NT4 , I found that I could only download them from M$ if I were registered or some such crap.
They had this "give me a clue" type set up, where you would type in your username and it would return the word you specified to be the "clue word" should you forget your password.
Whilst typing in random male and female names, I came across some guy whos clue word was "DEC"...
:)
In like Flynn.
I wanted "touch" for NT as I had some Workstations that were playing up and I found that had last modified file dates that were much older than the created date. M$ POSIX utils touch did'nt help, and they were promptly deleted.
But it was fun to break a security system that was designed for idiots by idiots to support idiotic softwares.
http://www.allwell.com.tw/Profile/profile.html
With all the stability troubles friends of mine have had with Cyrix CPU's, I'd rather wait for their Transmeta units. Should run a whole lot cooler too.
Ahhhhhh, Huston... We have a blue screen...
Made a small, single man helicopter more than 10 years ago. A real helo, not a gyro.
Nicely put. So many IT journos I see, are journos first and pretty clueless when it comes to the all important IT bit. Boils my blood.
http://abcnews.go.com/service/Help/abc_contactus.h tml Fred Moody, needs to consider a few FACTS that he obviously has no idea about: Linux is an open source Kernel. Because it is open source, bugs are found and fixed much easier and quicker. The open source community has nothing to hide. They don't covertly repair bugs THAT NEVER make it onto the Bug Traq list via binary only "service packs". With open source comes open and honest announcements of possible security risks. No hiding behind unreliable i386 binaries hoping security by obscurity gets them through to the next service pack with it's new bugs. Many "vulnerabilities" in Linux are so vaguely considered "dangerous" that it often turns out to be a bit over-hyped and is fixed well before anyone thinks of a good way to exploit it, much less find a system that can be exploited and then carry the exploit out before that bug is fixed within days or hours. But THESE make it onto those lists making Linux look so God awfull in the eyes of the blind. MS runnaway market leader, therefore most bugs is OK? They are the RUNAWAY MARKETING LEADER, that is why they have so many bugs. "Linux is arguably the worst operating-system product in history" Then why the fuck is Hotmail STILL not M$ powered FUCK WIT? This kinda shit makes me see red. I could punch this fuck in the face for being such a stupid arsehole. Here's the tally so far for Microsofts SHIT... I know the following appears to not all be "Microsoft Products", but bear in mind that practically ALL OF IT is built on M$ libraries, being a big contributor to the vulnerabilities... Just for this year Fred... 2000-07-12: Sun Java Web Server Vulnerability 2000-07-11: BB4 Technologies Big Brother Directory Traversal Vulnerability 2000-07-11: NAI VirusScan/NetShield AutoUpgrade Executable Verification Vulnerability 2000-07-11: Microsoft Excel 97 / 2000 Register.ID Vulnerability 2000-07-11: WFTPD Denial of Service Vulnerability 2000-07-11: Microsoft SQL Server Enterprise Manager Password Disclosure Vulnerability 2000-07-10: Blackboard CourseInfo 4.0 Plaintext Administrator Password Vulnerability 2000-07-08: Guild FTPD File Existence Disclosure Vulnerability 2000-07-07: Microsoft SQL Server 7.0 Stored Procedure Vulnerability 2000-07-05: LocalWEB HTTP Buffer Overflow Vulnerability 2000-07-04: Microsoft FrontPage 2000 Server Extensions Path Disclosure Vulnerability 2000-07-04: Microsoft FrontPage 2000 Server Extensions DoS Vulnerability 2000-06-30: Microsoft Windows 2000 Telnet Server DoS Vulnerability 2000-06-30: Microsoft Windows 2000 Remote CPU-overload Vulnerability 2000-06-30: Sybergen Secure Desktop 2.1 Multiple Vulnerabilities 2000-06-30: Sybergen Sygate Denial of Service Vulnerability 2000-06-29: iMesh.Com iMesh 1.02 Buffer Overflow Vulnerability 2000-06-29: Microsoft Windows 9x ARP Spoofing Vulnerability 2000-06-27: Microsoft Internet Explorer 5.01 and Access 2000 / 97 VBA Code Execution Vulnerability 2000-06-27: Floosietek FTGate Mail Server Vulnerability 2000-06-27: Microsoft Internet Explorer 5.01 and Excel/Powerpoint 2000 ActiveX Object Execution Vulnerability 2000-06-27: SapporoWorks WinProxy Buffer Overflow Vulnerability 2000-06-26: Fortech Proxy+ Telnet Gateway Vulnerability 2000-06-25: LeafDigital LeafChat 1.7 DoS Vulnerability 2000-06-24: Microsoft Internet Explorer and Outlook/Outlook Express Remote File Write Vulnerability 2000-06-22: Allaire JRun 2.3.x Sample Files Vulnerability 2000-06-22: NetworkICE BlackICE High UDP Port Block Delay Vulnerability 2000-06-21: BEA Systems WebLogic Server and Express Source Code Disclosure Vulnerability 2000-06-19: Network Associates Net Tools PKI Server 1.0 Buffer Overflow Vulnerability 2000-06-19: Network Associates Net Tools PKI Server 1.0 Unauthenticated Access Vulnerability 2000-06-19: WebBBS Web Server Multiple Buffer Overflow Vulnerability 2000-06-16: Alt-N MDaemon 2.8.5.0 UIDL DoS Vulnerability 2000-06-16: Small HTTP Server Buffer Overflow Vulnerability 2000-06-15: HM Software S to Infinity Multiple Vulnerabilities 2000-06-15: AnalogX SimpleServer WWW 1.05 DoS Vulnerability 2000-06-15: Microsoft Windows 2000 Windows Station Access Vulnerability 2000-06-14: Norton Antivirus for MS Exchange 'Fail-Open' State Vulnerability 2000-06-14: Network Associates PGP Certificate Server Unresolveable IP Address DoS Vulnerability 2000-06-14: Norton Antivirus for MS Exchange Buffer Overflow Vulnerability 2000-06-13: Mindstorm Networks SmartFTP Daemon 0.2 Directory Traversal Vulnerability 2000-06-10: Multiple Vendors HTTP Redirect Java Applet Vulnerability 2000-06-10: Multiple Vendors java.net.URLConnection Applet Direct Connection Vulnerability 2000-06-08: Lilikoi Ceilidh 2.60 Multiple Vulnerabilities 2000-06-08: Multiple Vendor JSP Source Code Disclosure Vulnerability 2000-06-08: Microsoft Windows NT 4.0 Remote Registry Request Dos Vulnerability 2000-06-08: McAfee VirusScan 4.03 Alert File Vulnerability 2000-06-07: Computer Associates eTrust Intrusion Detection System DoS Vulnerability 2000-06-07: i-drive Filo 1.0.0.1 Buffer Overflow Vulnerability 2000-06-07: Computer Associates eTrust Intrusion Detection System Weak Encryption Vulnerability 2000-06-06: Microsoft IE NavigateComplete2 Cross Frame Access Vulnerability 2000-06-06: EType EServ Logging Buffer Overflow Vulnerability 2000-06-05: Microsoft Windows NT 4.0 PDC/BDC Synchonization Reused Keystream Vulnerability 2000-06-05: Microsoft Windows NT 4.0 / 2000 SMB Write Request DoS Vulnerability 2000-06-05: Microsoft Windows NT 4.0 / 2000 Ignored SMB Response DoS Vulnerability 2000-06-05: Microsoft Outlook / Exchange Blank Headers DoS Vulnerability 2000-06-05: Microsoft IE SSL Certificates Vulnerability 2000-06-05: Microsoft Windows NT 4.0 Machine Account Creation Vulnerability 2000-06-04: PassWD 1.2 Weak Encryption Vulnerability 2000-06-01: Multiple Vendor xterm (and derivatives) Denial of Service Vulnerability 2000-06-01: Microsoft Windows 2000 Default 40-bit Encrypted Protected Store Vulnerability 2000-06-01: Sambar Server 4.3 Buffer Overflow Vulnerability 2000-06-01: Concatus IMate Web Mail Server 2.5 Buffer Overflow Vulnerability 2000-05-30: ITHouse Mail Server 1.04 Buffer Overflow Vulnerability 2000-05-30: Microsoft SQL Server DTS Password Disclosure Vulnerability 2000-05-30: Microsoft Media Service DoS Vulnerability 2000-05-30: Microsoft SQL Server 7.0 System Administrator Password Disclosure Vulnerability 2000-05-29: ICQ Web Front Remote DoS Attack Vulnerability 2000-05-25: Omnis Studio 2.4 Weak Database Field Encryption Vulnerability 2000-05-25: Network Associates WebShield SMTP Configuration Modification Vulnerability 2000-05-25: Microsoft Windows NT 4.0 HostAnnouncement DoS Vulnerability 2000-05-25: Network Associates WebShield SMTP 4.5.44 Buffer Overflow Vulnerability 2000-05-25: Microsoft Windows Computer Browser Reset Vulnerability 2000-05-24: Alt-N MDaemon Mail Server DoS Vulnerability 2000-05-24: Pacific Software Carello File Duplication and Source Disclosure Vulnerability 2000-05-24: HP Web JetAdmin Directory Traversal Vulnerability 2000-05-24: HP Web JetAdmin 6.0 Printing DoS Vulnerability 2000-05-24: Rockliffe MailSite 4.2.1.0 Buffer Overflow Vulnerability 2000-05-23: Danware NetOp Remote Control Unauthenticated File Transfer Vulnerability 2000-05-19: Multiple Vendor Fragmented IP Packets DoS Vulnerability 2000-05-19: Nite Server FTPd Multiple DoS Vulnerabilities 2000-05-18: Axent NetProwler Malformed IP Packets DoS Vulnerability 2000-05-18: Lotus Domino Server ESMTP Buffer Overflow Vulnerability 2000-05-17: MS IE ActiveX Combined Component Attributes Vulnerability 2000-05-17: NetworkICE ICECap Manager Default Username and Password Vulnerability 2000-05-17: Microsoft IE DocumentComplete() Cross Frame Access Vulnerability 2000-05-15: Qualcomm Eudora Pro Long Filename Attachment Vulnerability 2000-05-15: Seattle Lab Emurl 2.0 Email Account Access Vulnerability 2000-05-13: Microsoft Active Movie Control Filetype Vulnerability 2000-05-12: Microsoft Outlook 98 / Outlook Express 4.x Long Filename Vulnerability 2000-05-11: NTMail Server 5.x Proxy Access Vulnerability 2000-05-11: Microsoft IIS 4.0/5.0 Malformed Filename Request Vulnerability 2000-05-11: Microsoft IIS 4.0/5.0 Malformed File Extension DoS Vulnerability 2000-05-11: Bugzilla 2.8 Unchecked Existing Bug Report Vulnerability 2000-05-11: Microsoft IE Cookie Disclosure Vulnerability 2000-05-11: Microsoft Office 2000 UA Control Vulnerability 2000-05-11: Microsoft Windows 2000 Default SYSKEY Configuration Vulnerability 2000-05-10: Microsoft IIS 4.0/5.0 Malformed .htr Request Vulnerability 2000-05-09: Microsoft SQL Server Xp_sprintf buffer overflow 2000-05-08: AOL Instant Messenger Path Disclosure Vulnerability 2000-05-06: Microsoft IIS shtml.exe Path Disclosure Vulnerability 2000-05-05: Gossamer Threads DBMan Information Leakage Vulnerability 2000-05-05: Netwin DNews News Server Buffer Overflow Vulnerability 2000-05-04: Netwin Dmailweb Server utoken Buffer Overflow Vulnerability 2000-05-04: InterScan VirusWall uuencoded Filename Buffer Overflow Vulnerability 2000-05-03: id Software Quake3Arena Directory Traversal Vulnerability 2000-05-03: L-Soft Listserv 1.8 Web Archives Buffer Overflow Vulnerability 2000-05-02: FileMaker Pro 5.0 Web Companion Software Multiple Vulnerabilities 2000-05-02: Microsoft Windows 9x NetBIOS NULL Name Vulnerability 2000-05-01: Cassandra NNTPServer v1.10 Buffer Overflow Vulnerability 2000-04-28: Eudora 4.2/4.3 Warning Message Circumvention Vulnerability 2000-04-25: Symantec pcAnywhere Port Scan DoS Vulnerability 2000-04-24: Spectra Container Editor Preview Object Security Vulnerability 2000-04-21: Atrium Software Mercur Mail Server 3.2 Directory Traversal Vulnerability 2000-04-21: Microsoft Windows Long Filename Extension Vulnerability 2000-04-20: Windows NT 4.0 / 2000 cmd.exe Buffer Overflow Vulnerability 2000-04-20: Windows 2000 Active Directory Object Attribute Vulnerability 2000-04-19: MS Frontpage Image Mapper Buffer Overflow Vulnerability 2000-04-19: MS Frontpage htimage.exe File Existence Disclosure Vulnerability 2000-04-19: MS IE 5.01 JSObject Cross-Frame Vulnerability 2000-04-17: Panda Security 3.0 Multiple Vulnerabilities 2000-04-16: Microsoft Internet Explorer for Macintosh getImage and classloader Vulnerabilities 2000-04-16: Microsoft Internet Explorer for Macintosh java.net.URLConnection Vulnerability 2000-04-14: MS IIS FrontPage 98 Extensions Buffer Overflow Vulnerability 2000-04-14: MS IIS FrontPage 98 Extensions Filename Obfuscation Vulnerability 2000-04-12: Microsoft NT 4.0 OffloadModExpo Registry Permissions Vulnerability 2000-04-12: AVM KEN! 1.3.10 Directory Traversal Vulnerability 2000-04-12: Microsoft IIS 4.0/5.0 Escaped Characters Vulnerability 2000-04-10: PCAnywhere Denial of Service Vulnerability 2000-04-06: Symantec pcAnywhere Weak Encryption Vulnerability 2000-04-06: Ipswitch IMail Server 5.x/6.x DoS Vulnerability 2000-04-03: Microsoft Excel XML Vulnerability 2000-04-03: Allaire Forums "rightAccessAllForums" Vulnerability 2000-04-03: Real Networks RealPlayer 6/7 Location Buffer Overflow Vulnerability 2000-03-31: SalesLogix eViewer DoS Vulnerability 2000-03-31: MS Index Server '%20' ASP Source Disclosure Vulnerability 2000-03-30: Microsoft IIS UNC Mapped Virtual Host Vulnerability 2000-03-30: NT / Windows 2000 TCP/IP Printing Service DoS Vulnerability 2000-03-29: ICA Weak Encryption Vulnerability 2000-03-27: GeoCel WindMail Remote File Read Vulnerability 2000-03-25: AnalogX SimpleServer:WWW 1.03 DoS Vulnerability 2000-03-22: Fastraq Mailtraq 1.1.4 Multiple Path Vulnerabilities 2000-03-21: vqSoft vqServer 1.9.9 Plaintext Password Vulnerability 2000-03-21: vqSoft vqServer 1.9.9 Directory Traversal Vulnerability 2000-03-20: Microsoft IIS 4.0 Chunked Transfer Encoding Buffer Overflow Vulnerability 2000-03-17: Norton AntiVirus for Internet Email Gateways Buffer Overflow Vulnerability 2000-03-17: Netscape Enterprise Server Directory Indexing Vulnerability 2000-03-17: Microsoft Windows Media License Manager DoS Vulnerability 2000-03-16: Atrium Software Mercur WebView WebMail-Client Buffer Overflow Vulnerability 2000-03-16: Trend Micro OfficeScan Unauthenticated CGI Usage Vulnerability 2000-03-15: Oracle Web Listener Batch File Vulnerability 2000-03-14: Atrium Software Mercur Mail Server 3.2 Multiple Buffer Overflows Vulnerability 2000-03-14: NT Automated Tasks / Drive Mappings Vulnerability 2000-03-14: Microsoft SQL Weak Password Encryption Vulnerability 2000-03-09: NT User Shell Folders Vulnerability 2000-03-08: Microsoft SQL Server Non-Validated Query Vulnerability 2000-03-08: Microsoft IIS UNC Path Disclosure Vulnerability 2000-03-06: Microsoft Clip Art Buffer Overflow Vulnerability 2000-03-05: Rit Research Labs "The Bat!" X-BAT-FILES Vulnerabilities 2000-03-04: Microsoft Windows 95/98 MS-DOS Device Name DoS Vulnerability 2000-03-01: Realsecure DoS Attack Subversion Vulnerability 2000-03-01: MS IE HTML Help Shortcut Vulnerability 2000-03-01: Realsecure CGI Attack Subversion Vulnerability 2000-02-29: Serv-U FTP Server Path Disclosure Vulnerability 2000-02-28: HP OpenView OmniBack DoS Vulnerability 2000-02-26: Trend Micro OfficeScan DoS Vulnerabilities 2000-02-24: InterAccess TelnetD Server 4.0 Terminal Configuration Vulnerability 2000-02-24: Sambar Server Batch CGI Vulnerability 2000-02-23: Microsoft Windows Media Services Handshake Sequence DoS Vulnerability 2000-02-21: InterAccess TelnetD Server 4.0 Buffer Overflow Vulnerability 2000-02-21: MS Site Server Commerce Edition Input Validation Vulnerability 2000-02-19: Microsoft Signed ActiveX Active Setup Vulnerability 2000-02-18: Microsoft Windows autorun.inf Vulnerability 2000-02-15: Microsoft Windows 2000 Install Unprotected ADMIN$ Share Vulnerability 2000-02-15: Multiple Vendor SNMP World Writeable Community Vulnerability 2000-02-14: ArGoSoft FTP Server 1.0 Multiple Buffer Overflow Vulnerabilities 2000-02-11: Netopia Timbuktu Pro 2.0 DoS Vulnerability 2000-02-10: Internet Anywhere Mail Server Connection Overload Vulnerability 2000-02-10: SNMP Trap Watcher 1.16 DoS Vulnerability 2000-02-10: Internet Anywhere Mail Server RETR DoS Vulnerability 2000-02-09: NT IIS ASP VBScript Runtime Error Viewable Source Vulnerability 2000-02-04: Microsoft Windows Shortcut Vulnerability 2000-02-03: surfCONTROL SuperScout Content Filtering Bypass Vulnerability 2000-02-03: MS Frontpage htimage.exe Path Leak Vulnerability 2000-02-02: NT IIS idq.dll Directory Traversal Vulnerability 2000-02-01: NT LsaQueryInformationPolicy() Domain SID Leak Vulnerability 2000-02-01: Rightfax Webclient Predictable Session Number Vulnerability 2000-02-01: NT Recycle Bin Pre-created Folder Vulnerability 2000-02-01: MS Outlook Express 5 Javascript Email Access Vulnerability 2000-01-31: Allaire Spectra 1.0 invoke.cfm Unauthenticated RAS Access Vulnerability 2000-01-31: Microsoft Java Virtual Machine getSystemResource Vulnerability 2000-01-27: SyGate Non-Authenticated Remote Administration Vulnerability 2000-01-26: NT Index Server Directory Traversal Vulnerability 2000-01-21: NT RDISK Registry Enumeration File Vulnerability 2000-01-20: Microsoft East Asian Word Conversion Vulnerability 2000-01-13: NT LPC Privilege Escalation Vulnerability 2000-01-07: Microsoft Internet Explorer Security Zone Settings Lag Vulnerability 2000-01-05: IMail IMonitor status.cgi DoS Vulnerability 2000-01-04: Microsoft CIS IMAP Buffer Overflow Vulnerability 2000-01-04: Allaire Spectra 1.0 Webtop Vulnerability 2000-01-04: Allaire Spectra Data Indexing DoS Vulnerability MORON
I have only seen the making of twice, ages ago and may have assumed incorrectly.
:)
I'm intrigued now.
My info is from the making of.
Define a movie camera.
They took multiple shots at very short, regular intervals, just like a real "movie" camera, except instead of these shots coming through one lens that pans around the object, they came through many lenses sequentually.
I was led to beleive it was more than one shot per lens (more than one panning cycle), if so, this is my idea of a movie camera. The frame rate of individual cameras is irrelevent as all the cameras make up the virtual panning camera.
If it was just one panning cycle, I am wrong.
The manual for the handheld GSM Nokia 2110e states, (loosely quoted) "Do not operate phone near head"! No joke. PS. I've read many places that only ionising radiation could cause cancer? Who's research can we believe?