That was easy. The next problem will probably have the same answer.
Like hardware support? Linux is great and all, but it is difficult explaining to some people, who ran windows fine on their machine, why their hardware with windows-only drivers won't easily work in Linux without hitting the shell, typing "cryptic" commands and hoping it works.
Interestingly the first startup (if the application is not in RAM) is much slower. This is because of Windows, not the applications.
I don't get how that is because of Windows. In any O/S, the first load of any app would be slower if the app wasn't loaded into memory beforehand, if it wasn't preloaded in some manner, or if it was loaded before but is no longer in the O/S's disk cache.
What symmetric cipher, that ssh uses, even supports 4096 bit encryption? I thought bits that high were only supported for public/private keys but not the symmetric ciphers themself. According to the ssh manual page, it seems like the supported symmetric ciphers only go up to 256 bits.
If you use public-key authentication (and users don't have r/w access to the ~/.ssh/authorized_keys file, you can put restrictions on what each key can forward to.
The sshd manual page has a section named "AUTHORIZED_KEYS FILE FORMAT" that has details on the format of what goes in $HOME/.ssh/authorized_keys and what options are supported.
There is a rather long bug report open about this. Bug 76831. A workaround mentioned in it is to type: about:config in your address bar. Right-click the bottom pane, and add a new "boolean" value with the name config.trim_on_minimize, and set it to false, and then restart Firefox.
It allows people who don't have complete copies of a high-demand file can contribute to the swarm.
You probably haven't used gnutella in over 2 or 3 years. Modern gnutella clients have had partial file sharing for years now that allows people who don't have complete copies of a file to contribute to the swarm, complete with hash checking of each individual piece, not just the entire file (using "tiger tree" hashing or THEX, I think).
Searches are really fast, too, because you can immediately hop on the network and find most anything you need immediately.
That is true thanks to "dynamic querying" that some gnutella clients already have. Dynamic querying helps gnutella clients not waste as much bandwidth on extremely popular searches, so that a lot less of the searches for rare content would be dropped on the network (that would have been dropped from excessive bandwidth usage of popular queries or query replies).
Re:Slippery slopes are the most fun...
on
Cubicle Privacy
·
· Score: 1
Which would mean that if someone screams for help, no one would hear you, even next door?
but if no one is seeding it, then it is effectively dead - no one can download the entire file.
That is only accurate if 100% of the file isn't distributed among the peers of the torrent. It is possible for torrents to not have a seeder and still have people completely download it successfully, as long as 100% of the file is distributed among the peers participating in the torrent.
There are a lot of modems that will hang up if they receive "+++ATH0\r" in a continuous stream.
If those modems disconnect from that, does that mean one could also tack on ATDT911 after that +++ATH0 and make someone's vulnerable modem dial 911 after disconnecting from a single ping packet?
Since the time that they felt like cutting costs in modems by reducing the actual features they provide in the hardware itself and emulating those features in cheaper software ("drivers") that use the system's CPU power for them, such as what they did back during the "RPI" modem days.
"Rockwell Protocol Interface (RPI(TM)) is a technology that allows error correction and data compression (ECC) technologies to be performed in the PC host computer, rather than in the modem hardware, as has been done traditionally."... "RPI lowers the cost of traditional modem hardware by redistributing the Error Correction and Data Compression (ECC) processing load from the modem to the host computer, eliminating the need for external memories (RAM and EPROM) and allowing lower cost controllers to be used. This drive to lower the component cost was strongly driven by modem vendors desiring to offer the lowest possible end user price."
What type of internet connection do you have at the different locations, how fast is it, how much does it cost to per month, and how long would a restore from a remote location take?
It could be that those services are doing reverse resolves of your IPv6 address when you connect to them and are getting no response to the reverse resolve query sent to your DNS servers. So, maybe the issue lies with your DNS servers or some in-between device (NAT router or firewall) that is dropping IPv6 DNS queries. You could test this theory out by re-enabling IPv6 on your server and client machine but disabling reverse resolves in your services (such as ssh) on the server machine and testing the speed again.
Sadly, the last I heard about Suse's support is that it is for "installation" only (for their home-user targetted desktop). If you were able to successfully install Suse, your support ends there.
Like hardware support? Linux is great and all, but it is difficult explaining to some people, who ran windows fine on their machine, why their hardware with windows-only drivers won't easily work in Linux without hitting the shell, typing "cryptic" commands and hoping it works.
Why not at eleven?
So, what are you using now?
I don't get how that is because of Windows. In any O/S, the first load of any app would be slower if the app wasn't loaded into memory beforehand, if it wasn't preloaded in some manner, or if it was loaded before but is no longer in the O/S's disk cache.
What symmetric cipher, that ssh uses, even supports 4096 bit encryption? I thought bits that high were only supported for public/private keys but not the symmetric ciphers themself. According to the ssh manual page, it seems like the supported symmetric ciphers only go up to 256 bits.
The sshd manual page has a section named "AUTHORIZED_KEYS FILE FORMAT" that has details on the format of what goes in $HOME/.ssh/authorized_keys and what options are supported.
So that he can sleep better next to them.
There is a rather long bug report open about this. Bug 76831. A workaround mentioned in it is to type: about:config in your address bar. Right-click the bottom pane, and add a new "boolean" value with the name config.trim_on_minimize, and set it to false, and then restart Firefox.
Was he using that computer as foot rest for that time before he called you?
You probably haven't used gnutella in over 2 or 3 years. Modern gnutella clients have had partial file sharing for years now that allows people who don't have complete copies of a file to contribute to the swarm, complete with hash checking of each individual piece, not just the entire file (using "tiger tree" hashing or THEX, I think).
That is true thanks to "dynamic querying" that some gnutella clients already have. Dynamic querying helps gnutella clients not waste as much bandwidth on extremely popular searches, so that a lot less of the searches for rare content would be dropped on the network (that would have been dropped from excessive bandwidth usage of popular queries or query replies).
Which would mean that if someone screams for help, no one would hear you, even next door?
Xfce might also be a good choice.
That is only accurate if 100% of the file isn't distributed among the peers of the torrent. It is possible for torrents to not have a seeder and still have people completely download it successfully, as long as 100% of the file is distributed among the peers participating in the torrent.
That sounds like a power supply issue. Failing power supplies do weird things like that or spontaneously reboot a system out of the blue.
If those modems disconnect from that, does that mean one could also tack on ATDT911 after that +++ATH0 and make someone's vulnerable modem dial 911 after disconnecting from a single ping packet?
"Rockwell Protocol Interface (RPI(TM)) is a technology that allows error correction and data compression (ECC) technologies to be performed in the PC host computer, rather than in the modem hardware, as has been done traditionally." ... "RPI lowers the cost of traditional modem hardware by redistributing the Error Correction and Data Compression (ECC) processing load from the modem to the host computer, eliminating the need for external memories (RAM and EPROM) and allowing lower cost controllers to be used. This drive to lower the component cost was strongly driven by modem vendors desiring to offer the lowest possible end user price."
Where do I sign up?
What type of internet connection do you have at the different locations, how fast is it, how much does it cost to per month, and how long would a restore from a remote location take?
Which end of the CAT5 cable do I put the condom on?
Such as this one?
It could be that those services are doing reverse resolves of your IPv6 address when you connect to them and are getting no response to the reverse resolve query sent to your DNS servers. So, maybe the issue lies with your DNS servers or some in-between device (NAT router or firewall) that is dropping IPv6 DNS queries. You could test this theory out by re-enabling IPv6 on your server and client machine but disabling reverse resolves in your services (such as ssh) on the server machine and testing the speed again.
Sadly, the last I heard about Suse's support is that it is for "installation" only (for their home-user targetted desktop). If you were able to successfully install Suse, your support ends there.