I don't get why people think so much of unnamed 'international treaties'. They're just pieces of paper. Now, the Bill of Rights is just a piece of paper too, but it was there first, and frankly I'd prioritize it over a lot of other pieces of paper.
X resources are a nice, standard, elegant and pleasant way of configuring programs that use the X Window System. Is there any valid reason why GTK should choose to break this? Why is it that adding gimp*font: fixed to my X resource database doens't work as I expect it?
I agree that X resources are great, I use them for customizing everything from xterm to netscape (Netscape*blinkingEnabled:False:) but I've never seen anyone else ever make use of them, and I've never seen anything to set them automatically for people.
I don't know why, but it seems about 1% of the population is able to grasp the concept of a file format and edit a text file to a specific end. I guess the gtk/GNOME people decided they wanted to appeal to more of the general populace than this:)
D) A TCP/IP stack on a client desktop machine is generally a more mature solution than a SNA stack on a client desktop machine.
If you're connecting to a machine from a Windows box via SNA, you're using some kind of 3rd party stack. It gets used, primarily, to connect to mainframes. And not much else. So it doesn't get tested much, at least not on the same scale as TCP/IP gets tested every day.
I want a distribution that will use the absolutely newest version of some form of software (even newer than unstable for debian)
If you ever spot an out-of-date package in Debian unstable, please file a wishlist bug against the package. Instructions on how to submit a bug are outlined here.
In fact, please do it ASAP, because potato is freezing in a week.
Actually, because of the way JVC has licensed the patents pertaining to VCR's (which will probably expire in a few years anyway), broken Macrovision handling is a required part of the VCR specification. If your VCR doesn't care about Macrovision, you're extremely lucky - hold onto it.:)
Worse, the patents on Macrovision filtering are held by Macrovision (the company) - these patents are how Macrovision was able to shut down operations of most of those who produce macrovision filters.
The remaining video stabilizers on the market usually cost upwards of $100.
IMHO this is why the current patent system is so evil - it allows one company/person to dictate details of a standard to any competitor, in spite of the interests of consumers.
Centris 650's run Debian ok. Top takes around 20% CPU though.:)
You'll need to create another partition for Debian, and because there's no FIPS-like utility for Macs, you may need to reinstall MacOS to accomodate this.
I took some drive rails and some creativity and hooked another drive to the metal plate just to the left of the power supply. It works but you can't put any Nubus cards in afterwards.
You should know that Slink doesn't support the ethernet controller on the Centris 650's out of the box.
Also keep in mind that you can take 10 years off any mac's apparent age just by painting it glossy black.:)
New packages usually don't break existing packages. The only real concern is that the new package itself is broken, in which case it can be removed without anybody getting hurt.
300 miles is outside the range of ground wave, except for maybe high-power medium frequency waves where the bandwidth is very poor (think broadcast AM) and only under very good circumstances.
You'd have to either do satellite (earth-moon-earth anyone?:) or sky wave.
UHF and up is very practical with satellite because you can retain line of sight, however the cost could be prohibitive. Also going that far up in the sky and back down again increases latency.
Sky wave limits the frequencies you can use - the best frequency depends on whether it's day or night (at both locations), how many sunspots there are, etc, because only those frequencies bounce off the various layers of the ionosphere, which constantly varies. Also 300 miles would most likely put you in the skip zone (the area not covered by either sky wave or ground wave).
This is either absolutely incredible or incorrect, as it would be the first commercial wireless product to do multiple symbols per wavelength.
Perhaps it's 12 and 6 GHz instead of MHz?
If it is GHz, it's still incredible that they can go 30 miles with it and/or (which is it?:) do non-line-of-sight connections.
Radio waves bounce off of buildings really well, the signal is still quite intact, the only problem is you get multiple signals due to multiple bounce paths to you, each one slightly delayed by a different amount (speed of light isn't so fast anymore once you deal with picosecond waves).
Looking at the technical specs it appears they not only worked around this problem but somehow used it to their advantage.
Just be careful not to relicense code you didn't write.
I thought I heard a long time ago that KDE was planning to relicense all the code they own to the Artistic license, does anyone know what became of this?
No, at least not that I've heard of. A while back Klee Dienes created a revised source package format - check http://www.debian.org/News/weekly/19 99/11/mail for details. Once again, it's not a.deb, it's tarballs and patches to them. For source,.debs aren't practical because it would cost the maintainers and mirrors a lot of bandwidth every time they wish to make a one-line change that would only affect a.diff.gz and the binary.deb - especially for very large packages.
Also a list of source dependancies is kept by the build daemon machines - I forget where it's at though.
Equivs You can use this to tell dpkg that certain dependancies are fulfilled.
Rebuild the package yourself This is probably the cleanest way. Grab the package source, type dpkg-source -x file.dsc to extract it, cd to the directory it made, hack away on Makefiles or whatever, type fakeroot debian/rules binary (leave off fakeroot if you're actually root) and voila - fresh compiled packages. You might wish to put them on hold ("=" in dselect or 'echo packagename hold | dpkg --set-selections') so that the packaging system knows not to upgrade them.
fetchmail does not and does not plan to support the Microsoft Exchange Server wire protocol. The link you posted points to using fetchmail with Exchange's POP3 support.
However, POP3 does not an Exchange Server make, in fact most admins don't enable support for it because of bugginess. Exchange users commonly keep mailboxes (with dozens of subfolders including calendar and contact data) on the server. Compare it more with IMAP instead.
The calendar/contact/task data is relatively standardized - dozens of software vendors ship with vCard support in one way or another. The FIPS PUB 98 standard used by Microsoft Mail (yeah, not exchange, I know, but very similar) is a NIST standard, and although available, I can't find it as I write this post. I've looked through it earlier and it's very nondescript (every message must contain a Subject line, a To line, a From line, etc).
The info we need is how this information is accessed. We know it's TCP RPC-based, but anything further will either have to come from Microsoft or be reverse engineered.
That, and the Personal Folders file format would be very useful (we're all itching to find out how they implemented "Compressable Encryption":)
Slashdot Mirror
I don't get why people think so much of unnamed 'international treaties'. They're just pieces of paper. Now, the Bill of Rights is just a piece of paper too, but it was there first, and frankly I'd prioritize it over a lot of other pieces of paper.
I agree that X resources are great, I use them for customizing everything from xterm to netscape (Netscape*blinkingEnabled:False :) but I've never seen anyone else ever make use of them, and I've never seen anything to set them automatically for people.
I don't know why, but it seems about 1% of the population is able to grasp the concept of a file format and edit a text file to a specific end. I guess the gtk/GNOME people decided they wanted to appeal to more of the general populace than this :)
Underestimate the number of computers that only need to do one thing at your peril :)
That's ^2, not ^3.
Test this with a flashlight sometime.
I think what he was trying to say was that the 20th century isn't over yet, thus the "last" century was 1801-1901 :)
The sphere in which a given wave is moving outwards from the source is two dimensional (most textbooks illustrate it as a plane).
If I was a defendant, I would feel my right to a fair trial would be compromised if the judge had the public to please.
"They made me wear this!" "Well, we did do the nose... but she's a witch!"
Luckily the constitution lets citizens do random foo until a law is passed saying a particular piece of foo is illegal.
Until then, citizens of the US can enjoy the liberty of playing DVDs under the operating system of their choice to further their pursuit of happiness.
At least you can encode your cds to mp3 on both CPU's :)
D) A TCP/IP stack on a client desktop machine is generally a more mature solution than a SNA stack on a client desktop machine.
If you're connecting to a machine from a Windows box via SNA, you're using some kind of 3rd party stack. It gets used, primarily, to connect to mainframes. And not much else. So it doesn't get tested much, at least not on the same scale as TCP/IP gets tested every day.
If you ever spot an out-of-date package in Debian unstable, please file a wishlist bug against the package. Instructions on how to submit a bug are outlined here.
In fact, please do it ASAP, because potato is freezing in a week.
Worse, the patents on Macrovision filtering are held by Macrovision (the company) - these patents are how Macrovision was able to shut down operations of most of those who produce macrovision filters.
The remaining video stabilizers on the market usually cost upwards of $100.
IMHO this is why the current patent system is so evil - it allows one company/person to dictate details of a standard to any competitor, in spite of the interests of consumers.
You'll need to create another partition for Debian, and because there's no FIPS-like utility for Macs, you may need to reinstall MacOS to accomodate this.
I took some drive rails and some creativity and hooked another drive to the metal plate just to the left of the power supply. It works but you can't put any Nubus cards in afterwards.
You should know that Slink doesn't support the ethernet controller on the Centris 650's out of the box.
Also keep in mind that you can take 10 years off any mac's apparent age just by painting it glossy black. :)
There was a growing concensus for THHGTTG names last I checked.
New packages usually don't break existing packages. The only real concern is that the new package itself is broken, in which case it can be removed without anybody getting hurt.
Obscurity:
NetBIOS hidden shares being transmitted in share lists and hidden on the client end.
Minimum disclosure:
NetBIOS hidden shares having never been transmitted to the client at all.
(NetBIOS uses the former technique)
Linux.com technically already IPO'd - they're not a separate company, they are run by VA Linux.
Sorry to detract from the joke :)
It wouldn't be a problem if NSI hadn't screwed everything up in the first place by not differentiating com, net, and org properly.
You'd have to either do satellite (earth-moon-earth anyone? :) or sky wave.
UHF and up is very practical with satellite because you can retain line of sight, however the cost could be prohibitive. Also going that far up in the sky and back down again increases latency.
Sky wave limits the frequencies you can use - the best frequency depends on whether it's day or night (at both locations), how many sunspots there are, etc, because only those frequencies bounce off the various layers of the ionosphere, which constantly varies. Also 300 miles would most likely put you in the skip zone (the area not covered by either sky wave or ground wave).
Perhaps it's 12 and 6 GHz instead of MHz?
If it is GHz, it's still incredible that they can go 30 miles with it and/or (which is it? :) do non-line-of-sight connections.
Radio waves bounce off of buildings really well, the signal is still quite intact, the only problem is you get multiple signals due to multiple bounce paths to you, each one slightly delayed by a different amount (speed of light isn't so fast anymore once you deal with picosecond waves).
Looking at the technical specs it appears they not only worked around this problem but somehow used it to their advantage.
Just be careful not to relicense code you didn't write.
I thought I heard a long time ago that KDE was planning to relicense all the code they own to the Artistic license, does anyone know what became of this?
Also a list of source dependancies is kept by the build daemon machines - I forget where it's at though.
You can use this to tell dpkg that certain dependancies are fulfilled.
This is probably the cleanest way. Grab the package source, type dpkg-source -x file.dsc to extract it, cd to the directory it made, hack away on Makefiles or whatever, type fakeroot debian/rules binary (leave off fakeroot if you're actually root) and voila - fresh compiled packages.
You might wish to put them on hold ("=" in dselect or 'echo packagename hold | dpkg --set-selections') so that the packaging system knows not to upgrade them.
However, POP3 does not an Exchange Server make, in fact most admins don't enable support for it because of bugginess. Exchange users commonly keep mailboxes (with dozens of subfolders including calendar and contact data) on the server. Compare it more with IMAP instead.
The calendar/contact/task data is relatively standardized - dozens of software vendors ship with vCard support in one way or another. The FIPS PUB 98 standard used by Microsoft Mail (yeah, not exchange, I know, but very similar) is a NIST standard, and although available, I can't find it as I write this post. I've looked through it earlier and it's very nondescript (every message must contain a Subject line, a To line, a From line, etc).
The info we need is how this information is accessed. We know it's TCP RPC-based, but anything further will either have to come from Microsoft or be reverse engineered.
That, and the Personal Folders file format would be very useful (we're all itching to find out how they implemented "Compressable Encryption" :)
test