M$ - Monumental Fail - Surely this isn’t true
Can anyone verify that this unbelievable claim is, in fact, true?
http://techdirt.com/articles/20080429/095514977.shtml
http://seattletimes.nwsource.com/html/microsoft/2004379751_msftlaw29.html
Tips, tricks, how-tos, opinions, and news regarding OpenSUSE Linux
Can anyone verify that this unbelievable claim is, in fact, true?
http://techdirt.com/articles/20080429/095514977.shtml
http://seattletimes.nwsource.com/html/microsoft/2004379751_msftlaw29.html
OK, I am totally stealing this one, but I wanted to share it (thx Steve).
“It’s official, Microsoft knows no shame. We used to think that the Zune tattoo guy was bad for publicity, but now it’s clear that the video promo team needs zero outside help in dragging whatever shred of dignity this company has through the mud. Whoever thought up this Bruce Springsteen-defiling “Rockin’ Our Sales” piece of garbage to promote the launch of Vista SP1 should be fired instantly and sued for defamation. It’s just that good. Video is naturally after the break.”
You HAVE to see just how low they can go.
Masochists click here for punishment.
Alrighty, folks. I gave a presentation at Utah Valley State College last night about a network security issue called ARP poisoning. It is the ability to hijack any computer’s connection on a local area network. The concept is that you force all traffic going to and from that machine through your own computer. You are then able to filter through that traffic and determine what the user is doing. It is possible to view passwords, and even change traffic as it goes through your computer. Even if they are on a secure website. It’s a fairly common method of attack, and is something to watch out for. I have compiled my notes into an article in the form of a 4-page PDF. If you want to take a look at how ARP Poisoning works, view the PDF here.
IM chat between myself and my good buddy Jason:
(03:11:36 PM) My Friend:http://www.ilovemyjournal.com/?action=personal_entry&eid=3675&user=1
(03:11:37 PM) My Friend: blogged.
(03:14:32 PM) Scott: Just read the whole thing, man… that is all too cool.
(03:14:52 PM) My Friend: (nod)
(03:15:10 PM) My Friend: Linux is like marriage….
(03:15:18 PM) My Friend: The more you're involved with it, the sweeter life becomes… 
(03:19:06 PM) Scott: Totally.
(03:19:41 PM) Scott: Windows is like being chained to a wild boar with barbed wire by the nut sack.
Things are looking good for folks wanting to switch to Linux without having to give up their Windows apps. Wine 1.0 is scheduled for a release in June. What does this mean?
Well, one of the primary focuses of this release is to work well with Photoshop. This is something that we’ve known for a couple of years, ever since I put together the Request an App Survey for Novell in January of 2006 (results here). Without question, the number one requested app was Photoshop. Apparently, for this reason, Google has provided some funding for the Wine folks.
Another hangup for people switching to Linux seems to be gaming support. I’d guess that the 1.0 release of Wine would likely support more games than it does now, or at least better support for the current list.
What will the Wine 1.0 release mean? Very likely, I would guess, more Windows users moving to Linux. Which is “A Good Thing.”
Read more about the Wine 1.0 release here
Hot off the openSUSE news room press:
After four regular weeks and one hack week after Alpha 2, we are very happy to announce openSUSE 11.0 Alpha 3.
The highlight of course is the reworked ZYpp framework, which gives you a much faster package management experience. This release also contains a new and professional installer theme.
A lot of packages were also updated to newer versions:
This is just the tip of the iceberg. There were 1855 checkins since Alpha2 - you can get a more complete list at Factory/News
Due to the huge amount of changes, there are also quite a few bugs that slipped in:
Find an up-to-date list under Bugs:Most_Annoying_Bugs_11.0_dev
We created the same media as with Alpha 2. They can all be downloaded at software.openSUSE.org/developer:
The next development release will be openSUSE 11.0 Beta 1 on April 17th (Roadmap).
If you use Linux for day-to-day computing, you likely use the secure shell, or ssh. If you are like me, you may grow weary of constantly having to type in passwords to access remote machines. Or maybe you have the perfect backup system, except that it uses ssh to transfer files, and requires you to type in a password (such as rsync or rdiff-backup). There is a way to access those machines without using a password. This technique should be used with care. I’d use it only on machines that I have access to, for example. You don’t want to set up passwordless access from a public machine to your production server, in other words. Use with caution.
The principle is that you generate a public and private key on the local machine. This will be whatever machine you are connecting from. You then transfer the public key to the remote machine. Then, when you ssh into the remote machine, it uses the keys to authenticate. You don’t type in a password, it just takes you straight to the shell prompt. How do we set this up?
Log into the machine you are going to connect from. Let’s say that your account is called ‘user’ and you are going to connect from a machine called ‘desktop’. Log in as ‘user’ on the ‘desktop’ machine and pull up a shell. Run this command. The stuff in red is what you do,not what you type:
[0218][user@desktop:~]$ ssh-keygen -t dsa Generating public/private dsa key pair. Enter file in which to save the key (/home/user/.ssh/id_dsa): [JUST PRESS ENTER HERE] Enter passphrase (empty for no passphrase): [JUST PRESS ENTER HERE] Enter same passphrase again: [JUST PRESS ENTER HERE] Your identification has been saved in /home/user/.ssh/id_dsa. Your public key has been saved in /home/user/.ssh/id_dsa.pub. The key fingerprint is: a5:25:c0:aa:fe:f3:9f:46:7a:23:e3:6e:10:ec:6f:d3 user@desktop [0218][user@desktop:~]$
Your keys are generated. On that machine, view /home/user/.ssh/id_dsa.pub. You will see something like this:
ssh-dss AAAAA3NzAC1kc3MAAACAANfnr9xkAks2u8Xd5I9nozzsXLKCYA8o9h3cMwL5QMcZGxz84Dyl3IyRwozv3I2xGwJAYyAHvJAS7AQmtFXtfmQts3dt2ZnlAmKj0TkC8pwDgvXJYzARJpCP2Zx7iwD/OCO3sTgT0wGwYtQrAcTeW5Tt6sSmQjEJ2rJj+Q5XA1xvAAAAFQDWcQ+OJRnk+jCYqESWqxHcyw74DwAAAIA9qAQyZrOJkjpzMSWAcliHvvuyCN8RInlgq+IwWynukOX7zYXcE2dJPopgpG3Aiiq/fxAQX5dUzXfSrL3KYftQOd/RNkAzMHAAzAJeQAA0wEt4uAjhGRwCOSg6wKMYJPYfVghnwIKARuSTUS8NjRXVKteHg7frOOHZwRGIm36pxgAAAIA8/CKLLn5QRctsvvvmvpOn2Xhek02z8K0YukYcXJOQ1FMTYWoHujA39sEAFsdx6Nq1t58lI2dsj6fpf7LOOvoYWtKQnTNRUptlOx27LTO9Q6DhKPV/93nLI/xFOFo/8twZ1TmpAgpAI3SQ9YCnX2A8H686OUwUPmY0kA+H8GKnug== user@desktop
What you need to do now, is determine the remote machine you are going to log into. Then, decide what user you are going to log in as on that machine. We are going to log in as a user called ‘admin’ on a server called ’server’. First, we will ssh into ’server’ as ‘admin’. Then, edit the file located at ~/.ssh/authorized_keys2. If it is not there, create it. All you need to do is paste the contents of the id_dsa.pub file from the ‘user’ account on the ‘desktop’ machine into the ~/.ssh/authorized_keys file for ‘admin’ on ’server’.
For example:
I go to my desktop, log in as ‘user’. I run ’ssh-keygen -t dsa’. It generates a ~/.ssh/id_dsa.pub file in my home directory.
I want to connect as ‘admin’ on a box called ’server’. I ssh in normally as ‘admin’ into the ’server’ machine. I edit the ~/.ssh/authorized_keys2 using my favorite text editor. I add the contents of the ~/.ssh/id_dsa.pub file from my desktop machine into the authorized_keys2 file on ’server’. I then save and quit. I then close all connections to ’server’. Then, I type ’ssh admin@server’, and hit ENTER. It drops me straight to a shell prompt.
This is a nice way to access a machine without having to type in the password every time. Only do this from machines that only you or authorized personnel have access to. Otherwise, you could have a li’l security problem.
Basic system packages are missing in the text-only install (and minimal graphic install) of OpenSUSE 10.3, from what I can tell. I installed a machine using the minimal graphical install. When finished, I found that basic packages like ‘man’ and ‘ping’ and ‘vim’ and some other basic commands were missing. The ‘crontab’ was missing, for the love of all that is holy.
Searching around, I found advice on how to install the missing packages, which is useless, because I’m already slightly familiar with package installation with YAST. What I would like to find is a plausable explanation for why such basic packages are missing from the text-only install. ESPECIALLY when such packages were installed in the text-only installs of previous versions of OpenSUSE.
Seriously, this is one of those “slap me in the face with a 2×4″ duh types of things. Why on the face of this planet would they make such a decision? If there is a good explanation, I am dying to know the answer. Anyone with some insight is more than welcome to share their thoughts.
Anyone wanna help me out here?
OK, so who hasn’t seen this? Nonetheless, it’s still worth revisiting:
Funny Linux command-lines with real output…
% cat “food in cans”
cat: can’t open food in cans
% nice man woman
No manual entry for woman.
% “How would you rate Quayle’s incompetence?
Unmatched “.
% Unmatched “.
Unmatched “.
% [Where is Jimmy Hoffa?
Missing ].
% ^How did the sex change operation go?^
Modifier failed.
% If I had a ( for every $ the Congress spent, what would I have?
Too many (’s.
% make love
Make: Don’t know how to make love. Stop.
% sleep with me
bad character
% got a light?
No match.
% man: why did you get a divorce?
man:: Too many arguments.
% !:say, what is saccharine?
Bad substitute.
% %blow
%blow: No such job.
% \(-
(-: Command not found.
$ PATH=pretending! /usr/ucb/which sense
no sense in pretending!
$ drink matter
matter: cannot create
Great stuff, tell you what.
[powered by WordPress.]
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
| « Apr | ||||||
| 1 | 2 | 3 | ||||
| 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 |
| 18 | 19 | 20 | 21 | 22 | 23 | 24 |
| 25 | 26 | 27 | 28 | 29 | 30 | 31 |
"I personally just encourage people to switch to KDE.
This 'users are idiots, and are confused by functionality' mentality of Gnome is a disease. If you think your users are idiots, only idiots will use it. I don't use Gnome, because in striving to be simple, it has long since reached the point where it simply doesn't do what I need it to do.
Please, just tell people to use KDE."
-Linus Torvalds
30 queries. 1.247 seconds
