Um... no. In July 2000, Mullah Omar ordered a ban on poppy cultivation. As far as I know, this hasn't been lifted. Other members of the Northern Alliance are responsible.
I presume you are a US citizen; please know your enemy. The Taliban may be at war with the US, but they are even harder on drugs. It is about as conceivable as Pat Robertson selling heroin to fund Christian Outreach.
Would work just fine for the data that the iPod supports.
So, that's not a good excuse for Apple causing this much pain. MTP could be added in a firmware update. And, the check-file updating could be done on the device if the MTP path is chosen. Yes, MTP users may be disadvantaged (by synching more slowly), but (for me anyway) it would beat having to start Windows XP(tm) in a virtual machines, and then launching iTunes.
But... openoffice.org is better than ms office. And, it's not an ms office clone.
Right now, I am giving presentations with impress. Slides to the projector, and my presenter screen on the laptop has the slide, the next slide, presenters notes and a clock.
openoffice.org actually runs on the platforms I use (Solaris and Linux).
openoffice.org integrates with LaTex.
openoffice.org offers PDF/A-1a export. openoffice.org font selection shows the font in the pulldown. (maybe recent MS stuff does these things too -- but MS needed to catch up).
Since openoffice.org runs on Solaris and Linux, and MS Office doesn't, it's absolutely a no-brainer. openoffice.org is better.
I still have my old analog modem, and I still control my own network. We hackers will simply retreat to UUCP ("bbs" for the micro-computer generation). With known and trusted peers only.
About the only thing added will be full crypto on the UUCP links.
And when they come for that...
It will go back to physical data exchange.
Too bad, though. But the level of discourse may become reasonable again, and maybe, just maybe, SPAM will go away. At least on the darknets.
"What the FSF doesn't realize is that their "ideals" are, for all intents and purposes, "defective by design", because it doesn't take into account the need for something to "just work" that doesn't require a geek to configure, tweak, install, maintain it.
And this is why Linux is not on the "desktop". I just set up Ubuntu for one of my relatives, on his laptop. While it installed and configured itself perfectly with one exception, that one exception would be a deal killer if I wasn't capable in fixing it. The wireless setup was broken."
And, in implied comparison, Apple iPhone wireless should be "just working".
Ok. Let me give you a counter-example. One will do (I am simply disproving your hypothesis). When the Apple (OS X, iPod Touch, iPhone) requests a DHCP server to assign an IP address, it doesn't actually trust that address. Instead, it will make ARP requests to ensure to it's satisfaction that the IP address is not in use.
Normally, this won't present any problems. However, if a layer 3 packet bridge is in the network, (parprouted would be an example), the ARP requests will be satisfied from the bridge. Thus (OS X, iPod Touch, iPhone) will refuse the IP address, and simply request another one.
The solution? For OS X, the ARP verification can be controlled via an obscure setting. Setting it to "0" disables the feature, allowing OS X to participate. The same change cannot be made on the iPod Touch or the iPhone. The solution for these devices is to assign a fixed IP address.
This problem would be completely beyond the comprehension of the target audience. And, is actually "impossible" to fix for the iPod Touch and iPhone (the DHCP client just doesn't work).
So, in conclusion, OS X, iPhone and iPod Touch are obviously (by your argument), not ready "for the desktop".
Which is an absurd result. Meaning that we have proven that your original statement is in error. Reductio ad absurdum. QED.
Note - the a and b are aligned. Assuming 8 space tab expansion. Now, let's see a 3 character expansion.
double...a; int...b;
Notice that a and b are no longer aligned -- even with a stinkin' monospace font!
And, what about the edge case - ? Can a space be tabbed? I sure hope so. Witness the expansion.
int.a,....b;
To maintain this over indent levels means that spaces should be tabbed.
Now, the solution is simple - tab control separate from source. This would allow me to say
inta, b;
which is what I am really trying to express. Notice the clear distinction between "indent" and "tab" here. What we then need is some format definition associated with the source - might as well go with proportional fonts and bold/italic as well.
But, as long as we only have AND it can be redefined (in some cases, its worse - I've had to deal with an editor that only allowed to be expressed as the next PIXEL boundary to move to. eg. tab=10 meant go to the next even 10 pixels), I'll stick with spaces, m'ok'thanx.
As you mentioned, it is a Linux Server. Which kind of implies that it isn't a Linux Client (well, it could be, but read on).
If your colleague is using Windows to access the server, simply mount (hey, this gets us back to SAMBA) the directory. Use whatever the usual approach is -- drill down, etc. After that step, she should simply right-click (or whatever) and assign a drive letter.
End of discussion. No need to launch into "the Unix way".
If your colleague is using Linux/BSD/Mac/? then she probably isn't going to be asking about drive letters. Most likely, she will be asking about the Mac way, which is simple enough. Drill down and just use the damn folder on that server.
If she is using something other than Windows/MAC, she needs some training. But, given the question, I would strongly suggest that she be nudged back to Windows.
I am assuming that your colleague isn't attempting to administer this server (but I do have to ask).
Of course Microsoft had an SMB implementation! That's (partly) the point.
SMB (Lan Manager) was the native file sharing for Windows (Windows 3.11 for Workgroups and DOS). Would you want to run a company using Windows 3.11 for Workgroups or DOS as your server? Go ahead. SAMBA simply acknowledges that people want to use DOS and Windows on the client.
The competition would have been Netware, and its client side interface.
LAN Manager on OS/2 was probably the direction seen by most as the "future" of SMB. Some wanted Unix servers, instead. As an aside, rank DOS, Windows 16 bit, OS/2 1.x, OS/2 2.x, Windows 9x, and Windows NT (XP, Vista, 7) and Unix as server level OSs. Which would you have preferred back in '94? "LAN Manager" code didn't exist for anything less that OS/2 1.x; the file sharing code in DOS and Windows 16 bit was probably quite a kludge (both DOS and Windows 16 bit use pre-emptive multi-tasking, and the networking was based on the IBM PCNet code). LAN Manager was released in 1987 to compete with Netware. Note that OS/2 Lan Manager was updated when Windows NT 1.0 was released to remain compatible (in 1993).
So, the importance of NT was that it provided a jump-off point for Microsoft and AT&T to produce a Unix SMB server. Note that most consider this to be of poor quality (I referenced the SUN PC Netlink experience in support of this assertion). It is not clear to me if an Enterprise quality server implementation of SMB existed before NT; at least, not one from Microsoft (unless you are going to count OS/2 1.x Lan Manager). The entire point I was driving at was that SAMBA grew into that implementation (and, note that SMB was originally not even a Microsoft thing -- it was developed at IBM).
SAMBA has simply been as implementation of SMB for Unix, supporting Microsoft client OSs. I know you referenced AD in your other post -- simply not relevant in this discussion. How else do you accomplish this task? Here are some possibilities:
- Use Windows (Vista, 7) exclusively as your file servers. - Use Windows (Vista, 7) as "shim servers" against a back-end server. - Use SAMBA. - Use PC Netlink (or another AS/U implementation).
Of these solutions, SAMBA looks pretty good. Personally I don't care what you use (and this really doesn't for most home users either; after all, SAMBA pretty much implies that you are using Unix somewhere).
So, technically (in a VERY narrow sense), you are correct. LAN Manager predated SAMBA (1987 vs 1992 or so, make it by 5 years). On the other hand, were you using OS/2 back then? It would have forced you to use a 286 processor, and commodity hard drivers in a server. The drive to SAMBA adoption was that this could be replaced by a Unix box. My way of looking at it was that SAMBA, in allowing Unix boxes to be used as servers for Windows/DOS, allowed the growth of SMB as a protocol in the Enterprise. If SAMBA hadn't existed, I doubt that SMB/CIFS would have been anywhere near as popular (we probably would be having this discussion about the Netware client now).
SAMBA having to clone the AD stuff? Think about that a bit. Yes, it's targeted as a compliant implementation. On the whole, it is a win for Microsoft, though, because it lets "big iron" support the Microsoft infrastructure. From your tag-name "Lunix Nutcase", I presume that you have some interest in Linux and Unix. I imagine that Microsoft wasn't that interested in Linux implementations of SAMBA, but is (likely) very supportive of Solaris and AIX implementations (just my guess). Linux would be of most interest (again, a guess) to Microsoft with the Z-Series implementation running SAMBA.
Given that Windows won't (likely ever) run on Power, Sparc or Z-Series, being able to directly mesh these systems into a Windows ecosystem just benefits Microsoft.
What I don't understand is why Microsoft isn't more supportive of SAMBA. Maybe the SAMBA developers pissed them off (which brings us back to this story). Remember: as long as SMB is the default file shar
SAMBA wasn't developed as a clone or a replacement for anything Microsoft produced. In fact, SAMBA (then known as server, or nbserver) predated Windows NT release.
Microsoft themselves offered patches early on (1993), even before the product was named SAMBA. Probably because it was advantageous to Microsoft. Simply, the idea was to have Unix boxes act as file servers for Windows. Windows didn't support NFS (directly - SMB is the native protocol - Beame and Whiteside supported NFS on NT in 1994, but this would be an extra-cost client expense).
Of course, eventually NT "grew up" and began to support more infrastructure operation, but, even today, SAMBA is a vital part of the "Windows Enterprise". If you are running Power or Sparc on servers and want to share to Windows, it's really the way to go.
AT&T offered a licensed Microsoft SMB implementation (Advanced Server for Unix), which was sub-licensed by some Unix vendors (SUN, HP, SCO, and possibly others). Unfortunately the quality of the implementation was questionable. SUN spent two years cleaning up the code before releasing it as PC-Netlink (HP and SCO may have offered it earlier). Microsoft didn't release the NT SMB code to AT&T until 1994. SUN released PC Netlink on Feb 1, 1999.
Which meant that from 1992/3 to 1999, the only way to run an SMB native file server on SUN was to use SAMBA. (You could have run NFS using Beame & Whiteside/Hummingbird).
How is SAMBA copying anybody here? (if we assume that a Windows NFS client had been made available by Microsoft, SAMBA would never have been popular).
"That's one heck of a detailed claim. Infringement would require some effort; anticipation (every limitation appearing in a single document, arranged in the same manner as the claim) is unlikely."
Um...
My "Computer Science" foo may not be strong, but I do see a problem.
Let's begin with the definition of "process" and "interconnected processors". When translated this actually doesn't mean much, especially if using a functional notation. In short, a functional sort has to conflict.
Except of course for the clause:
"and wherein at least two of the second plurality of the worker processes operate simultaneously"
Now, this may, or may not happen. I guess it depends on the implementation of the functional programming system. But, we certainly cannot permit the automatic parallelization of functional algorithms anymore!
I use "Dropbox" to move/synchronize files. Of course, I leave the silly default files alone.
But my own stuff? How about that lovely file "DrMm9Vs1udHmzdZG41chJ5,K"? That one's only 77 bytes long -- I guess they could figure out which files I update most often, and, given enough compute power, figure out that THAT file is an idea I jotted down last week...
Just encrypt the stinking data BEFORE you send it to them. It's cloud survival 101.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
542 root 19 -1 352m 16m 11m R 24 3.3 85:38.02 X
3547 user 20 0 226m 91m 22m R 9 18.6 33:51.96 firefox
9213 user 20 0 84032 15m 9720 R 4 3.2 0:02.46 Terminal
[snip]
The netbook is not unstable; firefox is usable, and is using 91m of memory,
Your grandparent poster made a negative reference to "Cubible(sic) Joe". Implying that the artistic type didn't have to work in a cubicle, and made more money.
Your parent poster simply wanted a piece of the action. And asked how that might be arranged. Tongue-in-cheek.
You, sir, are the pompous blowhard.
Now THAT'S what I call the "Apple fanboi" way -- start off with an insulting git, and move to a weirdly self-referential pompous blowhard; all believing that somehow they are providing deeply meaningful comments. It's actually entertaining! Thanks for the grins.
But you know the real take-away for me? You have just given me my new sig!
It's not a race. If software is written to a standard, there is an expectation that it can be moved to other platforms by simply recompiling.
The platform can then be chosen to meet the customers needs.
To give an example: A large company was using workstations made by ***, but were afraid that *** was going out of business. They then rebuilt the application to work on desktop systems made by **** utilizing graphics cards from ***** and ******. Since the applications used OpenGL for rendering, the move was simple. Unfortunately, neither of the implementations supported Z-cued lines, which was important for the application. The customer then tried workstations from vendor *** whose OpenGL implementation did support Z-cued lines.
Of course, wire-frame drawing with Z-cued lines isn't important in the gaming space, but using OpenGL as the lingua fraca allowed the software to be moved.
Does Direct3D support Z-cued lines? I don't know, and, frankly, don't care. The application cannot be moved to anything other than an Intel box, utilizing nVidia or ATI anyway.
Military applications, phones, embedded, are then not reachable.
So, sure, go ahead and use the graphics support that is appropriate. But, since there are only two platforms (Windows and XBox) that can use Direct3D, I have never even bothered to learn about it. It may be the "cat's meow", but it is easier to simply recommend the use of OpenGL on Windows (and I could not, honestly, care less about XBox), and guarantee at least a path for portability.
"Because the people who WORK on the Macs are the people who draw for a living, compose music, make videos, etc. They are the people who have the jobs Cubible Joe wish he could have (and are obviously successful enough at it to afford apple products)."
I am a "Cubible(sic) Joe". I have a job that doesn't involve drawing (much), music or videos. Sure, I could work on a Mac -- and I can even afford Apple products.
"IBM might be a big US company but it is hardly focused "almost entirely" on open source. Pretty much all of their hardware is proprietary,
As much as Sun's."
SUN put SPARC up for standardization. IEEE Standard 1754-199.
"their own Unix is proprietary,
But you have a choice of different OS's supported on their proprietary hardware, unlike Sun. This includes Linux, for which IBM has made the contributions for the hardware-specific features."
And how is this different from SUN? Oh, wait, SUNs OS is open-source, and, because the platform is open, it is easy enough to put Linux on.
"they sell all sorts of proprietary tools like Lotus Notes, ClearCase and the rest of the Rational tools, etc.
Sun sells many proprietary products.
Sure you can point out a number of projects and things they work on and support that are open source, but those hardly make up even a significant portion of their portfolio.
The same can be said for Sun. Of course, Oracle also makes contributions (check the stats for recent kernels, Oracle is normally somewhere around number 3-5 corporate contributor, behind Red Hat, Novell, IBM."
NFS, NIS, Solaris, JAVA, OpenOffice, VirtualBox, MySQL etc. How much more would you have wanted? Anyway, SUN obviously never got much traction with people like you, and is now no more. RIP, SUN. And why would SUN have been a major Linux contributor, anyway? Aside from silly Linux-side licensing quibbles that prevent stuff like DTRACE and ZFS from being incorporated into Linux (which BSD has already incorporated). Now Oracle is in a position to relicense those things. Like I said, RIP SUN. And yet, some people STILL bash on it.
No. Because "more fps is better". Helps AMD and nVidia sell new graphics cards, and helps sell new systems to gamers. (similar to "horsepower", and "ping time", "fps" is a single brag-measure).
And, because it is easiest to generate a game using a generate/event loop. The technique was described in
James D. Foley , Andries Van Dam, Fundamentals of interactive computer graphics, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1982 (http://portal.acm.org/citation.cfm?id=6684&dl=GUIDE&coll=GUIDE&CFID=69932769&CFTOKEN=26597849)
and is still used to this day.
Personally, I find "twitch games" hopelessly boring, but there is some literature that playing these games improves (in some sense), the human visual system. http://www.rochester.edu/news/show.php?id=3342
I don't have a subscription to "Nature Neuroscience", and I haven't reviewed this myself (not my field). The brief synopsis indicates an improvement in gray-scale resolving, but I don't know of any supporting experiments yet.
But 35% is far better than "can't do it at all". Which is what an Atom with the older gen Intel would get you.
And 35% still gives you plenty of CPU for background tasks (which you probably won't even utilize).
So, you would then have to judge the two solutions based on power performance (especially since you brought in the Atom processor). Do you have any insight into the relative power performance? (to clarify, a unit like "BlueRay/hour").
Which is why the model "identify malware" doesn't work.
The cute kittens on the screen-saver is NOT malware. Even if it "phones home" it's not malware. It's only malware if it does something that the user doesn't want. So... it's not even malware if it opens a mail relay and spams... if that's what the user wants.
The only way to prevent malware is to allow the definition of what malware is. Resources used by programs can be checked against those definitions. This is the thrust of efforts like kernel capabilities and MAC (mandatory access controls).
It took YEARS to fit this into Linux, and provide workable base definitions. Arguably, 6 versions of Fedora were needed to successfully migrate to SELinux.
Now, repository owners need to do due diligence as well, but with a capability/resource controlling system in place, it becomes very difficult to even define what malware is: if a program uses resources beyond what it is allowed, it is simply stopped. This may be a permanent thing (opening a mail relay) or a temporary thing (not having permission to remove a file). The program is simply whatever it is -- one persons malware may well be anothers application.
Of course, there is a firm definition of malware still available - software which subverts the resource control. AFAIK, there aren't any such attacks on SELinux.
Unfortunately, Ubuntu doesn't install a MAC (mandatory access control). Which is REALLY annoying, because without this, welcome to the "Windows Malware Experience".
Microsoft will have to move to a MAC system as well. But, it will time. First, privilege escalation prompts. Then, manual program classification; system programs first, and then others. Then, the utilities needed to allow the definition of security profiles, and then the user debugging of those profiles. Stay the course, Microsoft -- you should be there in 2014 or so.
There are two MAC systems in common use: SELinux and AppAmour. Since I am more familiar with SELinux (they are both based on the same kernel base). Try "sudo apt-get install selinux". Better - switch to Fedora.
Anyway the whole "Linux is obscure, and that's why its secure" argument is easily refuted. Good Linux distributions are much more secure than Windows (pre Vista, anyway).
Vista and beyond implement MAC as well -- via "Mandatory Integrity Control". Four different security layers are defined; low, medium, high and system. But, it isn't clear that general resource use can be tied to these. Files and file system objects can be protected, and processes isolated. But, it still seems coarse... But I am not an expert in MIC, so I may well be wrong.
Anyway, with a MAC system, and the principle that Visa uses putting "internet software" into the Low MIC category, we may well see the end of the "Virus and Malware Protection Racket".
It's the same story with GNU readline(); is the library a vital part of the Pre Viewer? And, if it is, does this make the application a derivative work? Does Palm want to go to court to argue that the Pre Viewer is not a derivative work of muPDF?
I honestly would consider settling if faced with this. Unless I had me some "super lawyers", but, that's just me.
We are talking about MAINTAINING code. Not writing new code.
Standard C did not come with a linked list, stack or queue library. Suck on that fact. If your job is to maintain a such a program, you really have to come to grips with this.
Slashdot Mirror
The Taliban sells heroin?
Um... no. In July 2000, Mullah Omar ordered a ban on poppy cultivation. As far as I know, this hasn't been lifted. Other members of the Northern Alliance are responsible.
I presume you are a US citizen; please know your enemy. The Taliban may be at war with the US, but they are even harder on drugs. It is about as conceivable as Pat Robertson selling heroin to fund Christian Outreach.
No USB protocol for smart devices... Um, no...
http://en.wikipedia.org/wiki/Media_Transfer_Protocol
Would work just fine for the data that the iPod supports.
So, that's not a good excuse for Apple causing this much pain. MTP could be added in a firmware update. And, the check-file updating could be done on the device if the MTP path is chosen. Yes, MTP users may be disadvantaged (by synching more slowly), but (for me anyway) it would beat having to start Windows XP(tm) in a virtual machines, and then launching iTunes.
But... openoffice.org is better than ms office. And, it's not an ms office clone.
Right now, I am giving presentations with impress. Slides to the projector, and my presenter screen on the laptop has the slide, the next slide, presenters notes and a clock.
openoffice.org actually runs on the platforms I use (Solaris and Linux).
openoffice.org integrates with LaTex.
openoffice.org offers PDF/A-1a export. openoffice.org font selection shows the font in the pulldown. (maybe recent MS stuff does these things too -- but MS needed to catch up).
Since openoffice.org runs on Solaris and Linux, and MS Office doesn't, it's absolutely a no-brainer. openoffice.org is better.
Yes, I can see it coming.
I still have my old analog modem, and I still control my own network. We hackers will simply retreat to UUCP ("bbs" for the micro-computer generation). With known and trusted peers only.
About the only thing added will be full crypto on the UUCP links.
And when they come for that...
It will go back to physical data exchange.
Too bad, though. But the level of discourse may become reasonable again, and maybe, just maybe, SPAM will go away. At least on the darknets.
I like content
I used to buy content
But then you asked for money for every blank
So fuck you
I would like to see HD movies
But you said Macrovision is a must
And I can't upscale to my TV
So fuck you
I bought into HD-DVD
And picked up a few nice movies
But the content cartel said no
So fuck you
I have divx on every player
And terrabytes of storage
But I can't buy movies that way
So fuck you
My mp3 player does wireless
And its legal to share songs*
But the player won't do it
So fuck you
*In Canada
"What the FSF doesn't realize is that their "ideals" are, for all intents and purposes, "defective by design", because it doesn't take into account the need for something to "just work" that doesn't require a geek to configure, tweak, install, maintain it.
And this is why Linux is not on the "desktop". I just set up Ubuntu for one of my relatives, on his laptop. While it installed and configured itself perfectly with one exception, that one exception would be a deal killer if I wasn't capable in fixing it. The wireless setup was broken."
And, in implied comparison, Apple iPhone wireless should be "just working".
Ok. Let me give you a counter-example. One will do (I am simply disproving your hypothesis). When the Apple (OS X, iPod Touch, iPhone) requests a DHCP server to assign an IP address, it doesn't actually trust that address. Instead, it will make ARP requests to ensure to it's satisfaction that the IP address is not in use.
Normally, this won't present any problems. However, if a layer 3 packet bridge is in the network, (parprouted would be an example), the ARP requests will be satisfied from the bridge. Thus (OS X, iPod Touch, iPhone) will refuse the IP address, and simply request another one.
The solution? For OS X, the ARP verification can be controlled via an obscure setting. Setting it to "0" disables the feature, allowing OS X to participate. The same change cannot be made on the iPod Touch or the iPhone. The solution for these devices is to assign a fixed IP address.
This problem would be completely beyond the comprehension of the target audience. And, is actually "impossible" to fix for the iPod Touch and iPhone (the DHCP client just doesn't work).
So, in conclusion, OS X, iPhone and iPod Touch are obviously (by your argument), not ready "for the desktop".
Which is an absurd result. Meaning that we have proven that your original statement is in error. Reductio ad absurdum. QED.
Oops, f'n thing ate my homework
try this
[clear tabs][indent]int[space][define tab]a,
[tab]b;
instead
I hope this clarifies wtf I'm talking about.
Simply put, "tab" doesn't work...
doublea;
intb;
should render as (LEADING indent removed)
double..a;
int.....b;
Note - the a and b are aligned. Assuming 8 space tab expansion. Now, let's see a 3 character expansion.
double...a;
int...b;
Notice that a and b are no longer aligned -- even with a stinkin' monospace font!
And, what about the edge case - ? Can a space be tabbed? I sure hope so. Witness the expansion.
int.a, ....b;
To maintain this over indent levels means that spaces should be tabbed.
Now, the solution is simple - tab control separate from source. This would allow me to say
inta,
b;
which is what I am really trying to express. Notice the clear distinction between "indent" and "tab" here. What we then need is some format definition associated with the source - might as well go with proportional fonts and bold/italic as well.
But, as long as we only have AND it can be redefined (in some cases, its worse - I've had to deal with an editor that only allowed to be expressed as the next PIXEL boundary to move to. eg. tab=10 meant go to the next even 10 pixels), I'll stick with spaces, m'ok'thanx.
The "Unix" way?
As you mentioned, it is a Linux Server. Which kind of implies that it isn't a Linux Client (well, it could be, but read on).
If your colleague is using Windows to access the server, simply mount (hey, this gets us back to SAMBA) the directory. Use whatever the usual approach is -- drill down, etc. After that step, she should simply right-click (or whatever) and assign a drive letter.
End of discussion. No need to launch into "the Unix way".
If your colleague is using Linux/BSD/Mac/? then she probably isn't going to be asking about drive letters. Most likely, she will be asking about the Mac way, which is simple enough. Drill down and just use the damn folder on that server.
If she is using something other than Windows/MAC, she needs some training. But, given the question, I would strongly suggest that she be nudged back to Windows.
I am assuming that your colleague isn't attempting to administer this server (but I do have to ask).
Of course Microsoft had an SMB implementation! That's (partly) the point.
SMB (Lan Manager) was the native file sharing for Windows (Windows 3.11 for Workgroups and DOS). Would you want to run a company using Windows 3.11 for Workgroups or DOS as your server? Go ahead. SAMBA simply acknowledges that people want to use DOS and Windows on the client.
The competition would have been Netware, and its client side interface.
LAN Manager on OS/2 was probably the direction seen by most as the "future" of SMB. Some wanted Unix servers, instead. As an aside, rank DOS, Windows 16 bit, OS/2 1.x, OS/2 2.x, Windows 9x, and Windows NT (XP, Vista, 7) and Unix as server level OSs. Which would you have preferred back in '94? "LAN Manager" code didn't exist for anything less that OS/2 1.x; the file sharing code in DOS and Windows 16 bit was probably quite a kludge (both DOS and Windows 16 bit use pre-emptive multi-tasking, and the networking was based on the IBM PCNet code). LAN Manager was released in 1987 to compete with Netware. Note that OS/2 Lan Manager was updated when Windows NT 1.0 was released to remain compatible (in 1993).
So, the importance of NT was that it provided a jump-off point for Microsoft and AT&T to produce a Unix SMB server. Note that most consider this to be of poor quality (I referenced the SUN PC Netlink experience in support of this assertion). It is not clear to me if an Enterprise quality server implementation of SMB existed before NT; at least, not one from Microsoft (unless you are going to count OS/2 1.x Lan Manager). The entire point I was driving at was that SAMBA grew into that implementation (and, note that SMB was originally not even a Microsoft thing -- it was developed at IBM).
SAMBA has simply been as implementation of SMB for Unix, supporting Microsoft client OSs. I know you referenced AD in your other post -- simply not relevant in this discussion. How else do you accomplish this task? Here are some possibilities:
- Use Windows (Vista, 7) exclusively as your file servers.
- Use Windows (Vista, 7) as "shim servers" against a back-end server.
- Use SAMBA.
- Use PC Netlink (or another AS/U implementation).
Of these solutions, SAMBA looks pretty good. Personally I don't care what you use (and this really doesn't for most home users either; after all, SAMBA pretty much implies that you are using Unix somewhere).
So, technically (in a VERY narrow sense), you are correct. LAN Manager predated SAMBA (1987 vs 1992 or so, make it by 5 years). On the other hand, were you using OS/2 back then? It would have forced you to use a 286 processor, and commodity hard drivers in a server. The drive to SAMBA adoption was that this could be replaced by a Unix box. My way of looking at it was that SAMBA, in allowing Unix boxes to be used as servers for Windows/DOS, allowed the growth of SMB as a protocol in the Enterprise. If SAMBA hadn't existed, I doubt that SMB/CIFS would have been anywhere near as popular (we probably would be having this discussion about the Netware client now).
SAMBA having to clone the AD stuff? Think about that a bit. Yes, it's targeted as a compliant implementation. On the whole, it is a win for Microsoft, though, because it lets "big iron" support the Microsoft infrastructure. From your tag-name "Lunix Nutcase", I presume that you have some interest in Linux and Unix. I imagine that Microsoft wasn't that interested in Linux implementations of SAMBA, but is (likely) very supportive of Solaris and AIX implementations (just my guess). Linux would be of most interest (again, a guess) to Microsoft with the Z-Series implementation running SAMBA.
Given that Windows won't (likely ever) run on Power, Sparc or Z-Series, being able to directly mesh these systems into a Windows ecosystem just benefits Microsoft.
What I don't understand is why Microsoft isn't more supportive of SAMBA. Maybe the SAMBA developers pissed them off (which brings us back to this story). Remember: as long as SMB is the default file shar
Um...
SAMBA wasn't developed as a clone or a replacement for anything Microsoft produced. In fact, SAMBA (then known as server, or nbserver) predated Windows NT release.
Microsoft themselves offered patches early on (1993), even before the product was named SAMBA. Probably because it was advantageous to Microsoft. Simply, the idea was to have Unix boxes act as file servers for Windows. Windows didn't support NFS (directly - SMB is the native protocol - Beame and Whiteside supported NFS on NT in 1994, but this would be an extra-cost client expense).
Of course, eventually NT "grew up" and began to support more infrastructure operation, but, even today, SAMBA is a vital part of the "Windows Enterprise". If you are running Power or Sparc on servers and want to share to Windows, it's really the way to go.
AT&T offered a licensed Microsoft SMB implementation (Advanced Server for Unix), which was sub-licensed by some Unix vendors (SUN, HP, SCO, and possibly others). Unfortunately the quality of the implementation was questionable. SUN spent two years cleaning up the code before releasing it as PC-Netlink (HP and SCO may have offered it earlier). Microsoft didn't release the NT SMB code to AT&T until 1994. SUN released PC Netlink on Feb 1, 1999.
Which meant that from 1992/3 to 1999, the only way to run an SMB native file server on SUN was to use SAMBA. (You could have run NFS using Beame & Whiteside/Hummingbird).
How is SAMBA copying anybody here? (if we assume that a Windows NFS client had been made available by Microsoft, SAMBA would never have been popular).
"That's one heck of a detailed claim. Infringement would require some effort; anticipation (every limitation appearing in a single document, arranged in the same manner as the claim) is unlikely."
Um...
My "Computer Science" foo may not be strong, but I do see a problem.
Let's begin with the definition of "process" and "interconnected processors". When translated this actually doesn't mean much, especially if using a functional notation. In short, a functional sort has to conflict.
Except of course for the clause:
"and wherein at least two of the second plurality of the worker processes operate simultaneously"
Now, this may, or may not happen. I guess it depends on the implementation of the functional programming system. But, we certainly cannot permit the automatic parallelization of functional algorithms anymore!
Almost any attempt runs afoul of this patent.
Dreaming? Nah.
I use "Dropbox" to move/synchronize files. Of course, I leave the silly default files alone.
But my own stuff? How about that lovely file "DrMm9Vs1udHmzdZG41chJ5,K"?
That one's only 77 bytes long -- I guess they could figure out which files I update most often, and, given enough compute power, figure out that THAT file is an idea I jotted down last week...
Just encrypt the stinking data BEFORE you send it to them. It's cloud survival 101.
I really want EVERY site I visit to use https. Why doesn't slashdot?
Ok, I just had firefox 3.0.3 running overnight on my netbook. 512M, but running Linpus Linux (not XP), with 22 addons.
Extensions are:
BetterPrivacy, CookieSafe, DownloadHelper, FEBE, Flagfox, Flashblock, Ghostery, Greasemonkey, MediaWrap, NoScript, NoSquint, Platypus, Torbutton, TrackMeNot, User Agent Switcher, VMware Remote Console Plug-in
Plugins are:
Adobe Reader 8.0, mplayerplug-in 3.50, DjVuLibre-3.5.19, GCJ Web Browser Plugin 1.4, Shockwave Flash 10.0 r12, Tcl Plugin 3.1.0
top - 08:19:26 up 10:55, 2 users, load average: 0.19, 0.43, 0.44
Tasks: 124 total, 4 running, 120 sleeping, 0 stopped, 0 zombie
Cpu(s): 32.6%us, 5.4%sy, 0.0%ni, 61.4%id, 0.0%wa, 0.5%hi, 0.0%si, 0.0%st
Mem: 504732k total, 496596k used, 8136k free, 11352k buffers
Swap: 1052248k total, 68k used, 1052180k free, 165084k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
542 root 19 -1 352m 16m 11m R 24 3.3 85:38.02 X
3547 user 20 0 226m 91m 22m R 9 18.6 33:51.96 firefox
9213 user 20 0 84032 15m 9720 R 4 3.2 0:02.46 Terminal
[snip]
The netbook is not unstable; firefox is usable, and is using 91m of memory,
Your grandparent poster made a negative reference to "Cubible(sic) Joe". Implying that the artistic type didn't have to work in a cubicle, and made more money.
Your parent poster simply wanted a piece of the action. And asked how that might be arranged. Tongue-in-cheek.
You, sir, are the pompous blowhard.
Now THAT'S what I call the "Apple fanboi" way -- start off with an insulting git, and move to a weirdly self-referential pompous blowhard; all believing that somehow they are providing deeply meaningful comments. It's actually entertaining! Thanks for the grins.
But you know the real take-away for me? You have just given me my new sig!
It's not a race. If software is written to a standard, there is an expectation that it can be moved to other platforms by simply recompiling.
The platform can then be chosen to meet the customers needs.
To give an example: A large company was using workstations made by ***, but were afraid that *** was going out of business. They then rebuilt the application to work on desktop systems made by **** utilizing graphics cards from ***** and ******. Since the applications used OpenGL for rendering, the move was simple. Unfortunately, neither of the implementations supported Z-cued lines, which was important for the application. The customer then tried workstations from vendor *** whose OpenGL implementation did support Z-cued lines.
Of course, wire-frame drawing with Z-cued lines isn't important in the gaming space, but using OpenGL as the lingua fraca allowed the software to be moved.
Does Direct3D support Z-cued lines? I don't know, and, frankly, don't care. The application cannot be moved to anything other than an Intel box, utilizing nVidia or ATI anyway.
Military applications, phones, embedded, are then not reachable.
So, sure, go ahead and use the graphics support that is appropriate. But, since there are only two platforms (Windows and XBox) that can use Direct3D, I have never even bothered to learn about it. It may be the "cat's meow", but it is easier to simply recommend the use of OpenGL on Windows (and I could not, honestly, care less about XBox), and guarantee at least a path for portability.
"Because the people who WORK on the Macs are the people who draw for a living, compose music, make videos, etc. They are the people who have the jobs Cubible Joe wish he could have (and are obviously successful enough at it to afford apple products)."
I am a "Cubible(sic) Joe". I have a job that doesn't involve drawing (much), music or videos. Sure, I could work on a Mac -- and I can even afford Apple products.
You are an insulting git.
I'll leave it at that.
Wow --
"IBM might be a big US company but it is hardly focused "almost entirely" on open source. Pretty much all of their hardware is proprietary,
As much as Sun's."
SUN put SPARC up for standardization. IEEE Standard 1754-199.
"their own Unix is proprietary,
But you have a choice of different OS's supported on their proprietary hardware, unlike Sun. This includes Linux, for which IBM has made the contributions for the hardware-specific features."
And how is this different from SUN? Oh, wait, SUNs OS is open-source, and, because the platform is open, it is easy enough to put Linux on.
"they sell all sorts of proprietary tools like Lotus Notes, ClearCase and the rest of the Rational tools, etc.
Sun sells many proprietary products.
Sure you can point out a number of projects and things they work on and support that are open source, but those hardly make up even a significant portion of their portfolio.
The same can be said for Sun. Of course, Oracle also makes contributions (check the stats for recent kernels, Oracle is normally somewhere around number 3-5 corporate contributor, behind Red Hat, Novell, IBM."
NFS, NIS, Solaris, JAVA, OpenOffice, VirtualBox, MySQL etc. How much more would you have wanted? Anyway, SUN obviously never got much traction with people like you, and is now no more. RIP, SUN. And why would SUN have been a major Linux contributor, anyway? Aside from silly Linux-side licensing quibbles that prevent stuff like DTRACE and ZFS from being incorporated into Linux (which BSD has already incorporated). Now Oracle is in a position to relicense those things. Like I said, RIP SUN. And yet, some people STILL bash on it.
Wow... just, wow.
No. Because "more fps is better". Helps AMD and nVidia sell new graphics cards, and helps sell new systems to gamers. (similar to "horsepower", and "ping time", "fps" is a single brag-measure).
And, because it is easiest to generate a game using a generate/event loop. The technique was described in
James D. Foley , Andries Van Dam, Fundamentals of interactive computer graphics, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1982 (http://portal.acm.org/citation.cfm?id=6684&dl=GUIDE&coll=GUIDE&CFID=69932769&CFTOKEN=26597849)
and is still used to this day.
Personally, I find "twitch games" hopelessly boring, but there is some literature that playing these games improves (in some sense), the human visual system. http://www.rochester.edu/news/show.php?id=3342
I don't have a subscription to "Nature Neuroscience", and I haven't reviewed this myself (not my field). The brief synopsis indicates an improvement in gray-scale resolving, but I don't know of any supporting experiments yet.
But 35% is far better than "can't do it at all". Which is what an Atom with the older gen Intel would get you.
And 35% still gives you plenty of CPU for background tasks (which you probably won't even utilize).
So, you would then have to judge the two solutions based on power performance (especially since you brought in the Atom processor). Do you have any insight into the relative power performance? (to clarify, a unit like "BlueRay/hour").
MySQL was not driven by commercial SQL servers such as Oracle or DB2.
There was a database called Mini SQL (aka mSQL). Yes, it came with source, but the license was restrictive.
This was the ancestor to MySQL. In-memory, fast tables, and "keep it simple". MySQL was the answer to Hughes mSQL.
Which is why the model "identify malware" doesn't work.
The cute kittens on the screen-saver is NOT malware. Even if it "phones home" it's not malware. It's only malware if it does something that the user doesn't want. So... it's not even malware if it opens a mail relay and spams... if that's what the user wants.
The only way to prevent malware is to allow the definition of what malware is. Resources used by programs can be checked against those definitions. This is the thrust of efforts like kernel capabilities and MAC (mandatory access controls).
It took YEARS to fit this into Linux, and provide workable base definitions. Arguably, 6 versions of Fedora were needed to successfully migrate to SELinux.
Now, repository owners need to do due diligence as well, but with a capability/resource controlling system in place, it becomes very difficult to even define what malware is: if a program uses resources beyond what it is allowed, it is simply stopped. This may be a permanent thing (opening a mail relay) or a temporary thing (not having permission to remove a file). The program is simply whatever it is -- one persons malware may well be anothers application.
Of course, there is a firm definition of malware still available - software which subverts the resource control. AFAIK, there aren't any such attacks on SELinux.
Unfortunately, Ubuntu doesn't install a MAC (mandatory access control). Which is REALLY annoying, because without this, welcome to the "Windows Malware Experience".
Microsoft will have to move to a MAC system as well. But, it will time. First, privilege escalation prompts. Then, manual program classification; system programs first, and then others. Then, the utilities needed to allow the definition of security profiles, and then the user debugging of those profiles. Stay the course, Microsoft -- you should be there in 2014 or so.
There are two MAC systems in common use: SELinux and AppAmour. Since I am more familiar with SELinux (they are both based on the same kernel base). Try "sudo apt-get install selinux". Better - switch to Fedora.
Anyway the whole "Linux is obscure, and that's why its secure" argument is easily refuted. Good Linux distributions are much more secure than Windows (pre Vista, anyway).
Vista and beyond implement MAC as well -- via "Mandatory Integrity Control". Four different security layers are defined; low, medium, high and system. But, it isn't clear that general resource use can be tied to these. Files and file system objects can be protected, and processes isolated. But, it still seems coarse... But I am not an expert in MIC, so I may well be wrong.
Anyway, with a MAC system, and the principle that Visa uses putting "internet software" into the Low MIC category, we may well see the end of the "Virus and Malware Protection Racket".
Sorry for the ramble, it's late.
Well... maybe.
And maybe not.
It's the same story with GNU readline(); is the library a vital part of the Pre Viewer? And, if it is, does this make the application a derivative work? Does Palm want to go to court to argue that the Pre Viewer is not a derivative work of muPDF?
I honestly would consider settling if faced with this. Unless I had me some "super lawyers", but, that's just me.
Just sayin'
We are talking about MAINTAINING code. Not writing new code.
Standard C did not come with a linked list, stack or queue library. Suck on that fact. If your job is to maintain a such a program, you really have to come to grips with this.