I am here, because i can read across the news, filter out the relevant part and i am informed very fast. On a video i cannot do this. i can try to skip through it, use fast-forward or similiar stuff, but then i miss out things. on a text i can see the important buzzwords whils scrolling over it, and slow down when its interesting. A video is much more time consuming, needs a workstation with speakers (most of the videos do) and of course a browser with the needed addons installed.
so do the interview, make a video for people who like to listen to the interview, and then provide a nice writeup in the news article, and only link the video.
as zfs can do raid, it might be a backup-solution. but then your backup cannot protect you from zfs-errors. which might be important, when some zfs-bug which fucks all your data is triggered. Never trust a single technique for live system AND backup system.
i think a off-dropbox copy is important. imagine something going wrong on the dropbox-server and pushing files full of garbage to both of your computers. now your two copies are as fucked as the copy on the dropbox-servers.
rsync with hardlinks is nice to make backup, but bad to manage it. Try deleting a old backup-set of about 20 GB "normal" files. with copy/hardlinks it takes a lot of time, with systems using archives (like difftar from duplicity) you just delete a small amount of files and you're having free space for more backups, again.
on the other hand you do not need to decide "full or incremental". every backup is a full one, so you do not delete one backupset and have a lot of useless incremental ones left.
for "oops i deleted the file" or "oops, i replaced some paragraph of text with a dumber version when i was drunk" this is quite useful backup. Easy to do, easy to recover. Only hard to remember and not automated. But this can be automated as well...
but then its going to be something more advanced, as rsync.//backups/$(date +%Y-%m-%d)/ anyway. so you got from stupid backup solution to inventing something good.
firefox had a time with just minor releases, they were called like 3.5, 3.6. Then they decided to change major things with each version, therefore incrementing the major-version-number as well to reflect this. because this can break stuff, they created ESR versions. so 10 will be supported, a upgrade from 10 to 17 will be smooth, but 10 -> 11 -> 12 ->... are NOT just minor changes, and 10 -> 17 will get A LOT of new features.
so you need a file for each firefox version, or you need to convince your users to use only esr-versions.
most services are paid per click, so until you click (and sometimes you even need to buy to get the page with the ads paid) its no use for the site owner, when you're seeing ads.
yeah, but then i can copy&paste the suggested ssh-keygen commandline as well. often i want to see the actual line and maybe the next (which is often the same hostkey but this time for the ip and not for the hostname).
first thing to look into: [enter]~? the ssh escape-key is ~, but only after a newline. and look out for deadkeys. ~? is a short help on this. There you can manage sub-connections and other stuff. ~. is very useful for terminating a ssh-process, which is still waiting for a network timeout.
And multiplexing a single ssh-connection: read the manpage of ssh for "ControlMaster". then a unix-socket which contains username and hostname in the filename is used to use a single ssh-connection for multiple streams (shells, transfers, etc.)
no, it could be a http keep alive connection inside the ssl-tunnel. and you do not know the traffic patterns of certain web-apps. On the other hand with ssh and screen you can reconnect fast and without noticing, if you need to.
But you should propably not risk a fight with the admins. either accept or discuss the rule.
thats the other way round. there the site knows the plaintext password and hashes it with a different salt on each authentication, challenging the user to know the hash of password+provided_salt, too.
Slashdot Mirror
- one person tweeting links without text all the time
- one person tweeting urls with always the same domain
I am here, because i can read across the news, filter out the relevant part and i am informed very fast. On a video i cannot do this. i can try to skip through it, use fast-forward or similiar stuff, but then i miss out things. on a text i can see the important buzzwords whils scrolling over it, and slow down when its interesting. A video is much more time consuming, needs a workstation with speakers (most of the videos do) and of course a browser with the needed addons installed.
so do the interview, make a video for people who like to listen to the interview, and then provide a nice writeup in the news article, and only link the video.
a trojan is no problem, the trojan horse, thats the problem! (and the greek soldiers inside)
> They have terms of use that forbid
gotcha.
they cannot forbid you anything, when you are not the customer. the company is not the customer, the employee is.
even children may be over 18.
they have no contract with the company, so they cannot forbid them to do so. But they can forbid their clients to give away login credentials.
this site is astroturfing. just look at the links mentioned in the articles ... they want to sell their product.
the rest of it is useful, but i would not link them anymore because of the spam for their products.
as zfs can do raid, it might be a backup-solution. but then your backup cannot protect you from zfs-errors. which might be important, when some zfs-bug which fucks all your data is triggered. Never trust a single technique for live system AND backup system.
i think a off-dropbox copy is important. imagine something going wrong on the dropbox-server and pushing files full of garbage to both of your computers. now your two copies are as fucked as the copy on the dropbox-servers.
rsync with hardlinks is nice to make backup, but bad to manage it. Try deleting a old backup-set of about 20 GB "normal" files.
with copy/hardlinks it takes a lot of time, with systems using archives (like difftar from duplicity) you just delete a small amount of files and you're having free space for more backups, again.
on the other hand you do not need to decide "full or incremental". every backup is a full one, so you do not delete one backupset and have a lot of useless incremental ones left.
for "oops i deleted the file" or "oops, i replaced some paragraph of text with a dumber version when i was drunk" this is quite useful backup. Easy to do, easy to recover. Only hard to remember and not automated. But this can be automated as well ...
but then its going to be something more advanced, as rsync ./ /backups/$(date +%Y-%m-%d)/ anyway. so you got from stupid backup solution to inventing something good.
of course it still does not cover drive failure.
just unpack the firefox tar.gz somewhere, run firefox from there and enjoy updates with user-rights. what is the hard part about this?
as there is no unsolved non-existent problem, its obvious that all non-existent problems are solvable.
no, you did not get the point of ESR releases.
firefox had a time with just minor releases, they were called like 3.5, 3.6. Then they decided to change major things with each version, therefore incrementing the major-version-number as well to reflect this. because this can break stuff, they created ESR versions. so 10 will be supported, a upgrade from 10 to 17 will be smooth, but 10 -> 11 -> 12 -> ... are NOT just minor changes, and 10 -> 17 will get A LOT of new features.
so you need a file for each firefox version, or you need to convince your users to use only esr-versions.
most services are paid per click, so until you click (and sometimes you even need to buy to get the page with the ads paid) its no use for the site owner, when you're seeing ads.
yeah, but then i can copy&paste the suggested ssh-keygen commandline as well. often i want to see the actual line and maybe the next (which is often the same hostkey but this time for the ip and not for the hostname).
no. There is a address-range for ipv4 in v6, so its no problem to transmit v4 packets in v6. The other way round is not possible without tunnels.
but normal people can easily change the domain for trashmail, but they cannot change their dyndns every other day. dns-names should be stable.
how is the server supposed to check, if the key is really using a password?
this is possible.
first thing to look into:
[enter]~?
the ssh escape-key is ~, but only after a newline. and look out for deadkeys. ~? is a short help on this. There you can manage sub-connections and other stuff.
~. is very useful for terminating a ssh-process, which is still waiting for a network timeout.
And multiplexing a single ssh-connection: read the manpage of ssh for "ControlMaster". then a unix-socket which contains username and hostname in the filename is used to use a single ssh-connection for multiple streams (shells, transfers, etc.)
no, it could be a http keep alive connection inside the ssl-tunnel. and you do not know the traffic patterns of certain web-apps.
On the other hand with ssh and screen you can reconnect fast and without noticing, if you need to.
But you should propably not risk a fight with the admins. either accept or discuss the rule.
[exec] screen -r on the remote shell or ssh screen -r ... mostly the same stuff, and already covered later by "directly running commands via ssh".
And to easily edit known_hosts there is an easy vim trick: vim .ssh/known_hosts +line_no (opens vim, jumps to line #line_no)
with this argument, it should be illegal for employers, when you tell them this stuff?
no, its only illegal to base the decision on this facts.
and a lot of time for uploading.
thats the other way round. there the site knows the plaintext password and hashes it with a different salt on each authentication, challenging the user to know the hash of password+provided_salt, too.