What is your problem? 8 GB hd: less than $USD100. 128 MB of RAM: less than $USD100. I can't see the issue here.
On my dual PPro with 128 MB of RAM and gobs of disk space eaten away from a full SuSE 6.4 install (2.5 GB gone), I find that Nautilus + Netscape + KDE + a few xterms makes Mr Swap nervous, particularly if I don't restart Netscape from time to time.
On my single PIII/800 with 128 MB of RAM, out of the box, 2446 uses 41 MB of RAM. Then I installed Office. On my laptop with 256 MB of RAM as I type this, I'm using 129 MB of RAM, and I have 26 things open, including media player, Outlook, 8 IE windows, and Citrix. The windows directory is using just over 1 GB on disk (about 970 MB in file sizes). The 2 GB gives it some head room to install in and a pagefile.
And in case you're wondering, I haven't had a blue screen yet. It even plays my DVDs and gets me over 4 hours of battery life on my new Dell.
0) ICS and ICF are OPTIONAL. Just in case you missed it: OPTIONAL. So is IPv6, but no one here is whinging about that yet, are they?
1) scriptability; use Windows Scripting Host (easy) or Group Policy (a custom ADM / inf file pair will be needed, but do-able) to change the settings of the personal firewall.
2) The way in which the personal firewall work is very similiar to a number of other personal firewalls, and also the old IP filters present since at least NT 3.51 days. Since that was a hoary ol' chestnut needing much hair on the chest to make work, this is too, and is no worse than using Checkpoint's Fw-1 (which admittedly has a range of protocols and services already pre-defined). There is an effort on to improve things here. If you are a beta 2 user, and you don't like what you see, report it to the.security newsgroup for fixing. My personal beef: no pre-done settings in group policy. It would be easy to make happen. So I've logged the bug, and hopefully it'll get fixed.
Now line up, according to the NDA I have to kill you.
Actually, WinXP Pro and Per both contain multi-user bits, both in terms of how X11 does it, and in the TermServices method. As most of you clueless./ weenies wouldn't have a clue how to make two Xservers work side by side (Ctrl-Alt-F7 / F8 for example), these features are unusual for you guys.
Both Pro and Per allow other users to take control of your desktop using Remote Desktop Connection. This uses RDP, just as TermSrv does
Both Pro and Per use the TermSrv's multiple winstations to have multiple users logged on at once. I've installed software as administrator in one session and read e-mail and surfed the web in another.
The hotkey to go between users and the replacement for SAS is very nice too: Win-L. This allows me to go to the toilet in safety with many fewer keystrokes than before, and even beats the good ol' xlock for non-rodent use.
In addition, NT has always had impersonation. This allows software to run as something else. This is like a more granular version of seteuid(), but nicer and more granular. Most people didn't know about it because it's mainly for programmers. For example, the Server process impersonates you when you connect through ipc$ so that when it tries to do something, it does it with your credentials, not the System's. And unlike Unix, a single process can impersonate many different security principals simulataneously.
For the more Unix like approach to su, such as sudo or priv, in Win2K they gave us some UI and a service to make it easier: runas. Hold down the shift key on a program and use Runas to run as another security principal. This comes through for Pro, but they're busy hiding it in the mom-n-pop Per.
And ever since NT 3.1, services have been running as different users to what you might log in as.
In NT 4.0 reskit, there's a little utility to log in remotely to a command console. This is brought forward in the Win2K reskit. This logs you in without a UI on the remote host, and you can run all your favorite command line tools. Which in NT 4.0 is useless but in Win2K is useful as you can do nearly everything via the cli (the number of cli.exe's jumped from ~80 to over 400). But why you'd want to when you can use MMC on your local box to do ~everything and install the RDP admin service for (1.0 - ~everything), it remains astonishing to me that people would subject themselves to such torture.
All this multi-user stuff works and is very smooth. Now line up, according to the NDA, I have to kill you.
I'm approximately 125 kg and 180 cm tall. By the pictures on your web site, I see that you and I are of similar stature/proportions.
Do you have the same problems that I have with:
People constantly asking when you're going to lose weight?
no appreciable romantic life?
people not seeing past the large husky exterior to the real inner you?
People assuming because you're fat, you're lazy?
JonKatz could do a series on big fat guys, and why we don't get the {ladies,men,CowboyNeal} of our dreams. I'm sure it's just as important as the Hellmouth.:-)
The common criteria are far more than the old orange book controls (B1, B2, C1,...). Part two of ISO 15408 has many things that I'd really like to see (and I'm prepared to help, too).
Why even bother with the old style Orange book stuff, which barely work in a networked environment, when the new style CC definitions are available for free?
Also will you be providing a framework such that deployed TrustedBSD systems are ready for CC evaluation?
Lastly, any plans for a NetBSD version? Want some help?
I deal with Adobe Acrobat documents that are encrypted, use a custom plug-in to prevent printing, and have various anti-copying bits set. It's only a step beyond that to think that Adobe will not take advantage of additional "protections" against copying.
The PDF documents I use cost me $AUD100 per document (they are Australian Standards). I keep them on my hard drive, which is where I first downloaded them. If I lost my hard drive or upgraded my laptop, you can be assured that I will want to protect my investment in these standards by copying/moving them. Any document I can't move or restore is violating my right to fair use.
That is the danger of this proposal. It must be stopped.
I don't care about you napster and divx fans, you suck big time as you rip off the artists you claim you care for and sap bandwidth I need for my daily browsing - I pay for my music and go and see movies when they come out.
But when it comes time to make a stand, this where we draw the line.
HP history and pnm2ppa - from a core developer
on
HP And Bruce Perens
·
· Score: 5
I've asked some of the original protocol developers and they don't have access to the documentation anymore. I've asked some of my friends who work at HP, and their access to the places where this doco is stored came up empty.
I've asked maddog via his Linux International link (of which HP is also a primary sponsor) to talk to HP for us, but never received a reply. He's a busy dude, so I didn't mind too much.
PPA printers are well supported using pnm2ppa 1.0.4. Usuable versions are in most of the distributions now, and we are FreeBSD/NetBSD/BeOS compatible (and for that matter, cygwin and simple to make under Visual C++). I develop under NetBSD on the alpha, and it's 64 bit clean.
About the last thing I'm going to work on is ghostscript integration. We need some help from the ghostscript dudes as we must calibrate our printers, so that should be fun.
PPA printers do use a lot of CPU time. We feed the printer data that is ready for the print head - there is nearly nothing in the three families of PPA printers. The sheer amount of data is uneconomical from the point of view of how fast you can send data down, and the level of compression we can achieve in the protocol is only moderate in comparison to PS or PCL3e (which is what the other HP deskjets use).
I made the posting/. submitter friendly - it's unique to/. - I posted several other places that just accepted the story as is. To get on/. I had to be economical with the truth, supply a link into another slashdot story (more ad revenue) and be seen to be pro-open source. I don't think we'd get published if we didn't do these things. Sorry to be Machiavellian on you, but/. story quality has declined seriously since the days when I first joined.
SAGE-AU have four initial agreements which can be added to your contract. We acknowledge the four we have do not necessarily cover every situation. This is why we have placed it on SourceForge, so it can take on a life of its own.
Microsoft is a huge target for criminals who like to test doors. One of the senior Microsoft security dudes at last year's SAGE-AU conference let us know that there are at least 10,000 port scans, and about 300 more complex attacks conducted against Microsoft every week. The team is made up of about 10-20 people, and they have to provide 24x7 coverage. The triage each attack and deal with those that actually form a real threat to the organisation. They also conduct internal tiger team attacks to ensure they know about the holes before attackers do. Considering they have over 30,000 desktops and associated servers, this is a difficult and immense task. Very few non-finance companies take security this seriously.
They are probably "cracked" on a regular basis, but because you don't hear about it, and so it remains a non-issue. As soon as a little event ends up in the news, this sort of silliness is the result. Hopefully, you'll understand why most companies, including banks, are extremely reluctant to share information with the law enforcement agencies. One simple little attack might take a company's value through the floor because investors don't understand the hoopla surrounding a security incident. You hear about bank holdups all the time, but you'll never hear about real incidents of electronic fraud or Internet banking attacks, even though they occur every day somewhere on the planet.
There are many companies that take a similar risk-managed approach to security. You classify assets based upon their worth to the organisation, and then you protect them to that value. Cracking into the machines that do "download.microsoft.com" is different to cracking into the corporate ERP system or the internal code repositories.
With over 10,000 attacks a week, Microsoft takes a reasonable approach to security, in my opinion. No one can be 100% secure, and it costs so much to be near 100% secure that it's not worth doing so. If you don't agree with me, bite me. Unlike most of you, risk managed security architecture is what I do for a living.
Win2K is my primary win32 operating system. I run all my games on it (Baldurs Gate II, Combat Flight Sim 2, Red Alert 2, Flight Sim 2000, Total Annilihation, Quake 3 (@ 89 fps, 1024x768, 32 bit, everything turned up high)) without a problem. I also do a variety of other things that drive it hard, including compiling, testing, security stuff and so on. The uptime is exemplarly; at home I have had my new Dell on for the month that I've had it without a reboot until I loaded Whistler last night.
Whistler Pro - I turned off moron mode as I found it difficult to live with the new interface, which might be fine for my mum, but useless for me. Remember, this is a Microsoft beta (equivalent to 0.4-0.7 or therabouts in most open source software). When I was beta'ing Win2K, Win2K went from NT 4.0 look with new barely new color schemes and Win98 pop outs in build 1477 through to Win2K's look and feel in about six hundred new builds. Expect Whistler's appearance to change until about April next year.
It seems stable enough. It has ATA-100 support (something that I had to retroactively add to Win2K when I got my Dell) and the screen drivers seem snappy enough. I'm intrigued to find that people are already reporting stuff doesn't work as everything I've tried (including a couple of games) works fine for me. My Logitech USB joystick just worked, and my USB Canon Ixus similarly just worked (in fact, the new features in Whistler for this stuff is just fantastic).
I like the new user "disconnect" feature. It allows multiple users to remain logged on and you can quickly move between them (if you have adequate memory).
I like the way print drivers seem to be kicked out of kernel mode. My 710c never gave me grief in Win2K, but now there's even less chance with Whistler.
Other than that, it's too early to make a full judgement. I've already found one potential security flaw and I have a negative installation experience during the express upgrade, but as I'm a tester and this is a beta, I've told Microsoft about both issues, and they'll fix it, like they did with the six things I found during the three years I tested Win2K. If every one of the "beta" testers did this, the product would be a far better product for it.
No - MCSE's and their ilk are simply there to improve your salary and to move to the top of the lists when ill-qualified HR departments are sorting the wheat from the chaff. My MCSE doubled my salary within 12 months of me getting it. Therefore it's a good thing. The RHCE will come to do this in the Linux^WRedhat world as well.
If you're lucky you might learn something. I taught my NT Workstation course instructor about NT's memory management because he didn't understand it. I also spent most of that week making a mess of other people's boxes (which is trivial because most students don't even change the default administrator password). But the SQL instructor was a very clueful guy. I still occasionally use the MSSQL skills I learnt then when I have to do mysql, Oracle, or Sybase ASE work.
In the Exchange course I managed to play with the Exchange 5.0 key server which I hadn't used before (or since), and that sort of thing can be helpful, as you don't play with all aspects of a product in real life.
Because you're not thinking MIPS per watt and you're not thinking long term.
Intel x86 and x86-compatible CPUs and associated bits n pieces are currently very power hungry. This will change - eventually, but then comes part two of my assertion: ia64.
The first generation of ia64 will not be a handheld or laptop processor for a long time because it is first and foremost a replacement for the Xeon line of processors. But in time, ia64 will become the preferred binary instruction set due to sheer weight of numbers.
Making software portable now, will help both the seamless transition between x86, x86-64 and ia64. Or indeed platforms like my Alpha.
Lastly, a variety of CPU vendors allows for much cheaper CPU's. Do you think that you'd have Celerons for not much money if viable competition did not exist? I don't think so either.
I wish you newbies running slashdot would ask around and remember the old grey beards who were doing "open source" well before you were born.
Linus released Linux in 1991. Berkeley had BSD code out there before 1980. Linus is a late starter to all this.
comp.sources.unix was vibrant at that time, ipso facto, Linus was jumping on the bandwagon. ESR's little manifesto came out in mid-1997, 21 years after Bill Gates accused hobbyists of stealing and demanding a new distribution model for software: paying for it.
Open source is not new. And it predates Linux by a long shot.
I'm sick of it. Libertarians are the fringe of politics and for good reason. Libertarians are NOT the friends of open source, and we would do well to steer clear of them.
Civil society improves the lot of the average peasant. Secular humanism improves the lot of oppressed non-Christians everywhere. Governments are good for society, as it allows society to flourish without fear from random uprisings or internecine civil warfare. An open, democratic society is demonstrably better than being in a despotic state (see Burma) or a lawless state (see Indonesia, a raft of sub-Saharan african nations such). You get one the best forms of democratic state via the use of the Westminster system, where church and state are separated. Examples are the US, England, Australia, and New Zealand. Very similar democracies exist in most European countries as well.
What does libertarians wish? Really dang small government, where the government is cast as the evil doer. The libertarian extremists wish us all to be armed to be teeth to protect ourselves from the nuts next door (as well as the guv'mint) because under their model, there is no government to interfere in their "right" to do whatever they damn well please.
Anyway, if there really was dang small government, there would be really big business. Can you imagine what would happen to what might have been the Internet? It would be expensive (recall Compu$erve). It would be proprietary (recall Compu$erve). Linux wouldn't be anywhere because the government would have let a DCMA style bill pass much before now so IBM's MCA bus would have succeeded, and we would all be paying IBM tax and not Microsoft tax on our new PC's. So remember, libertarians are NOT your friends.
This is all so far from actually doing any coding of any sort that I wish places like slashdot (where it is co-joined all too regularly) would drop these little nuggets of crap in/dev/null where they damn well belong.
We just need enough bandwidth to surf the net and play Total Annilihation without lag. WaveLAN does that for us. We use 40 bit WEP (Silver cards, natch) to prevent all but the most ardent admirers from snooping on us. The fastest link in the house is the 11 Mb/s WaveLAN. The cable modem is about 4.5 Mb/s and the hub is 10 Mb/s. Although we're very well connected here, the entire LAN didn't cost us much money (certainly less than $USD1000 including all five WaveLAN cards). It works well enough for us.
IR has dropout problems. I have problems all the time with my various remotes. I need more IR shiny surfaces to encourage the set top box to change channels more easily.
We play nothing but Total Annilihation here. I'm waiting for the PS2 to come out in Australia, but even then, I might wait for it to come down a little bit before buying into it.
Check out the machine room. Only three Intel's in this picture. The rest are alphas. The little libretto with its lid closed sitting near a keyboard on the desk is the WaveLAN gateway. The cable modem is sitting on the far PC. Guests can use the long cat5 leads on the floor. They go everwhere inside the hours, but for true geekdom, the WaveLAN is for the garden on our lovely sunny days we're having here in sunny Sydney.
Our lounge room with two of the laptops and essential entertainment equipment. Notice no steenking cat 5 for us!
The Android from the Simpsons. The big fat guy who is aka "The Collector" in the Lucy Lawless episode. The guy who runs the comic shop. The guy who gets the medium size star trek utility belt.
* a big fat pipe that everyone pays for (DSL or cable is fine). And I'm not talking about a bucket bong here.
* an agreed administrator for the firewall and internal infrastructure (dhcp, mail relay, etc). This person then gets to choose the One True Operating System(tm) for the firewall and the rest of you can get stuffed. Rotate on a three month basis to reduce friction
* bins a fair way away from the kitchen or dining room (the pizza boxes get gross when people "forget" to take the rubbish out)
* a large fridge to take the booze (this is not optional for Australian-infested geek houses)
* lots of fridge magnets for the pizza menus
* A WaveLAN gateway for resident and itinerant geeks, and lots of long cat5 cables for those who are WaveLAN challenged. Spare WaveLAN cards
* rules on significant others staying more than about three nights a week. Even when everyone in the house is earning more than six figures.
* rules on who buys the next bottle of single malt scotch, cognac, brandy, even *shhudder* bourbon (there's nothing worse than using a marker on a Glenlivet or Glenmorangie)
* Sound padding for the walls when people spank the monkey. Got to have privacy, man.
* A damn fine hifi with a large CD and DVD collection. Most geeks will supply this one without too many problems
* Big ass TV. None of this 34 cm crap. Most geeks disdain TV publically, but are closet watchers. Example, ask who the Android is and why they identify with him. You'll get an answer from 99.99% of all True Geeks(tm).
* Cable or satellite TV with as many channels as the house can afford
* UPS for the machine room. Get an extractor if gets warm like ours does.
Tips for living with a geek
Get a cleaner at least once every two weeks. This works fine for me.
Get a gardener if you have a garden. Geeks do not garden on a regular enough basis. Things will die and overgrow and look messy and you can get evicted.
Work on the chores. Geeks are naturally lazy and refuse to do the dishes if they do the rubbish or vice versa. Don't mention the bathroom
Kick the mess back into the responsible person's bedroom. The shared areas shouldn't be cluttered with people's crap unless it's really geeky and can be used or admired by all.
Pinging fe80::260:1dff:fef6:32b7 with 32 bytes of data:
Reply from fe80::260:1dff:fef6:32b7%7: bytes=32 time=2ms
Reply from fe80::260:1dff:fef6:32b7%7: bytes=32 time=2ms
Reply from fe80::260:1dff:fef6:32b7%7: bytes=32 time=2ms
Reply from fe80::260:1dff:fef6:32b7%7: bytes=32 time=2ms
That's over my WaveLAN wireless PC Card in my Win2K laptop to my flatmate's Libretto C100 running a recent NetBSD-current which is our WaveLAN - LAN gateway. All of our boxes are IPv6 native. No IPv4 encapsulation for us. And yes, WaveLAN kicks ass! You NEED WaveLAN.
So, in answer to one of the major questions, Microsoft's stack works with other IPv6 implementations. It doesn't keep settings between reboots at the moment, and it doesn't do ESP only AH.
I work in the architecture area of a large telco. We have 30,000 desktops to manage. Every time we need a change, the lack of desktop scalability bites us every time.
The registry is per machine. Windows 2000 makes that accessible via the Network, using Group Policy.
Therefore anything that allows administrators to look after a 30,000 desktop change in one to two days is a major win.
For a start, Win2K's kernel bears no resemblance to the DOS kernel. The 16 bit command interpreter is not present.
The registry (as with all other objects, including files, mutexs, memory sections, etc) is protected via the Object Manager, which calls the Security Reference Monitor to check validation.
If the programs have the Win2K logo, they have the correct permissions for TS and use the registry properly (per machine settings go in HKLM and per user settings are in HKCU, which in Win2K hangs out in the Active Directory in a domain environment).
Security is moderately tight, but just like a chmod -R ugo=rwX/* or chown -R nobody.users/* administrators can make the security a whole bunch worse if they DO NOT HAVE A CLUE.
Better not tell the guys doing KDE and Gnome that a single centralized place to do administration is a bad idea. Administrators looking after 30,000 desktops can't work any other way. It's not a flawed architecture - it's the ONLY scalable model to move us forward from the each system is an island in the sea of machines.
Slashdot Mirror
On my dual PPro with 128 MB of RAM and gobs of disk space eaten away from a full SuSE 6.4 install (2.5 GB gone), I find that Nautilus + Netscape + KDE + a few xterms makes Mr Swap nervous, particularly if I don't restart Netscape from time to time.
On my single PIII/800 with 128 MB of RAM, out of the box, 2446 uses 41 MB of RAM. Then I installed Office. On my laptop with 256 MB of RAM as I type this, I'm using 129 MB of RAM, and I have 26 things open, including media player, Outlook, 8 IE windows, and Citrix. The windows directory is using just over 1 GB on disk (about 970 MB in file sizes). The 2 GB gives it some head room to install in and a pagefile. And in case you're wondering, I haven't had a blue screen yet. It even plays my DVDs and gets me over 4 hours of battery life on my new Dell.
0) ICS and ICF are OPTIONAL. Just in case you missed it: OPTIONAL. So is IPv6, but no one here is whinging about that yet, are they?
1) scriptability; use Windows Scripting Host (easy) or Group Policy (a custom ADM / inf file pair will be needed, but do-able) to change the settings of the personal firewall.
2) The way in which the personal firewall work is very similiar to a number of other personal firewalls, and also the old IP filters present since at least NT 3.51 days. Since that was a hoary ol' chestnut needing much hair on the chest to make work, this is too, and is no worse than using Checkpoint's Fw-1 (which admittedly has a range of protocols and services already pre-defined). There is an effort on to improve things here. If you are a beta 2 user, and you don't like what you see, report it to the .security newsgroup for fixing. My personal beef: no pre-done settings in group policy. It would be easy to make happen. So I've logged the bug, and hopefully it'll get fixed.
Now line up, according to the NDA I have to kill you.
Both Pro and Per allow other users to take control of your desktop using Remote Desktop Connection. This uses RDP, just as TermSrv does
Both Pro and Per use the TermSrv's multiple winstations to have multiple users logged on at once. I've installed software as administrator in one session and read e-mail and surfed the web in another.
The hotkey to go between users and the replacement for SAS is very nice too: Win-L. This allows me to go to the toilet in safety with many fewer keystrokes than before, and even beats the good ol' xlock for non-rodent use.
In addition, NT has always had impersonation. This allows software to run as something else. This is like a more granular version of seteuid(), but nicer and more granular. Most people didn't know about it because it's mainly for programmers. For example, the Server process impersonates you when you connect through ipc$ so that when it tries to do something, it does it with your credentials, not the System's. And unlike Unix, a single process can impersonate many different security principals simulataneously.
For the more Unix like approach to su, such as sudo or priv, in Win2K they gave us some UI and a service to make it easier: runas. Hold down the shift key on a program and use Runas to run as another security principal. This comes through for Pro, but they're busy hiding it in the mom-n-pop Per.
And ever since NT 3.1, services have been running as different users to what you might log in as.
In NT 4.0 reskit, there's a little utility to log in remotely to a command console. This is brought forward in the Win2K reskit. This logs you in without a UI on the remote host, and you can run all your favorite command line tools. Which in NT 4.0 is useless but in Win2K is useful as you can do nearly everything via the cli (the number of cli .exe's jumped from ~80 to over 400). But why you'd want to when you can use MMC on your local box to do ~everything and install the RDP admin service for (1.0 - ~everything), it remains astonishing to me that people would subject themselves to such torture.
All this multi-user stuff works and is very smooth. Now line up, according to the NDA, I have to kill you.
Do you have the same problems that I have with:
JonKatz could do a series on big fat guys, and why we don't get the {ladies,men,CowboyNeal} of our dreams. I'm sure it's just as important as the Hellmouth. :-)
I'm, as cucked as a newrt. I've had a few ntognightr5, nd wqriet \franekhy;y I think i SOHGULD N'T Drive.
U;n avnazed I caj do HGTMML on an eZ basis. I'm surpsied I know what a
ius for.
The common criteria are far more than the old orange book controls (B1, B2, C1, ...). Part two of ISO 15408 has many things that I'd really like to see (and I'm prepared to help, too).
Why even bother with the old style Orange book stuff, which barely work in a networked environment, when the new style CC definitions are available for free?
Also will you be providing a framework such that deployed TrustedBSD systems are ready for CC evaluation?
Lastly, any plans for a NetBSD version? Want some help?
The PDF documents I use cost me $AUD100 per document (they are Australian Standards). I keep them on my hard drive, which is where I first downloaded them. If I lost my hard drive or upgraded my laptop, you can be assured that I will want to protect my investment in these standards by copying/moving them. Any document I can't move or restore is violating my right to fair use.
That is the danger of this proposal. It must be stopped.
I don't care about you napster and divx fans, you suck big time as you rip off the artists you claim you care for and sap bandwidth I need for my daily browsing - I pay for my music and go and see movies when they come out.
But when it comes time to make a stand, this where we draw the line.
I've asked some of the original protocol developers and they don't have access to the documentation anymore. I've asked some of my friends who work at HP, and their access to the places where this doco is stored came up empty.
I've asked maddog via his Linux International link (of which HP is also a primary sponsor) to talk to HP for us, but never received a reply. He's a busy dude, so I didn't mind too much.
PPA printers are well supported using pnm2ppa 1.0.4. Usuable versions are in most of the distributions now, and we are FreeBSD/NetBSD/BeOS compatible (and for that matter, cygwin and simple to make under Visual C++). I develop under NetBSD on the alpha, and it's 64 bit clean.
About the last thing I'm going to work on is ghostscript integration. We need some help from the ghostscript dudes as we must calibrate our printers, so that should be fun.
PPA printers do use a lot of CPU time. We feed the printer data that is ready for the print head - there is nearly nothing in the three families of PPA printers. The sheer amount of data is uneconomical from the point of view of how fast you can send data down, and the level of compression we can achieve in the protocol is only moderate in comparison to PS or PCL3e (which is what the other HP deskjets use).
I made the posting /. submitter friendly - it's unique to /. - I posted several other places that just accepted the story as is. To get on /. I had to be economical with the truth, supply a link into another slashdot story (more ad revenue) and be seen to be pro-open source. I don't think we'd get published if we didn't do these things. Sorry to be Machiavellian on you, but /. story quality has declined seriously since the days when I first joined.
SAGE-AU have four initial agreements which can be added to your contract. We acknowledge the four we have do not necessarily cover every situation. This is why we have placed it on SourceForge, so it can take on a life of its own.
They are probably "cracked" on a regular basis, but because you don't hear about it, and so it remains a non-issue. As soon as a little event ends up in the news, this sort of silliness is the result. Hopefully, you'll understand why most companies, including banks, are extremely reluctant to share information with the law enforcement agencies. One simple little attack might take a company's value through the floor because investors don't understand the hoopla surrounding a security incident. You hear about bank holdups all the time, but you'll never hear about real incidents of electronic fraud or Internet banking attacks, even though they occur every day somewhere on the planet.
There are many companies that take a similar risk-managed approach to security. You classify assets based upon their worth to the organisation, and then you protect them to that value. Cracking into the machines that do "download.microsoft.com" is different to cracking into the corporate ERP system or the internal code repositories.
With over 10,000 attacks a week, Microsoft takes a reasonable approach to security, in my opinion. No one can be 100% secure, and it costs so much to be near 100% secure that it's not worth doing so. If you don't agree with me, bite me. Unlike most of you, risk managed security architecture is what I do for a living.
Whistler Pro - I turned off moron mode as I found it difficult to live with the new interface, which might be fine for my mum, but useless for me. Remember, this is a Microsoft beta (equivalent to 0.4-0.7 or therabouts in most open source software). When I was beta'ing Win2K, Win2K went from NT 4.0 look with new barely new color schemes and Win98 pop outs in build 1477 through to Win2K's look and feel in about six hundred new builds. Expect Whistler's appearance to change until about April next year.
It seems stable enough. It has ATA-100 support (something that I had to retroactively add to Win2K when I got my Dell) and the screen drivers seem snappy enough. I'm intrigued to find that people are already reporting stuff doesn't work as everything I've tried (including a couple of games) works fine for me. My Logitech USB joystick just worked, and my USB Canon Ixus similarly just worked (in fact, the new features in Whistler for this stuff is just fantastic).
I like the new user "disconnect" feature. It allows multiple users to remain logged on and you can quickly move between them (if you have adequate memory).
I like the way print drivers seem to be kicked out of kernel mode. My 710c never gave me grief in Win2K, but now there's even less chance with Whistler.
Other than that, it's too early to make a full judgement. I've already found one potential security flaw and I have a negative installation experience during the express upgrade, but as I'm a tester and this is a beta, I've told Microsoft about both issues, and they'll fix it, like they did with the six things I found during the three years I tested Win2K. If every one of the "beta" testers did this, the product would be a far better product for it.
If you're lucky you might learn something. I taught my NT Workstation course instructor about NT's memory management because he didn't understand it. I also spent most of that week making a mess of other people's boxes (which is trivial because most students don't even change the default administrator password). But the SQL instructor was a very clueful guy. I still occasionally use the MSSQL skills I learnt then when I have to do mysql, Oracle, or Sybase ASE work.
In the Exchange course I managed to play with the Exchange 5.0 key server which I hadn't used before (or since), and that sort of thing can be helpful, as you don't play with all aspects of a product in real life.
My MCSE: NT 4.0 stream, Exchange 5.5, SQL 6.5
I work in an large environment with retarded monkeys in control. Trust me, the NT and Win2K boxes there stay up despite their best efforts.
Intel x86 and x86-compatible CPUs and associated bits n pieces are currently very power hungry. This will change - eventually, but then comes part two of my assertion: ia64.
The first generation of ia64 will not be a handheld or laptop processor for a long time because it is first and foremost a replacement for the Xeon line of processors. But in time, ia64 will become the preferred binary instruction set due to sheer weight of numbers.
Making software portable now, will help both the seamless transition between x86, x86-64 and ia64. Or indeed platforms like my Alpha.
Lastly, a variety of CPU vendors allows for much cheaper CPU's. Do you think that you'd have Celerons for not much money if viable competition did not exist? I don't think so either.
Linus released Linux in 1991. Berkeley had BSD code out there before 1980. Linus is a late starter to all this. comp.sources.unix was vibrant at that time, ipso facto, Linus was jumping on the bandwagon. ESR's little manifesto came out in mid-1997, 21 years after Bill Gates accused hobbyists of stealing and demanding a new distribution model for software: paying for it.
Open source is not new. And it predates Linux by a long shot.
Get with the program.
Libertarian nuts != open source.
/dev/null where they damn well belong.
I'm sick of it. Libertarians are the fringe of politics and for good reason. Libertarians are NOT the friends of open source, and we would do well to steer clear of them.
Civil society improves the lot of the average peasant. Secular humanism improves the lot of oppressed non-Christians everywhere. Governments are good for society, as it allows society to flourish without fear from random uprisings or internecine civil warfare. An open, democratic society is demonstrably better than being in a despotic state (see Burma) or a lawless state (see Indonesia, a raft of sub-Saharan african nations such). You get one the best forms of democratic state via the use of the Westminster system, where church and state are separated. Examples are the US, England, Australia, and New Zealand. Very similar democracies exist in most European countries as well.
What does libertarians wish? Really dang small government, where the government is cast as the evil doer. The libertarian extremists wish us all to be armed to be teeth to protect ourselves from the nuts next door (as well as the guv'mint) because under their model, there is no government to interfere in their "right" to do whatever they damn well please.
Anyway, if there really was dang small government, there would be really big business. Can you imagine what would happen to what might have been the Internet? It would be expensive (recall Compu$erve). It would be proprietary (recall Compu$erve). Linux wouldn't be anywhere because the government would have let a DCMA style bill pass much before now so IBM's MCA bus would have succeeded, and we would all be paying IBM tax and not Microsoft tax on our new PC's. So remember, libertarians are NOT your friends.
This is all so far from actually doing any coding of any sort that I wish places like slashdot (where it is co-joined all too regularly) would drop these little nuggets of crap in
harumpf.
IR has dropout problems. I have problems all the time with my various remotes. I need more IR shiny surfaces to encourage the set top box to change channels more easily.
We play nothing but Total Annilihation here. I'm waiting for the PS2 to come out in Australia, but even then, I might wait for it to come down a little bit before buying into it.
Our lounge room with two of the laptops and essential entertainment equipment. Notice no steenking cat 5 for us!
Check this out for all your the Comic Book Guy references.
Point taken. CBG would be proud of you.
The Android from the Simpsons. The big fat guy who is aka "The Collector" in the Lucy Lawless episode. The guy who runs the comic shop. The guy who gets the medium size star trek utility belt.
oops
You need the following things:
* a big fat pipe that everyone pays for (DSL or cable is fine). And I'm not talking about a bucket bong here.
* an agreed administrator for the firewall and internal infrastructure (dhcp, mail relay, etc). This person then gets to choose the One True Operating System(tm) for the firewall and the rest of you can get stuffed. Rotate on a three month basis to reduce friction
* bins a fair way away from the kitchen or dining room (the pizza boxes get gross when people "forget" to take the rubbish out)
* a large fridge to take the booze (this is not optional for Australian-infested geek houses)
* lots of fridge magnets for the pizza menus
* A WaveLAN gateway for resident and itinerant geeks, and lots of long cat5 cables for those who are WaveLAN challenged. Spare WaveLAN cards
* rules on significant others staying more than about three nights a week. Even when everyone in the house is earning more than six figures.
* rules on who buys the next bottle of single malt scotch, cognac, brandy, even *shhudder* bourbon (there's nothing worse than using a marker on a Glenlivet or Glenmorangie)
* Sound padding for the walls when people spank the monkey. Got to have privacy, man.
* A damn fine hifi with a large CD and DVD collection. Most geeks will supply this one without too many problems
* Big ass TV. None of this 34 cm crap. Most geeks disdain TV publically, but are closet watchers. Example, ask who the Android is and why they identify with him. You'll get an answer from 99.99% of all True Geeks(tm).
* Cable or satellite TV with as many channels as the house can afford
* UPS for the machine room. Get an extractor if gets warm like ours does.
Tips for living with a geek
Get a cleaner at least once every two weeks. This works fine for me.
Get a gardener if you have a garden. Geeks do not garden on a regular enough basis. Things will die and overgrow and look messy and you can get evicted.
Work on the chores. Geeks are naturally lazy and refuse to do the dishes if they do the rubbish or vice versa. Don't mention the bathroom
Kick the mess back into the responsible person's bedroom. The shared areas shouldn't be cluttered with people's crap unless it's really geeky and can be used or admired by all.
You can get the newest version here.
Here's the stack in action:
That's over my WaveLAN wireless PC Card in my Win2K laptop to my flatmate's Libretto C100 running a recent NetBSD-current which is our WaveLAN - LAN gateway. All of our boxes are IPv6 native. No IPv4 encapsulation for us. And yes, WaveLAN kicks ass! You NEED WaveLAN.
So, in answer to one of the major questions, Microsoft's stack works with other IPv6 implementations. It doesn't keep settings between reboots at the moment, and it doesn't do ESP only AH.
I work in the architecture area of a large telco. We have 30,000 desktops to manage. Every time we need a change, the lack of desktop scalability bites us every time.
The registry is per machine. Windows 2000 makes that accessible via the Network, using Group Policy.
Therefore anything that allows administrators to look after a 30,000 desktop change in one to two days is a major win.
For a start, Win2K's kernel bears no resemblance to the DOS kernel. The 16 bit command interpreter is not present.
/* or chown -R nobody.users /* administrators can make the security a whole bunch worse if they DO NOT HAVE A CLUE.
The registry (as with all other objects, including files, mutexs, memory sections, etc) is protected via the Object Manager, which calls the Security Reference Monitor to check validation.
If the programs have the Win2K logo, they have the correct permissions for TS and use the registry properly (per machine settings go in HKLM and per user settings are in HKCU, which in Win2K hangs out in the Active Directory in a domain environment).
Security is moderately tight, but just like a chmod -R ugo=rwX
Better not tell the guys doing KDE and Gnome that a single centralized place to do administration is a bad idea. Administrators looking after 30,000 desktops can't work any other way. It's not a flawed architecture - it's the ONLY scalable model to move us forward from the each system is an island in the sea of machines.