Of course it's ugly. Of course you could build one your self. Of course
it looks like a PC.
Because that's all it is. This is just one geek who's put
together the hardware and software himself, made
from old PC bits + a small LCD screen.
He isn't some big company selling at a profit.
in fact he says
"...testers can purchase the Digital Jukebox from me at cost (+shipping) or I'm happy to help anyone build one themselves. The software is free. See the Hardware page for cost breakdown information."
You may not get a hard disk that small with the latest machines... but you might want to have a nice quiet low powered always on firewall machine (or whatever), using a 128MB CF disk instead of a hot rotating noisy hard disk drive.
A 65MB install is a great way to get going on that (you can pick up an IDE to CF adapter for next to nothing these days).
Well... classic LPD takes, essentially, a stream of pure ASCII characters. This may move from host to host. It is only at the final destination (where the printer is) that any filtering takes place (conversion for the appropriate printer). With the advent of postscript this ASCII stream may be a postscript file.
This has advantages of device independence... applications only need to know how to send ASCII or postscript.. so you don't need to install device drivers on all the client machines - the administrator can move queues/devices around without having to reconfigure/inform any clients.
This has disadvantages in the the client (application) knows nothing about the particular features of the printer - resolution, paper size, the fact that letter head is in tray 1, plain in tray 2 and so on.
CUPS (IPP) is a solution to this problem. It provides information about the printer associated with a queue to the client. This is done in a standard way so that the client only has to understand cups to be able to send output (ideally postscript, but text also) to CUPS. Again, the drivers are installed on the machine that hosts the device - which takes care of either converting the text/postscript to an appropriate format (for example, to print to your epson ink jet).
So with CUPS you have a great deal of control over you print out while retaining a lot of the advantages of the UNIX model (no need to install printer drivers all over the place).
To clarify.. R4 isn't speech as in "talk radio" - Radio 4 is like TV but with better pictures. I.e. you have programs about things - not just someone talking/interviewing/phoning in.
Wow! Did a lot of work on writing course materials in More... (switched from Cricket Presents IIRC). It was a good application. Sadly, the Mac Classic that we had has died.
Switched to MS Word for a while.... not really as quick as More...
.. Today, the courses notes are all in XML and processed using a DocBook tool chain...
Better would be an open standard for Calendar Access.
And there is one - CAP - it is a draft with no reference implementations, however (either a calendary or a server).
However the reefknot project is attempting to build libraries for CAP among other things.
Of course, a lot of development is needed. The dream should be a standards based server which supports CAP - but also offers MS Exchange emulation for "legacy" clients.....
... and a lot of resource to run.... and all your windows apps are displayed in their own window.
They idea behind Wine is that you do not need any MS code at all - so no MS licence fee is needed.
With Wine the windows app appears to be a native Linux app - uses the same window manager, can cut and paste etc. works over the network to your remote X display and all the other native Linux/UNIX/X goodies.
Of course, Wine isn't finished yet (especially without any MS code);-).
Re:A great example of open-source at work.
on
Five Years of KDE
·
· Score: 1
IIRC, NT 4.0 was release July/August 1996 - Windows XP around now...
Which makes it five years between NT 4.0 and Windows XP.
Which is a bit less impressive. Especially when you consider that it was the aim to replace the Windows 9x produce in 98,99,00...
NT 3.1 was around 1993.... 3.51 1995?
Re:New bug and feature request
on
Mozilla 0.9.5
·
· Score: 1
It does. Second option down on the right click menu.
To summarise, the names of the committee are on the report. It doesn't, HP/Perens say, that the individual committee members agree with the report. The take is that Peterson was opposed to the idea....
Re:Last stable release until February
on
KDE 2.2.1 Up
·
· Score: 1
How about notable? That has positive connotations.
Ami pro (samna pro?) was the word processor that every one tried to copy. Quatro pro was the spreadsheet that every one tried to copy.
The MS products were always "good enough".
We bought the MS products not because they were the best, but because everything was so unstable and unreliable on Windows 3.1x that we thought that there was more change of getting the MS office applications to work with the MS operating system - with the assumption that there actually might have been some testing on this platform - rather than taking different bits of software from different manufacturers and hoping they would all work*.
*then* the bundling started - for example, MS Office shipped with a licence for MS Mail... so one product subsidised the other. So it was very easy to buy the microsoft things. Even though they weren't technically the best.
* Of course, stability never improved, even when NT came out - so we switched to Linux;-).
Don't accept any connections over the wireless which aren't IPSEC.
Run IPSEC on your Access Point. An AP is just a computer i.e. just software... nothing (apart from lack of documentation etc.) to stop you using your Linux/BSD server as your AP.
Or just use IBSS (ad-hoc) if you can't make an IPSEC access point.
Indeed - it is "just software" so it can be changed... Which is the main point.
It is WEP (Wired Equivalency Protocol) that has been cracked. You might not even have been using that. It just needs to be replaced with something that works...
You can use ipsec (www.freeswan.org) as a replacement if you really need it
Consider the likelihood of someone bothering to listen in to your home network... probably not very likely unless you are an international terrorist or some such. I would expect that your wallet with its credit card is more likely to get stolen than to have someone else with a wireless card come and listen in.
Slashdot Mirror
Even better: www.digital.com redirects to Compaq which redirects to HP.
That is not linking then, is it.
It is my source.
And your source.
And everyone who has made some GPL contribution.
Lindows actually does relatively little development... it is based on Debian via Corel via Xandros.
If you cough up $99 dollars you can download it.
Except for the source.
The LGPL fork has only just happened. Lindows will be, as are Transgaming, still using the X11 code.
Because that's all it is. This is just one geek who's put together the hardware and software himself, made from old PC bits + a small LCD screen.
He isn't some big company selling at a profit. in fact he says
"...testers can purchase the Digital Jukebox from me at cost (+shipping) or I'm happy to help anyone build one themselves. The software is free. See the Hardware page for cost breakdown information."
also, snail mail spamming costs the sender - it is in their interest to send to people who they think might be a bit interested in the s ervice
A 65MB install is a great way to get going on that (you can pick up an IDE to CF adapter for next to nothing these days).
This has advantages of device independence... applications only need to know how to send ASCII or postscript.. so you don't need to install device drivers on all the client machines - the administrator can move queues/devices around without having to reconfigure/inform any clients.
This has disadvantages in the the client (application) knows nothing about the particular features of the printer - resolution, paper size, the fact that letter head is in tray 1, plain in tray 2 and so on.
CUPS (IPP) is a solution to this problem. It provides information about the printer associated with a queue to the client. This is done in a standard way so that the client only has to understand cups to be able to send output (ideally postscript, but text also) to CUPS. Again, the drivers are installed on the machine that hosts the device - which takes care of either converting the text/postscript to an appropriate format (for example, to print to your epson ink jet).
So with CUPS you have a great deal of control over you print out while retaining a lot of the advantages of the UNIX model (no need to install printer drivers all over the place).
To clarify.. R4 isn't speech as in "talk radio" - Radio 4 is like TV but with better pictures. I.e. you have programs about things - not just someone talking/interviewing/phoning in.
Switched to MS Word for a while.... not really as quick as More...
.. Today, the courses notes are all in XML and processed using a DocBook tool chain...
Go and get a basic book on TCP/IP. And read it.
Where in the IP packet is the MAC address?
When you've got the basics of "encapsulation" and mastered routing. Then go and find out about NAT.
How on earth does a post like this get a score of "2"....
Meeting scheduling - Evolution can do this
Notes - Evolution can do this
Public Folders - Any imap server can do this.
LDAP integration - Clients and Servers have Ldap integration.
Shared Calendars is the thing that is missing from open source applications.
But it is coming... reefknot.
Of course, the way exchange does it is proprietary - using nasty hard to reverse engineer MS-DCE functions.
There is a project to reverse engineer this though: http://sourceforge.net/projects/osexchange.
Better would be an open standard for Calendar Access.
And there is one - CAP - it is a draft with no reference implementations, however (either a calendary or a server).
However the reefknot project is attempting to build libraries for CAP among other things.
Of course, a lot of development is needed. The dream should be a standards based server which supports CAP - but also offers MS Exchange emulation for "legacy" clients.....
translucent.png
http://www.xfree86.org/~keithp/render/translucent. png
.
And, an alternative to X http://www.directfb.org/screenshots/gimp.png
Their successes had mistakes have informed subsequent generations and new designs.
Because, of the flaws in BIND - e.g. running as root - other, new designs, know not to do that.
BIND releases in the last few years do not have to and should not be run as root.
Anyway, I think your criticism of BIND is a bit harsh as most of the design flaws have been removed. Of course, there may still be bugs...
It is all about learning from mistakes. And BIND, being open, enables you to do that!
They idea behind Wine is that you do not need any MS code at all - so no MS licence fee is needed.
With Wine the windows app appears to be a native Linux app - uses the same window manager, can cut and paste etc. works over the network to your remote X display and all the other native Linux/UNIX/X goodies.
Of course, Wine isn't finished yet (especially without any MS code);-).
Which makes it five years between NT 4.0 and Windows XP.
Which is a bit less impressive. Especially when you consider that it was the aim to replace the Windows 9x produce in 98,99,00...
NT 3.1 was around 1993.... 3.51 1995?
It does. Second option down on the right click menu.
To summarise, the names of the committee are on the report. It doesn't, HP/Perens say, that the individual committee members agree with the report. The take is that Peterson was opposed to the idea....
How about notable? That has positive connotations.
Ami pro (samna pro?) was the word processor that every one tried to copy. Quatro pro was the spreadsheet that every one tried to copy.
The MS products were always "good enough".
We bought the MS products not because they were the best, but because everything was so unstable and unreliable on Windows 3.1x that we thought that there was more change of getting the MS office applications to work with the MS operating system - with the assumption that there actually might have been some testing on this platform - rather than taking different bits of software from different manufacturers and hoping they would all work*.
*then* the bundling started - for example, MS Office shipped with a licence for MS Mail... so one product subsidised the other. So it was very easy to buy the microsoft things. Even though they weren't technically the best.
* Of course, stability never improved, even when NT came out - so we switched to Linux ;-).
Run IPSEC on your Access Point. An AP is just a computer i.e. just software... nothing (apart from lack of documentation etc.) to stop you using your Linux/BSD server as your AP.
Or just use IBSS (ad-hoc) if you can't make an IPSEC access point.
Indeed - it is "just software" so it can be changed... Which is the main point.
WEP cracking isn't the end of the world.