Technicus stultissimus: June 2009

Wednesday, June 24, 2009

Out of boot experience

Windows Welcome music (Windows XP)
C:\Windows\system32\oobe\images\title.wma
...

Hagamos un pequeño viaje al pasado, exactamente a 1994. Por aquellas días, Mark Malamud y Erik Gavriluk, que trabajan en el proyecto de Microsoft con nombre clave Cairo, se ponen en contacto con Brian Eno, el compositor de música electrónica que empezara con Roxy Music, y consiguen que componga los 6 segundos del sonido de inicio del que más tarde sería Windows 95. Brian cuenta en una entrevista concedida al San Francisco Chronicle que la idea le llegó en un momento en que estaba seco de ideas y le pareció realmente divertido y asombroso tratar de componer una pieza musical tan pequeña, que era como fabricar una pequeña joya. Después de medir minuciosamente los microsegundos de la pequeña pieza musical, cuenta Brian que al volver a los temas de 3 minutos le parecían océanos de tiempo. “The Microsoft sound” continuó acompañando el arranque de las versiones siguientes de los sistemas operativos de Redmond, si bien ya no se trataba del tema de Eno… ¡qué poco apego a la tradición!

Brian Eno, en 2006 (Wikipedia)
Quizás lo más singular de toda esta historia es que se cuenta que Brian compuso la pequeña pieza usando su ordenador Apple Machintosh.

Tuesday, June 23, 2009

Pruebalo, funciona

Hola,
karen_puta@hotmail.com ha decidido enviarte una invitación para probar nuestro servicio totalmente gratuito.
Te permite detectar todos los contactos que te han eliminado de su lista.
De este modo, podrás:
- Fijarte quién te ha eliminado de su lista.
- Limpiar tu MSN de quien no quiere hablarte.
- Recuperar contactos eliminados.
- Ver quién te tiene agregado que no tienes en tu lista.
Pruébalo aquí - CLICK AQUI
¡Te esperamos!

¡Sitio web reportado como falsificación!
Este sitio web en tumsn.net ha sido reportado como una falsificación web y ha sido bloqueada basándose en sus preferencias de seguridad.
Las falsificaciones de webs son diseñadas para intentar engañar al usuario para que revele información personal o financiera imitando fuentes en las que confia.
Introducir cualquier información en esta página web puede resultar en un robo de identidad o en otro tipo de fraude.

Sunday, June 21, 2009

Full virtualization on Phenom?

To check if the CPU supports full virtualization use command
#grep vmx /proc/cpuinfo
or look for info with
#cat /proc/cpuinfo

Saturday, June 20, 2009

Grub error on SCSI and SATA disks

Source
Grub Error 2 means "Selected disk doesn't exist"
Errors description

Errors Reported by the Stage 1

The general way that the Stage 1 handles errors is to print an error string and then halt. Pressing Ctrl-Alt-Del will reboot.

The following is a comprehensive list of error messages for the Stage 1:

"Hard Disk Error"
This error message will occur if the Stage 2 or Stage 1.5 is being read from a hard disk, and the attempt to determine the size and geometry of the hard disk fails.
"Floppy Error"
This error message will occur if the Stage 2 or Stage 1.5 is being read from a floppy disk, and the attempt to determine the size and geometry of the floppy disk fails. It's listed as a different error since the probe sequence is different than for hard disks.
"Read Error"
This error message will occur if a disk read error happens while trying to read the Stage 2 or Stage 1.5.
"Geom Error"
This error message will occur if the location of the Stage 2 or Stage 1.5 is not in the area supported by reading the disk with the BIOS directly. This could occur because the BIOS translated geometry has been changed by the user or the disk is moved to another machine or controller after installation, or GRUB was not installed using itself (if it was, the Stage 2 version of this error would have been seen during that process and it would not have completed the install).

Errors Reported by the Stage 1.5

The general way that the Stage 1.5 handles errors is to print an error number in the form "Error: " and then halt. Pressing Ctrl-Alt-Del will reboot.

The error numbers correspond to the Errors Reported by the Stage 2 in the listed sequence.

Errors Reported by the Stage 2

The general way that the Stage 2 handles errors is to abort the operation in question, print an error string, then (if possible) either continue based on the fact that an error occurred or wait for the user to deal with the error.

The following is a comprehensive list of error messages for the Stage 2 (error numbers for the Stage 1.5 are listed before the colon in each description):

1 : "Selected item won't fit into memory"
This error is returned if a kernel, module, or raw file load command is either trying to load it's data such that it won't fit into memory or it is simply too big.
2 : "Selected disk doesn't exist"
This error is returned if the device part of a device- or full filename refers to a disk or BIOS device that is not present or not recognized by the BIOS in the system.
3 : "Disk read error"
This error is returned if there is a disk read error when trying to probe or read data from a particular disk.
4 : "Disk write error"
This error is returned if there is a disk write error when trying to write to a particular disk. This would generally only occur during an install of set active partition command.
5 : "Disk geometry error"
This error is returned when a read is attempted at a linear block address beyond the end of the BIOS translated area. This generally happens if your disk is larger than the BIOS can handle (512MB for (E)IDE disks on older machines or larger than 8GB in general).
6 : "Attempt to access block outside partition"
This error is returned if a linear block address is outside of the disk partition. This generally happens because of a corrupt filesystem on the disk or a bug in the code handling it in GRUB (it's a great debugging tool).
7 : "Partition table invalid or corrupt"
This error is returned if the sanity checks on the integrity of the partition table fail. This is a bad sign.
8 : "No such partition"
This error is returned if a partition is requested in the device part of a device- or full filename which isn't on the selected disk.
9 : "Bad filename (must be absolute pathname or blocklist)"
This error is returned if a filename is requested which doesn't fit the syntax/rules listed in the Filesystem Description.
10 : "Bad file or directory type"
This error is returned if a file requested is not a regular file, but something like a symbolic link, directory, or FIFO.
11 : "File not found"
This error is returned if the specified filename cannot be found, but everything else (like the disk/partition info) is OK.
12 : "Cannot mount selected partition"
This error is returned if the partition requested exists, but the filesystem type cannot be recognized by GRUB.
13 : "Inconsistent filesystem structure"
This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem or bugs in the code handling it in GRUB.
14 : "Filesystem compatibility error, can\'t read whole file"
Some of the filesystem reading code in GRUB has limits on the length of the files it can read. This error is returned when the user runs into such a limit.
15 : "Error while parsing number"
This error is returned if GRUB was expecting to read a numbur and encountered bad data.
16 : "Device string unrecognizable"
This error is returned if a device string was expected, and the string encountered didn't fit the syntax/rules listed in the Filesystem Description.
17 : "Invalid device requested"
This error is returned if a device string is recognizable but does not fall under the other device errors.
18 : "Invalid or unsupported executable format"
This error is returned if the kernel image boing loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD).
19 : "Loading below 1MB is not supported"
This error is returned if the lowest address in a kernel is below the 1MB boundary. The Linux zImage format is a special case and can be handled since it has a fixed loading address and maximum size.
20 : "Unsupported Multiboot features requested"
This error is returned when the Multiboot features word in the Multiboot header requires a feature that is not recognized. The point of this is that the kernel requires special handling which GRUB is likely unable to provide.
21 : "Unknown boot failure"
This error is returned if the boot attempt did not succeed for reasons which are unknown.
22 : "Must load Multiboot kernel before modules"
This error is returned if the module load command is used before loading a Multiboot kernel. It only makes sense in this case anyway, as GRUB has no idea how to communicate the presence of location of such modules to a non-Multiboot-aware kernel.
23 : "Must load Linux kernel before initrd"
This error is returned if the initrd command is used before loading a Linux kernel. Similar to the above error, it only makes sense in that case anyway.
24 : "Cannot boot without kernel loaded"
This error is returned if GRUB is told to execute the boot sequence without having a kernel to start.
25 : "Unrecognized command"
This error is returned if an unrecognized command is entered into the command-line or in a boot sequence section of a config file and that entry is selected.
26 : "Bad or incompatible header on compressed file"
This error is returned if the file header for a supposedly compressed file is bad.
27 : "Bad or corrupt data while decompressing file"
This error is returned the run-length decompression code gets an internal error. This is usually from a corrupt file.
28 : "Bad or corrupt version of stage1/stage2"
This error is returned if the install command is pointed to incompatible or corrupt versions of the stage1 or stage2. It can't detect corruption in general, but this is a sanity check on the version numbers, which should be correct.

Super Grub Disk

BerliOS.de

We want Linux newbies to restore their new toy, but also help the Linux advanced user make potentially dangerous operations to the MBR in a safe way. Super Grub Disk is also a teaching tool to help you learn more about bootloaders and the booting process. After all, booting is the most important thing your computer does -- without the boot process, you would not have an operating system to use!

NewSID

Source
Von Mark Russinovich und Bryce Cogswell
NewSID herunterladen (68 KB)

NTFS-3g error: Hal.Storage.mount-fixed

org.freedesktop.Hal.Device.PermissionDeniedByPolicy:
org.freedesktop.Hal.Storage.mount-fixed
auth_admin_keep_always <-- (action, result).
Source

Hal is the hardware abstraction layer, which to my knowledge knows no policy by itself. That is usually the domain of "udev". Have a look at
http://www.reactivated.net/writing_udev_rules.html
http://gentoo-wiki.com/HOWTO_Customizing_UDEV
http://linuxcommand.org/man_pages/udev8.html
http://ftp.kernel.org/pub/linux/util...tplug/udev-FAQ
http://www.linuxfromscratch.org/lfs/...er07/udev.html
But maybe, just maybe, it is faster to have a look at your file ".hal-mtab-lock". What does it contain? "cat /etc/mtab" lists the mounted devices as you probably know. Why not renaming that ".hal-mtab-lock" for a test and try to access your DVD-drive...
-------------------------------
Windows-Partitionen einbinden
Bugs in Hal?
mein Fall:/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part2 / ext3 acl,user_xattr 1 1
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part8 /DATEN ntfs-3g users,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8 0 0
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part11 /IMAGES ntfs-3g users,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8 0 0
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part9 /MMEDIA ntfs-3g users,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8 0 0
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part10 /VMs ntfs-3g users,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8 0 0
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part1 /Win2k3 ntfs-3g defaults,users,locale=POSIX 0 0
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part3 /WinXP ntfs-3g defaults,locale=POSIX 0 0
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part7 /home ext3 acl,user_xattr 1 2
/dev/sdb9 /media/data1 ntfs-3g defaults,locale=POSIX 0 0
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part6 swap swap defaults 0 0

/dev/sdb9 wird gemounted ohne Probleme!

VirtualBox installation in OpenSuSE 11.1

Source
Installation of VirtualBox in openSUSE is made easy through the 1-click installation.

Friday, June 19, 2009

Extended n Filesystem Explorer

Explore2fs
Explore2fs is a GUI explorer tool for accessing ext2 and ext3 filesystems. It runs under all versions of Windows and can read almost any ext2 and ext3 filesystem. A beta version of Virtual Volumes is now available. This is a technology preview for Explore2fs 2. Virtual Volumes also has the ability to read ReiserFS and many other filesystems
explore2fs-1.08beta9.zip

Thursday, June 18, 2009

Windows x64 [6 en 1] DVD

Download

AMD X2 procesadores & juegos

Source

Localization: MUI and Regional Options

Source (unattended.msfn.org)

The Multilanguage User Interface (MUI) is used for localizing the OS interface elements (menus, dialogs windows, etc). MUI is not available for retail, and distributed among the volume license customers only. Home users cannot download MUI from the Microsoft web site. The only MUI available on the Microsoft web site is MUI for Windows Embedded. It cannot be used with Windows XP. MUI can be installed on the English Windows XP only.
In this section the Russian MUI is discussed, but the procedures can be applied to any other language version of MUI. There is a total of five CDs with several MUI languages per CD. For example, I'm interested in installing Russian language interface only. First of all, I would like to extract Russian MUI from the CD. This task can be accomplished by creating the Administrative Installation Point. All you need to do is to run setup.exe with the /a switch.

X:\muisetup.exe /a

Where X is the CD-ROM letter. Then follow the wizard and "install" (extract to the specified location) the language you need. This is your MUI installation source that can be used for the installation.
There's only one modification left. You need the updated muisetup.exe. If you have SP2 installed, navigate to your %SystemRoot%\mui folder and copy the muisetup.exe file from there to the MUI installation source (confirm overwrite prompt). If you don't have SP2 installed, you can extract muisetup.exe from the SP2 source (I hope you'll figure out how to do it). Once the updated muisetup.exe is placed in the MUI source, you can prepare for the installation.
...

Internet Explorer Enhanced Security

Windows Server 2003 shipped with security locked down by default. Part of this locking down is Internet Explorer Enhanced Security which is an extra layer of protection when surfing the internet using Internet Explorer (more information can be found by going here on a Windows Server 2003 [test] machine). Some people want to uninstall it.

Before we start, understand the way the uninstaller works. You can uninstall the entire Configuration, or just for users, or just for Administrators. The un-installer is set up like this:
Enhanced Security
->For Administrators
->For Users
If you have just random users connecting via Remote Desktop or Terminal Services, you may want to leave the Users configuration installed. This tutorial will be removing all of it.

Disabling IEES Configuration (source of this post)
Disabling Internet Explorer Enhanced Security Configuration

Click Start-- Control Panel -- Add/Remove Programs
Now click Add/Remove Windows Components
Click the check mark next to Internet Explorer Enhanced Security Configuration (to make it unchecked).
If you'd like to only disable it for Administrators or only for Users you can click Details and do so.
NEXT and voilá

Wipe the free space on media

Linux tools
By default, shred will overwrite the whole drive 25 times!
If you have a 100GB disk, that means writing 2500GB of data.
To just do it once, you would type (hda or sda!)
#shred -n 1 /dev/hda1
but bear in mind that this is less secure.
--------------------------------
# cat /dev/urandom > /dev/hda1
Break w/ Ctrl+c
--------------------------------
# dd if=/dev/urandom of=/dev/hda1
if u want zeros:
# dd if=/dev/zero of=/dev/hda1
---------------------------------
You can "delete" the journal with:
tune2fs -O ^has_journal /dev/hdXX
But can you shred the journal?
=======================
Windows XP Professional
The cipher command can be used to wipe the free space on a drive.
Use the /w: switch.
This command would wipe the free space on drive C:cipher /w:c==========================
http://www.dban.org/

Wednesday, June 17, 2009

Why doesn't Linux need defragmenting?

Source THANKS for the excellent explanation!!!

That is a question that crops up with regularity on Linux forums when new users are unable to find the defrag tool on their shiny new desktop. Here's my attempt at giving a simple, non-technical answer as to why some filesystems suffer more from fragmenting than others.

Rather than simply stumble through lots of dry technical explanations, I'm opting to consider that an ASCII picture is worth a thousand words. Here, therefore, is the picture I shall be using to explain the whole thing:

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
b  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
e  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
f  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
g  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
h  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
i  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
j  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
k  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
l  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
m  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
n  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
o  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
p  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
q  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
r  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
s  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
t  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
u  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
v  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
w  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
x  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
y  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
z  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

This is a representation of a (very small) hard drive, as yet completely empty - Hence all the zeros. The a-z's at the top and the left side of the grid are used to locate each individual byte of data: The top left is aa, top right is za, and bottom left is az. You get the idea, I'm sure. . .
We shall begin with a simple filesystem of a sort that most users are familiar with: One that will need defragmenting occasionally. Such filesystems, which include FAT, remain important to both Windows and Linux users: if only for USB flash drives, FAT is still widely used - unfortunately, it suffers badly from fragmentation.
We add a file to our filesystem, and our hard drive now looks like this:

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  T O C h e l l o . t x t a e l e 0 0 0 0 0 0 0 0 0 0
b  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 T O C
e  H e l l o , _ w o r l d 0 0 0 0 0 0 0 0 0 0 0 0 0 0
f  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

(Empty rows g-z ommitted for clarity)

To explain what you see: The first four rows of the disk are given over for a "Table of contents", or TOC. This TOC stores the location of every file on the filesystem. In the above example, the TOC contains one file, named "hello.txt", and says that the contents of this file are to be found between ae and le. We look at these locations, and see that the file contents are "Hello, world"
So far so good? Now let's add another file:

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  T O C h e l l o . t x t a e l e b y e . t x t m e z
b  e 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 T O C
e  H e l l o , _ w o r l d G o o d b y e , _ w o r l d
f  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

As you can see, the second file has been added immediately after the first one. The idea here is that if all your files are kept together, then accessing them will be quicker and easier: The slowest part of the hard drive is the stylus, the less it has to move, the quicker your read/write times will be.
The problem this causes can be seen when we decide to edit our first file. Let's say we want to add some exclamation marks so our "Hello" seems more enthusiastic. We now have a problem: There's no room for these exclamation marks on our filesystem: The "bye.txt" file is in the way. We now have only two options, neither is ideal:

We delete the file from its original position, and tack the new, bigger file on to the end of the second file.
We fragment the file, so that it exists in two places but there are no empty spaces.

To illustrate: Here is approach one

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  T O C h e l l o . t x t a f n f b y e . t x t m e z
b  e 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 T O C
e  0 0 0 0 0 0 0 0 0 0 0 0 G o o d b y e , _ w o r l d
f  H e l l o , _ w o r l d ! ! 0 0 0 0 0 0 0 0 0 0 0 0

And here is approach two:

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  T O C h e l l o . t x t a e l e a f b f b y e . t x
b  t m e z e 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 T O C
e  H e l l o , _ w o r l d G o o d b y e , _ w o r l d
f  ! ! 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

This is why FAT filesystems need defragging regularly. All files are placed right next to each other, so any time a file is enlarged, it fragments. And if a file is reduced, it leaves a gap. Soon the hard drive becomes a mass of fragments and gaps, and performance starts to suffer.

And then there is Linux. Which has a different philosophy. Windows filesystems are ideal if you have a single user, accessing files in more-or-less the order they were created in, one after the other. Linux, however, was always intended as a multi-user system: It was gauranteed that you would have more than one user trying to access more than one file at the same time. So a different approach was used. When we create "hello.txt" on a Linux filesystem, it looks like this:

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  T O C h e l l o . t x t h n s n 0 0 0 0 0 0 0 0 0 0
b  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 T O C
e  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
f  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
g  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
h  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
i  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
j  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
k  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
l  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
m  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
n  0 0 0 0 0 0 0 H e l l o , _ w o r l d 0 0 0 0 0 0 0
o  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
p  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
q  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
r  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
s  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
t  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
u  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
v  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
w  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
x  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
y  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
z  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

And then when another file is added:

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  T O C h e l l o . t x t h n s n b y e . t x t d u q
b  u 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 T O C
e  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
f  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
g  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
h  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
i  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
j  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
k  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
l  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
m  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
n  0 0 0 0 0 0 0 H e l l o , _ w o r l d 0 0 0 0 0 0 0
o  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
p  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
q  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
r  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
s  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
t  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
u  0 0 0 G o o d b y e , _ w o r l d 0 0 0 0 0 0 0 0 0
v  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
w  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
x  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
y  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
z  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

The cleverness of this approach is that the disk's stylus can sit in the middle, and most files, on average, will be fairly nearby: That's how averages work, after all.

Plus when we add our exclamation marks to this filesystem, observe how much trouble it causes:

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  T O C h e l l o . t x t h n u n b y e . t x t d u q
b  u 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 T O C
e  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
f  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
g  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
h  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
i  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
j  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
k  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
l  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
m  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
n  0 0 0 0 0 0 0 H e l l o , _ w o r l d ! ! 0 0 0 0 0
o  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
p  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
q  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
r  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
s  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
t  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
u  0 0 0 G o o d b y e , _ w o r l d 0 0 0 0 0 0 0 0 0
v  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
w  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
x  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
y  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
z  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

That's right: Absolutely none.

Windows tries to put all files as close to the start of the hard drive as it can, thus it constantly fragments files when they grow larger and there's no free space available.

Linux scatters files all over the disk so there's plenty of free space if the file's size changes. It also re-arranges files on-the-fly, since it has plenty of empty space to shuffle around.
Defragging a Windows filesystem is a more intensive process and not really practical to run during normal use.
Fragmentation thus only becomes an issue on Linux when a disk is so full that there just aren't any gaps a large file can be put into without splitting it up. So long as the disk is less than about 80% full, this is unlikely to happen.
It is also worth knowing that even when an OS says a drive is completely defragmented, due to the nature of hard drive geometry, fragmentation may still be present: A typical hard drive actually has multiple disks, AKA platters, inside it.
Let's say that our example hard drive is actually on two platters, with aa to zm being the first and an to zz the second:

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
b  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
e  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
f  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
g  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
h  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
i  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
j  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
k  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
l  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
m  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

   a b c d e f g h i j k l m n o p q r s t u v w x y z

n  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
o  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
p  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
q  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
r  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
s  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
t  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
u  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
v  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
w  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
x  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
y  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
z  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

The following file would be considered non-fragmented, because it goes from row m to row n, but this ignores the fact that the stylus will have to move from the very end of the platter to the very beginning in order to read this file.

   a b c d e f g h i j k l m n o p q r s t u v w x y z

a  T O C h e l l o . t x t r m e n 0 0 0 0 0 0 0 0 0 0
b  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
c  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
d  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
e  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
f  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
g  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
h  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
i  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
j  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
k  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
l  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
m  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 H e l l o , _ w o

   a b c d e f g h i j k l m n o p q r s t u v w x y z

n  r l d ! ! 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
o  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
p  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
q  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
r  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
s  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
t  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
u  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
v  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
w  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
x  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
y  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
z  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

I hope this has helped you to understand why no defragging software came with your Linux installation. If not, I'm always open to suggestions [Smiley]

You may also be interested in why deleting just isn't enough
---------------------------------
Why does Linux need defragmenting?

PC schaltet beim Herunterfahren nicht ab

Source

Achtung: dieser Tipp funktioniert nicht beim W2K-Server!
Eigentlich sollte der PC unter Windows 2000/XP beim Herunterfahren abschalten, sofern es
sich um ein ATX-Modell handelt. Dies ist aber dann z.B. nicht der Fall, wenn man W2K / XP
absichtlich ohne ACPI installiert. Um das Abschalten dennoch zu erreichen, muss man in
der Systemsteuerung unter "Energieoptionen" auf der Registerkarte "APM" die
"Unterstützung für das Advanced Power Management" aktivieren.
Wenn diese Registerkarte fehlt, muss man im Gerätemanager unter Ansicht / Ausgeblendete Geräte anzeigen aktivieren.
Dann wird in der Geräteliste auch der "Herkömmliche NT-APM Schnittstellenknoten" angezeigt und ist vermutlich deaktiviert.
Also aktivieren, danach wird in den "Energieoptionen" auch die Registerkarte "APM" angezeigt.
---------------------------------
Mehrere Möglichkeiten kommen hier in Betracht:
1. Der PC besitzt kein ATX Netzteil.
2. Der PC wurde ohne ACPI installiert. Hier muss APM (Unterstützung für Advanced Power Management) eingeschaltet werden.
Zu finden unter: Systemsteuerung / Energieoptionen
Dort APM einschalten. Jetzt sollte W2K den Rechner automatisch ausschalten können.
3. Schlüssel: HKEY_LOCAL_MACHINE / Software / Microsoft / WindowsNT / CurrentVersion / Winlogon
Wert: PowerdownAfterShutdown [REG_SZ] auf "1" stellen.
4. Im BIOS-Setup unter Powermanagement die Option soft-off by pwr-bttn (beim AWARD-BIOS) auf Instant-Off stellen.

Globovision & batanga.com

http://radio.batanga.com/sp/linuxusers.asp

The Problem with Multimedia & Linux distros

Source

I love Linux, but why does playing music have to be soo tough?

oldcpu

Global Moderator of openSuSE forums:

Why?? To avoid being sued. Novell is a big fat juicy target for those seeking to make money by suing an operating system supplier for illegal provision of codecs without payment of royalties.
In many cases private users are free to download and install codecs, but its not legal for operating system suppliers to provide the codecs.
Also, from what I have read its not the policy of Novell/SuSE-GmbH to provide proprietary software, drivers, nor codecs (and the MAJORITY of audio formats are in a proprietary format). This is because of the "open" in openSUSE. Note the emphasis on "open". That is because Novell/SuSE-GmbH in openSUSE try harder than most other distribution packagers to provide a distribution that follows the free open source philosophy:
Free Software Philosophy - openSUSE
... which means no automatic playing of most music as such music is stored in proprietary formats. Fortunately there are work arounds and ways to download and install codecs and applications to play such music, BUT its up to the openSUSE community to provide those means. And by "openSUSE community" I mean users like YOU and ME to contribute and find a way to make it easier. If we do not do this, (ie YOU and ME and other's like us), then NO ONE ELSE will.
caf4926 is doing his best in this guide to make this music installation easier for you in a Linux distribution (openSUSE) that places VERY HIGH importance on Free open source software and NO PROPRIETARY software, codecs, applications.
--------------------------------
Useful Terminal Commands & Solutions to Low Resolution Issues
Useful Guides for Ubuntu - Install Anything - Ubuntu:Chronicles

Compiz in KDE4.2

Thanks, Carl!
Compiz in KDE4.2 - Video
OpenSUSE Help - Video Downloads

Here I have uploaded a Video of Managing Packages in Yast - Software Management. Using Filter by Repository and doing Update All, you can choose 'if newer version avail' or 'unconditionally'.
If all Packages are showing with Blue text then the 'if newer ver' option is fine. But if there is a mix of Red and Blue use 'unconditionally'. This method of Package Management is especially helpful in Managing packages in repo's like those in the video - unstable or factory repo's. Or in multi-media situations where everytime you click on a package to update (eg;Amarok) say in Packman you get dependency errors. You can temporarily disable the check box for that and re-enable it before pressing accept. This lets you mark all the updates/upgrades/changes without interference. By the time you finish doing 'update all' in the various repo's - when you check at the end for dependencies, it is usually all OK. Read carefully any errors you do get, it is a bit confusing but it is usually fairly easy to opt your way through it. Or save the the error to file with the expert button.

Yast_Package]Yast Video- Package Management_Archived

Multi-media Subarea (OpenSUSE)

Welcome to the openSUSE Forums multimedia section!
This is our multimedia thread area, where support for multimedia is provided. This is intended to include questions about media applications, codecs (DVD, music, video, pdf) configuration (usage, bugs), etc ...
If you have sound working, but can not play many audio/video formats, it is possible these are proprietary formats that are not supported "after a fresh install" by openSUSE. More information on the openSUSE approach for packaged audio/video support can be found here:
Restricted Formats - openSUSE
OpenSUSE users can have 1st rate multimedia with the appropriate 3rd party applications and codecs installed. Information on installing 3rd party applications/codecs can be found here:
Multimedia - openSUSE-Community
More information for installing 3rd party "restricted formats" on different openSUSE versions can be found here:
Restricted Formats - openSUSE-Community
Note it often makes the above significantly easier if you have setup your repositories per this wiki here:
Repositories - openSUSE-Community
If you have a problem getting your sound card to work, please go here:
SDB:AudioTroubleshooting - openSUSE
If that that does not help you get your basic sound working, please post in this "multimedia" sub-forum, providing in your post the following information:
* provide the URLs (of a summary webpage) that are created by running the two diagnostic scripts noted here:
SDB:AudioTroubleshooting - openSUSE
* in a terminal, or xterm, or konsole, type: uname -a #and post output here
* in a terminal, or xterm, or konsole, type: rpm -qa | grep alsa #and post output here
* in a terminal, or xterm, or konsole, type: cat /etc/modprobe.d/sound #and post output here
* in addition in openSUSE-11.1 run the script /usr/sbin/alsa-info.sh and post here the output URL. Just the URL.

openSUSE-community.org/Restricted_Formats

Restricted Multimedia Formats (MP3, MPEG-4, etc.)
Note: Different copyright and patent laws apply differently depending on what country you are in; if you are unsure about a particular restriction or patent, you might consider applying for legal advice. This site does not offer legal advice. For more information about why some formats/codecs are restricted and why they don't ship out-of-the-box on openSUSE, read Restricted Formats.
To go through a simple wizard guiding you through the installation process of some additional multimedia codecs where necessary, simply click on one of the links below:

If you are using the KDE Desktop Environment

1-click installation

codecs-kde.ymp
Note: On 32-bit systems there'll be a dialog asking for about architecture change for libxine1 from from i586 to i686, accept that change.

If you are using the KDE Desktop Environment

Command line installation
Instead of using the 1-click you can install the codecs using a root terminal instead. Simply copy/paste the commands.
Add the required software repositories (one line command: zypper... ):

zypper addrepo
 http://ftp.skynet.be/pub/packman/suse/11.1 packman

zypper
addrepo http://suse.linuxin.dk/repo/11.1 libdvdcss

Install the packages (one line command: zypper... ):

zypper install ffmpeg flash-player gst-fluendo-mp3
k3b-codecs libdvdcss libxine1-codecs
phonon-backend-xine w32codec-all amarok-xine

If you are using the GNOME Desktop Environment:

codecs-gnome.ymp

his will enable you to have:

Flash
Java
Latest Amarok (with MP3 Support) for KDE, or Helix-Banshee for GNOME users
Encrypted DVD (libdvdcss)
Extra xine codecs, for MPEG-4 etc. (libxine1)
K3b with MP3 Support (k3b-codecs)
Win 32 Codecs (w32codec-all)

..as well as the option of installing many more applications (select Customise mode at the screen), including:

Opera
VLC
..and more

TROUBLESHOOTING

Sometimes things are not installed correctly. When that happens, you will find that you cannot play mp3, mp4, wmv using totem. At that point key to making it work correctly may not be so obvious. Here is what I did to get things working after the default install attempt went badly.

The key was to DISABLE all repositories but the packman and libdvdcss repositories... then remove all of the gstreamer packages and totem. Then do the install using the link from http://opensuse-community.org/Restricted_Formats/11.1. After this, re-enable all of repositories that you disabled before and then install totem. At that point everything works.

CARL'S PAGE
openSUSE 11.1_Install Slideshow

Multi-media and Restricted Format Installation

Source
Ben Kevan: Things to do after installing openSUSE 11.0
Multi-media and Restricted Format Installation Guide (openSUSE)

The purpose of this guide is to try and simplify what some have found to be a tricky process. There exist 'OneClick' options for this. Experienced users, at least as far as I am aware, do not use the 'OneClick' method. Keep in mind this was written for openSUSE 11.0 – You will be Working from Yast – Software – Software Management /& Repositories.
Some basic Repositories You Must Have:

Oss: Index of /distribution/11.0/repo/oss
Non-oss: Index of /distribution/11.0/repo/non-oss
Update: Index of /update/11.0

These repositories should be in your repositories list from Installation.
If Not, add them.
Additional Repositories You will need:

Packman: http://ftp.gwdg.de/pub/linux/misc/packman/suse/11.0/
Videolan VLC: Index of /pub/vlc/SuSE/11.0/

N.B. You will install one package from VLC: libdvdcss – That's it!! Then DISABLE this repo. Install this Package FIRST.
Now we can move on to everything else...
But first you need to know something of the installation process. Using Yast – Software – Software Management you can filter by Repositories and so go to the repository you need to work from. In our case it will be the Packman Repository. Installed Packages have a tick in the check box, Packages with Blue text mean they are updates – Packages showing Red text mean they are roll-backs. In the case of a New Installation it is unlikely that there will be any Red packages. If you see blue packages in the Packman repo – do the following:
- Looking at the menu buttons along the top of the GUI, select 'Package' and in the drop box select 'Update all in this list if Newer version Available'. Now accept.
**In Gnome this option is not available, but there is a work around to get the QT GUI here:
How To Get QT zypper GUI in GNOME YAST
If you receive a dependency error, look to accept the 'Vendor Change' option to resolve it.
For eg: Amarok from a default install of KDE will be a Blue package and will update, but you will need to confirm 'Vendor Change' to Packman. If you can't work out what to do, save the error to file by clicking the 'other' button in the error box. Then paste that info in to a question in the forum.
When Yast finishes it will ask if you want to install more? Select Yes.
Now filter by repository again and go back to Packman.
You now need to mark for installation the following – some of which may auto add to install by dependency as you work through the list.
libavcodec52
libdvdnav4
libdvdplay0
libdvdread4
libffmpeg0
libquicktime0
libxine1
libxine1-codecs
libxvidcore4
smplayer
vlc
w32codec-all
xine-ui
xvidcore
This list is by no means comprehensive and depending on your system and chosen desktop environment, you may need further adjustment. You may also want to use the search box and type realplayer to install this too. It should be noted that FLASHPLAYER is installed by default at install and should just work. If it does not - Post your question/problem in the forum.

Thanks to RedDwarf for this check list:
Check your multimedia problem in ten steps
'oldcpu' has a 'sticky' here:
Multimedia sub-area - openSUSE Forums

ONECLICK's openSUSE 11.0
KDE: http://opensuse-community.org/codecs-kde.ymp
GNOME: http://opensuse-community.org/codecs-gnome.ymp

Multi-media and Restricted Format Installation Guide

UPDATED FOR openSuSE 11.1

The purpose of this guide is to try and simplify what some have found to be a tricky process. There exist 'OneClick' options for this. Experienced users, at least as far as I am aware, do not use the 'OneClick' method. Keep in mind this was written for openSUSE 11.0 (NOW UPDATED FOR 11.1) – You will be Working from Yast – Software – Software Management /& Repositories.
Some basic Repositories You Must Have:

These repositories should be in your repositories list from Installation.
If Not, add them.
Additional Repositories You will need:

Packman: Index of /pub/linux/misc/packman/suse/11.1
Videolan VLC: http://download.videolan.org/pub/vlc/SuSE/11.1

N.B. You will install one package from VLC: libdvdcss – That's it!! Then DISABLE this repo. Install this Package FIRST.
---------------------------------
Now we can move on to everything else:
But first you need to know something of the installation process. Using Yast – Software – Software Management you can filter by Repositories and so go to the repository you need to work from. In our case it will be the Packman Repository. Installed Packages have a tick in the check box, Packages with Blue text mean they are updates – Packages showing Red text mean they are roll-backs. In the case of a New Installation it is unlikely that there will be any Red packages. If you see blue packages in the Packman repo – do the following:
- Looking at the menu buttons along the top of the GUI, select 'Package' and in the drop box select 'Update all in this list if Newer version Available'. Now accept.
**In Gnome this option is not available, but there is a work around to get the QT GUI here:
QT zypper GUI in GNOME YAST
If you receive a dependency error, look to accept the 'Vendor Change' option to resolve it.
For eg: Amarok from a default install of KDE will be a Blue package and will update, but you will need to confirm 'Vendor Change' to Packman. If you can't work out what to do, save the error to file by clicking the 'other' button in the error box. Then paste that info in to a question in the forum.
When Yast finishes it will ask if you want to install more? Select Yes.
Now filter by repository again and go back to Packman.
You now need to mark for installation the following – some of which may auto add to install by dependency as you work through the list.
amarok-packman (if kde or you want this media player) + amarok-xine
libavcodec52
libdvdnav4
libdvdplay0
libdvdread4
libffmpeg0
libquicktime0
libxine1
libxine1-codecs
libxvidcore4
smplayer
vlc
w32codec-all
xine-ui
xvidcore
This list is by no means comprehensive and depending on your system and chosen desktop environment, you may need further adjustment. You may also want to use the search box and type realplayer to install this too. It should be noted that FLASHPLAYER is installed by default at install and should just work. If it does not - Post your question/problem in the forum.
Thanks to RedDwarf for this check list:
Check your multimedia problem in ten steps
'oldcpu' has a 'sticky' here:
Welcome to multimedia sub-area

ONE CLICK OPTION
KDE: http://opensuse-community.org/codecs-kde.ymp

Gnome: http://opensuse-community.org/codecs-gnome.ymp

__________________

For all other apps:
Search an application & One Click Install openSuSE 11.1 KDE

NTFS access in Linux

Use ntfs-config to allow full access to the NTFS partitions
If errors:
$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sdb5': Operation not supported
Mount is denied because NTFS is marked to be in use. Choose one action:
Choice 1: If you have Windows then disconnect the external devices by
clicking on the 'Safely Remove Hardware' icon in the Windows
taskbar then shutdown Windows cleanly.

Choice 2: If you don't have Windows then you can use the 'force' option for
your own responsibility. For example type on the command line:

mount -t ntfs-3g /dev/sdb5 /media/PAGEFILE_ -o force

Or add the option to the relevant row in the /etc/fstab file:

/dev/sdb5 /media/PAGEFILE_ ntfs-3g force 0 0

Instant Boot & Inteligent Energy Saver

Quelle

Hier gibt es zwei Optionen: zum einen den "fast mode" und zum anderen den "regular mode". Aktiviert man Instant Boot in einem der beiden Modi, so startet der PC beim nächsten Herunterfahren selbstständig neu, bootet abermals und fährt sich dann erst herunter.

Anschließen bootet der PC deutlich schneller, der Vorgang erinnert an ein Aufwachen aus dem Standby-Modus (S3 STR) bzw. Ruhezustand (regular mode). Der Test dieser Funktion ist denkbar simpel - wir booten das System einmal mit aktiviertem Instant Boot und einmal ohne.

Modus	Dauer
Instant Boot (fast mode)	16 s
Instant Boot (regular mode)	21 s

Standby S3 (STR)	15 s
Standby S4 (Ruhezustand)	20s

Die Quintessenz aus unserem Vergleich ist schnell gezogen: zeitlich bringt Instant Boot nichts. Die sogar geringfügig längere Bootzeit ist bedingt durch das automatische Laden des Instant Boot Clients beim Windowsstart - was man nicht vermeiden kann. Liest man sich die Dokumentation zu diesem Feature einmal genau durch und sieht nicht nur das individualistische Video dazu an, eröffnet sich einem auch schnell wieso.

So soll und kann Instant Boot gar nicht schneller als der klassische S3- oder S4-Modus sein. Denn Instant Boot bedient sich exakt dieser Modi. Der einzige Vorteil soll das vermeiden von „accumulated garbage data" sein. Was das genau für überflüssige Daten sein sollen und welche Vorteile deren Vermeidung für den Anwender genau bringten erklärt ASRock leider nicht. Wir konnten in der Praxis keinen Unterschied entdecken.

Intelligent Energy Saver

Intelligent Energy Saver, kurz IES, soll (elektrische) Energie sparen, indem einzelne Phasen der CPU-Versorgung - je nach Bedarf - zu oder abgeschalten werden. Zwar bewirbt ASRock dieses Feature nicht explizit in Zusammenhang mit dem A780GM-LE, allerdings wird es von dem passenden Softwaretool unterstützt. Aktiviert man IES in dem Tool, so wird angezeigt, wie viele Phasen der Versorgung momentan aktiv sind. In unserem Fall waren im Idle zwei Phasen aktiv und unter Last vier Phasen.

In der Übersicht nun die Energieersparnis, gemessen mit der 9350e-CPU:

Modus	IES	normal	delta
Idle	55	57	2 W / 3,5%
Vollast	115	115	0 W / 0%
3 Kerne Last	106	108	2 W / 1,9%
2 Kerne Last	94	99	5 W / 5,6%
1 Kerne Last	79	85	6 W / 7%

Wie zu erwarten, bringt IES nur im Vollast-Modus nichts. Aber ist bereits nur einer von drei Kernen nicht belastet ,macht sich ein Unterschied bemerkbar. Gerade bei der Belastung nur eines CPU-Cores, einer sicher häufigen Alltagssituation, lassen sich immerhin ca. sieben Proeznt Strom einsparen. Somit ist es auf alle Fälle empfehlenswert, dieses Feature auch zu verwenden.

Tuesday, June 16, 2009

Monday, June 15, 2009

Restricted Formats -OpenSuSE 11.1

opensuse-community.org

In openSUSE 11.1 all our codec handling will be done using One-Click-Install. This provides a simple wizard to guide you through everything, and you have to install absolutely nothing extra to be good to go!
One-Click Install: Hassle-Free Installation of Software
openSUSE contains thousands of packages that are often spread across various repositories. Great places like the Packman project, Guru’s RPM site and of course the openSUSE Build Service provide thousands of packages for openSUSE users. The problem, however, is frequently the hassle of locating the package, adding the repository that contains it, and then finally installing the package. This can be a tiresome process particularly if you are intending to use many packages from different repositories (say, in the Build Service).

One Click Install removes this hassle.

Dual boot probs: XP & 2k3

Source (remastered)

The boot partition in M$-speak is where the OS resides ie. winnt/windows folder.
The system partition is where the master boot record points to and contains ntdetect, ntldr and boot.ini.
In M$DOS days it was exactly the opposite. Boot files where the boot partition and where the OS was, was called system partition.

Windows 2003 in D: and reinstallation of Windows XP on C: instead of an installed Windows 2003
XP has since been running flawlessly, though win 2003 on D: will not boot any longer, that is, i see the dual boot screen, but if i go for win 2003, it will try to boot up, but at the precise moment when the moving win2003 logo (that moving bar from left to right) should show up, the PC reboots, leaving me no option other than boot in win XP.

All the important boot files from D: win2003 are on C:, so when you redid it, you killed them and that's why 2003 on D: no longer boots. You can likely fix this by doing a "Repair" of Win2003.
So when you formatted you erased the boot related files of Win2003. Now XP was the lone owner of the pc world.
To get the 2003 master boot record back you run the 2003 recovery console command FIXMBR.

To fix the 2003 versions of ntldr and ntdetect of win2003 on C: (over winXP)
Start the Win2003 installCD and when give the choice between new or repair, you will choose repair.

After this you should be able to multiboot both OS's. If there is a issue it will be with the boot.ini.
Either use the recovery console Bootcfg utility to autocorrect the boot.ini or manuall edit it:
Add the following line to c:\boot.ini of winXP and try to boot in Windows 2003:

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows 2003 Server" /fastdetect

It assumes that win2k3 is installed on Partition 2 on your first harddrive.
If it doesn't work restart the windows 2003 installation CD, after first reboot remove the Windows 2003 Disk & edit boot.ini & add the above line.

Active Directory Federation Services (ADFS) in Windows
How To ADFS
ADFS es un funcionalidad agregada en la versión de Windows Server 2003 R2, si bien hay muchos que conocen un concepto básico, vamos a ver cómo poner en práctica y cuáles son los escenarios a aplicar para un uso de ADFS.
ADFS es una implementación de Web Servicies (WS) en especial de WS-Federation que permite interactuar con cualquier otra federación que cumpla con los mismos tipos de WS.
Lo que nos permite ADFS es la posibilidad hacer relaciones de confianza entre federaciones (dominios) donde la autenticación se hace en cada federación usando estos WS.En los escenarios de Internet el escenario aplicable es el de SSO. Como ejemplo simple nos permite tener una federación con recursos (resource partner) y otra federación de cuentas (Account partner).En la federación de recursos de debe declarar aplicaciones (basadas en Token - legacy o Aplicaciones ADFS Aware basadas .Net 2.0) y que son accedidas desde internet por una federación asociada. En este caso la federación asociada cumple el rol de Federación de cuentas, donde cuenta con un repositorio de validación (Active Directory o ADAM)
Lo más importante de todo esto es que un usuario para acceder a la aplicación de la federación de recursos, usara una cuenta de su dominio y a través de nuestra relación de federaciones podrá acceder y validarse a nuestra aplicación sin la necesidad de hacer VPN o relación de confianza entre dominios ni forest.
El beneficio principal de este esquema es que la federación encargada de la aplicación no se tiene que preocupar de la administración de cuentas, claves de los usuarios externos que la consumen, ya que se validan en su propio dominio.

Web Services management

Windows Remote Management (WS-Management)

Windows Remote Management (WinRM) service implements the WS-Management protocol for remote management. WS-Management is a standard web services protocol used for remote software and hardware management. The WinRM service listens on the network for WS-Management requests and processes them. The WinRM Service needs to be configured with a listener using winrm.cmd command line tool or through Group Policy in order for it to listen over the network. The WinRM service provides access to WMI data and enables event collection. Event collection and subscription to events require that the service is running. WinRM messages use HTTP and HTTPS as transports. The WinRM service does not depend on IIS but is preconfigured to share a port with IIS on the same machine. The WinRM service reserves the /wsman URL prefix. To prevent conflicts with IIS, administrators should ensure that any websites hosted on IIS do not use the /wsman URL prefix.
...

Source Thanks, Mathevs!!
I dived into WS-Management support in Vista / ~~Longhorn Server~~ Windows Server 2008 this weekend. There are a couple of caveats if you want to enable remote WS-Management based access to these machines. Support for remote management is also built into Windows Server 2003 R2.
WS-Management specification allows remote access to any resource that implements the specification. Everything accessed in a WS-Management world is a resource, which is identifiable by a URI. The spec uses WS-Eventing, WS-Enumeration, WS-Transfer and SOAP 1.2 via HTTP.
Since remote management implementation in Windows acknowledges all the work done in the WMI space, you can simply issue commands in terms of URIs that incorporate WMI namespaces.

For example, the WMI class or action (method) is identified by a URI, just as any other WS-Management based resource. You can construct access to any WMI class / action using the following semantics:

http://schemas.microsoft.com/wbem/wsman/1/wmi denotes a default WMI namespace accessible via WS-Management
http://schemas.microsoft.com/wbem/wsman/1/wmi/root/default denotes access to root/default namespace

Since the majority of WMI classes are in root/cimv2 namespace, you should use the following URI to access those:

http://schemas.microsoft.com/wbem/wsman/1/wmi/root/cimv2

User access in NTFS partitions

Change in /etc/fstab
users,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8 0 0
to
defaults 0 0
or
users, umask=000 0 0

If you are the only user of this machine you could use
uid=',fmask=177,dmask=077
to give you full exclusive access.
Code:

/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part7 /home        ext3       acl,user_xattr        1 2
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part3 /WinXP     ntfs-3g    users,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8 0 0
/dev/disk/by-id/ata-ST3250310AS_6RYFZQM8-part8 /DATEN    ntfs-3g    uid={user name},fmask=177,dmask=077,locale=de_DE.UTF-8 0 0

fmask is a umask just for files. The 'x' bit is cleared for owner. The 'wx' bits are cleared for group and others.
dmask clears the write permission bit for group and others. The 'x' bit is different for directories. It allows you to enter a directory.

After installing openSUSE 11.0

Things to do...

Setting up repositories:

For my machine I added the following repositories for my final build:
http://download.videolan.org/pub/vlc/SuSE/11.0 (VLC Media, restricted formats)
http://download.opensuse.org/repositories/KDE:/KDE4:/STABLE:/Desktop/openSUSE_11.0/ (KDE 4 Stable) Note: if this was not my workbox, I would actually do Unstable to get KDE 4.1
http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_11.0/ (Wine, for windows emulation)
http://download.opensuse.org/repositories/KDE:/Backports/openSUSE_11.0/ (KDE Backports, updates to Amarok and other KDE Applications)
http://download.opensuse.org/repositories/X11:/XGL/openSUSE_11.0/ (Compiz Fusion, staying up to date and hip with the most recent Compiz builds, I highly recommend since it’s constantly developed on)
http://ftp.skynet.be/pub/packman/suse/11.0/ (Packman, xinelibs / codecs and so much more)
http://download.opensuse.org/repositories/mozilla/openSUSE_11.0/ (Firefox, recent builds of Firefox)
http://download.opensuse.org/repositories/GNOME:/Community/openSUSE_11.0/ (Gnome Community, I use for Pidgin and GIMP)
http://download.opensuse.org/repositories/OpenOffice.org:/STABLE/openSUSE_11.0/ (OpenOffice is an important application for me since I use it daily for word processing or spreadsheets, keeping it up to date allows for the best compatabilities with people using restricted formats like xls/doc)
http://download.opensuse.org/repositories/Education:/desktop/openSUSE_11.0/ (Education - For Bluefish)
http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_11.0/ (KDE Stable repository, not sure why because not many changes should happen to the 3.5.9 family)

Here is a quick screenshot of my repositories:

(Note: I am running KDE, if you are running GNOME, I highly recommend the following repo:
http://download.opensuse.org/repositories/GNOME:/STABLE/openSUSE_11.0/)
(Note: If you are running an NVIDIA card, setup the following repository:
ftp://download.nvidia.com/opensuse/11.0/)
(Note: If you are running an ATI card, setup the following repository:
http://www2.ati.com/suse/11.0/)
(Note: If you are running a wireless card that has a requirement for MadWifi, setup the following repository:
http://madwifi.org/suse/11.0/)

Setup your Video Card (if you have more configurations to do, ie Nvidia / ATI)
Install the packages that are associated with your NVIDIA / ATI card.

For me I downloaded the NVIDIA Driver from nvidia.com and installing running:
sudo sh NVIDIA-Linux-x86-173.08-pkg1.run
Since I had some issues with the 173.14 driver.

...

Partitionieren & Swap-Erstellung

Partitionieren (OpenSuSE)

Fremde Partitionen und fstab
Wenn die Partitionierung von YaST durchgeführt wird und andere Partitionen im System erkannt werden, werden diese Partitionen ebenfalls in die Datei '/etc/fstab' aufgenommen, um den mühelosen Dateizugriff zu ermöglichen. Diese Datei enthält alle Partitionen im System sowie deren Eigenschaften, beispielsweise Dateisystem, Einhängepunkt und Benutzerberechtigungen.

Hier ein Beispiel von Partitionsdaten in der Datei '/etc/fstab':

/dev/disk/by-id/scsi-SATA_SAMSUNG_SV4002H0413J1FR917614-part1 /data1 auto noauto,user 0 0
/dev/disk/by-id/scsi-SATA_SAMSUNG_SV4002H0413J1FR917614-part5 /data2 auto noauto,user 0 0
/dev/disk/by-id/scsi-SATA_SAMSUNG_SV4002H0413J1FR917614-part6 /data3 auto noauto,user 0 0

Unabhängig davon, ob es sich um Linux- oder FAT-Partitionen handelt, werden diese Partitionen mit den Optionen noauto und user angegeben. Dadurch kann jeder Benutzer diese Partitionen nach Bedarf einhängen oder aushängen. Aus Sicherheitsgründen gibt YaST hier nicht automatisch die Option exec ein, die zur Ausführung von Programmen vom Speicherort aus erforderlich ist. Wenn sie jedoch Programme von diesem Ort aus ausführen möchten, können sie die Option manuell eingeben. Diese Maßnahme ist erforderlich, wenn sie Systemmeldungen, wie beispielsweise Meldungen über einen „fehlerhaften Interpreter“ oder „verweigerte Berechtigungen“, erhalten.

[bearbeiten]

Verwenden von Swap

Mittels Swap wird der physikalisch verfügbare Arbeitsspeicher erweitert. Ihnen steht dadurch über das physikalische RAM hinaus mehr Arbeitsspeicher zur Verfügung. Die Arbeitsspeicherverwaltungssysteme der Kernels vor Version 2.4.10 benötigten Swap als Sicherheitszugabe. Wenn Ihr Swap damals nicht zweimal so groß war wie Ihr RAM, kam es zu erheblichen Leistungseinbußen. Auf heutige Systeme treffen diese Einschränkungen allerdings nicht mehr zu.

Wenn dem Kernel der Arbeitsspeicher nicht ausreicht, lagert er selten verwendete Arbeitsspeicherseiten aus. Den aktiven Anwendungen steht dadurch mehr Arbeitsspeicher zur Verfügung und selbst das Zwischenspeichern läuft reibungsloser ab.

Versucht eine Anwendung jedoch, sämtlichen Arbeitsspeicher für sich zu reklamieren, den sie nur irgendwie erhalten kann, kann es mit dem Swap-Speicher zu Problemen kommen. Wir sollten uns hierzu drei der wichtigsten Szenarien näher ansehen:

System ohne Swap
Die Anwendung erhält den gesamten Arbeitsspeicher, der, auf welche Weise auch immer, freigegeben werden kann. Der gesamte Cache-Speicher wird freigegeben. Dadurch verlangsamen sich alle anderen Anwendungen. Nach einigen Minuten tritt der "Out of Memory-Killermechanismus" des Kernels in Kraft und der Prozess wird abgebrochen.
System mit mittelgroßem Swap (128 MB – 256 MB)
Zunächst lässt die Leistung des Systems wie bei einem System ohne Swap nach. Sobald das gesamte physikalische RAM aufgebraucht ist, wird auch auf den Swap-Speicher zurückgegriffen. An diesem Punkt wird das System sehr langsam; die Fernausführung von Kommandos wird unmöglich. Je nach Geschwindigkeit der Festplatten, die den Swap-Speicher stellen, verbleibt das System etwa 10 bis 15 Minuten in diesem Zustand, bevor das Problem vom "Out of Memory-Killer" des Kernels endgültig "gelöst" wird.
System mit großem Swap (mehrere GB)
Auf einem solchen System sollten sie besser keine Anwendung ausführen, die völlig außer Rand und Band gerät und den Swap-Speicher grenzenlos nutzt. In einem solchen Fall würde das System Stunden brauchen, um sich wieder zu regenerieren. Sehr wahrscheinlich treten in diesem Fall bei anderen Prozessen Timeouts und Fehler auf, wodurch das System in einem undefinierten Zustand zurückbleibt, selbst wenn der fehlerhafte Prozess abgebrochen wird. Am besten schalten sie das System in einem solchen Fall aus und wieder ein und versuchen es wieder hochzufahren. Sehr viel Swap-Speicher ist nur dann sinnvoll, wenn sie eine Anwendung verwenden, die diese Menge an Swap tatsächlich benötigt. Solche Anwendungen (wie Datenbanken oder Bildbearbeitungsprogramme) verfügen in der Regel über eine Option, mit der sie den benötigten Festplattenspeicher direkt abrufen können. Die Verwendung dieser Option ist auf jeden Fall einem übergroßen Swap-Speicher vorzuziehen.

Falls ihre Anwendungen nicht außer Kontrolle geraten, aber dennoch nach einiger Zeit mehr Swap erforderlich ist, können sie den Swap-Speicher auch online erweitern. Wenn sie eine Partition als Swap-Speicher vorbereitet haben, fügen Sie diese Partition einfach mit Hilfe von YaST hinzu. Falls sie auf keine Swap-Partition zurückgreifen können, können sie den Swap-Speicher auch durch eine Swap-Datei erweitern. Swap-Dateien sind im Vergleich zu Partitionen in der Regel langsamer. Im Vergleich zu physikalischem RAM sind jedoch beide Swap-Methoden extrem langsam. Der tatsächliche Geschwindigkeitsunterschied ist allerdings nicht so bedeutend, wie es den Anschein hat.
---------------------------------

Erstellen des swapbereichs

Beim Partitionieren wird üblicherweise des Partitionstyp 0x82
gewählt. Dann mit mkswap die Partition "formatieren" und gegebenenfalls den
Eintrag in der /etc/fstab anpassen. Und manuell mit swapon (wieder)
anschalten.
Man kann auch ein Swapfile anlegen:
dd if=/dev/zero of=/path/to/swapfile bs=1024 count={Größe in KB}
eine leere Datei in gewünschter Größe anlegen,
mit mkswap formatieren und mit swapon anschalten

Inaktivieren des Swapbereichs
Manuell mit swapoff
und/oder vor einen Reboot
den Eintrag in der /etc/fstab auskommentieren.
Auch vor dem Neupartitionieren machen.
--------------------------------

wiki.ubuntuusers.de/Swap
Linux bietet auch die Möglichkeit, anstatt einer Partition den Swap Space in eine Datei zu legen, die sogenannte "Auslagerungsdatei". Dieses Verfahren nutzt z.B. Windows standardmäßig.
Um eine Auslagerungsdatei zu erstellen, ist ein Terminal ^[1] notwendig. Mit

sudo mkdir -p /var/cache/swap/

legt man den angegebenen Verzeichnispfad komplett an.
Danach kommt

sudo dd if=/dev/zero of=/var/cache/swap/swap0 bs=1M count=512

Den Wert hinter count= sollte man natürlich anpassen, er gibt die Größe der Auslagerungsdatei in Megabyte an.

Experten-Info:

Die Zeile besagt, dass eine Datei mit dem Namen swap0 mit 512MB Größe angelegt wird. Die Größe ergibt sich aus 1M*512=512MiB, wobei 1M=1 Mio. Byte entspricht. Es ist wichtig, dass die Datei so angelegt wird, da sie dann auf der Festplatte durchgehend nur durch leere Speicherstellen besteht und keine zufälligen Daten enthält.
Mehr in den Manpages von Shell/dd und zero.

Um den Speicher zu formatieren, gibt man folgendes ein:

sudo mkswap /var/cache/swap/swap0

Die Warnung kann man dabei ignorieren. Um nicht jedem beliebigen User die Möglichkeit zu geben, den Swap auszulesen, sollte man

sudo chmod 0600 /var/cache/swap/swap0

ausführen. Das setzt die Rechte für alle Benutzer außer root auf "kein Lesen, kein Schreiben, kein Ausführen".
Damit das System über den Swap Bescheid weiß, gibt man einfach das hier ein:

sudo swapon /var/cache/swap/swap0

Ein Neustart ist nicht notwendig.
Sicher will man die Auslagerungsdatei auch nach einem Neustart wieder verwenden. Dazu einfach die Datei /etc/fstab in einem Editor mit Rootrechten ^[2] öffnen und dort diese Zeile anhängen:

/var/cache/swap/swap0    none    swap    sw      0 0

Swap Partition nachträglich erstellen
Falls man die Swap Partition neu erstellen möchte und das bei der Installation vergessen hat, sollte man wie folgt vorgehen:

Man erstellt eine Swap-Partion ^[3] und formatiert diese Mithilfe des mkswap Befehls. Anschließend kann die Partition eingebunden werden. Um die Partition dauerhaft einzubinden, öffnet man die Datei /etc/fstab mit Rootrechten ^[2]. In der Datei fügt fügt man folgende Zeile ein, welche vorher angepasst werden muss.

 none swap sw 0 0

Wenn man den Ruhezustand nutzen möchte, muss man zuerst die UUID herausfinden, das geht über folgenden Befehl im Terminal ^[1]:

ls /dev/disk/by-uuid -al

Danach muss die Datei /etc/initramfs-tools/conf.d/resume mit Rootrechten ^[2] editiert werden und folgende Zeile eingefügt und mit der eigenen UUID angepasst werden:

RESUME=UUID=

Zuletzt muss das initrd-Image neu geschrieben werden, das geht über folgenden Terminalbefehl:

sudo update-initramfs -u

Swap überwachen
Mit

sudo swapon -s

kann man jederzeit den Stand des Swap überprüfen.

Alternativ hilft hier unter GNOME das Programm "System-> Systemverwaltung -> Systemüberwachung". Im Reiter "Ressourcen" kann man die Belegung von Swap sehen. Man kann auch ein Systemmonitor Applet zum Gnome Panel hinzufügen.

Nutzt man KDE 3, so kann man das Programm
"K-Menü -> System -> Systemüberwachung - Performancemonitor" nutzen.
Bei KDE4 ist das entsprechende Programm im Menü in
"Programme -> System -> Systemmonitor" zu finden, der Reiter "Systemlast" zeigt mitunter auch die Swapnutzung an.

Unter Xfce kann man sich die Belegung von Swap anzeigen lassen, in dem man den Menüpunkt "Applications -> System -> Systemüberwachung", Reiter "Ressourcen" wählt.
Oder, in dem man zum Xfce Panel das Plugin "Systemauslastung" hinzufügt.
---------------------------------

10.5.1.2 Anlegen einer Swap-Datei

Um eine Swap-Datei zu erstellen, müssen Sie eine Datei öffnen und soviele Bytes hineinschreiben, wie die Swap-Datei groß sein soll. Hierfür können Sie gut den Befehl dd (4.5.4) verwenden.

enterprise:~ # dd if=/dev/zero of=/swap bs=1024 count=16384
16384+0 Records ein
16384+0 Records aus
enterprise:~ # ls -l /swap
-rw-r--r--    1 root     root     16777216 Nov 17 12:15 /swap

Das Gerät /dev/zero ist praktisch das Gegenteil von /dev/null. Während /dev/null praktisch ein WOM (Write Only Memory) ist, der alle Informationen schluckt und Sie nicht wieder hergibt, ist /dev/null ein unendlich großer Datenträger, auf dem aber nur Nullen stehen. Der obige Befehl liest praktisch 16384 Blöcke mit 1024 Bytes von diesem Gerät und schreibt Sie in die Datei /swap.

Nach dem Anlegen der Datei sollten Sie sicherheitshalber mit dem Befehl sync (10.3.4) die Dateisysteme wieder synchronisieren.

Auf keinen Fall darf die Swap-Datei eine Lücke besitzen. Die Blöcke der Datei müssen sich hintereinander auf der Platte befinden.

10.5.1.3 Swap-Bereich formatieren
Nach dem Anlegen der Partition bzw. der Datei muß diese für den Einsatz als Auslagerungsspeicher vorbereitet werden, d. h. formatiert werden.
Hier kommt der Befehl mkswap zum Einsatz.

mkswap -c GERÄTENAME

GERÄTENAME steht für den Namen der Partition bzw. der Datei. Der Schalter -c ist optional und bewirkt, daß der Swap-Bereich bei der Formatierung auf fehlerhafte Blöcke untersucht wird.

Nehmen wir als Beispiel mal die oben angelegte Swap-Partition. Mit dem folgenden Befehl wird sie als Swap-Bereich formatiert.

enterprise:~ # mkswap -c /dev/hdb1
Swapbereich Version 1 mit der Größe 279642112 Bytes wird angelegt

Die Swap-Datei wird analog angelegt. Nur daß anstatt des Gerätenamens, der Dateiname angegeben wird.

enterprise:~ # mkswap -c /swap
Swapbereich Version 1 mit der Größe 16773120 Bytes wird angelegt
enterprise:~ # sync

Nach dem Einrichten einer Swap-Datei sollten Sie immer das Dateisystem mit sync synchronisieren um sicherzugehen, daß die Informationen auch physikalisch auf die Platte übertragen worden sind. Dies ist bei der Swap-Partition natürlich nicht nötig.

10.5.1.4 Swap-Bereich aktivieren und deaktivieren
Damit der neue Swap-Bereich auch vom System benutzt wird, muß er aktiviert werden. Dafür ist der Befehl swapon verantwortlich. Analog dazu können Sie natürlich mit dem Befehl swapoff einen Swap-Bereich auch deaktivieren. Anhand des Befehls free (12.8.5) kann die Veränderung des Swap-Bereichs beobachtet werden.

Als Beispiel schauen wir uns doch mal die Einbindung unserer Swap-Datei ins System an.

enterprise:~ # free
          total       used       free     shared    buffers     cached
Mem:        513448     466992      46456          0      63500     258672
-/+ buffers/cache:     144820     368628
Swap:      1028120          0    1028120
enterprise:~ # swapon /swap
enterprise:~ # free
          total       used       free     shared    buffers     cached
Mem:        513448     467032      46416          0      63528     258672
-/+ buffers/cache:     144832     368616
Swap:      1044496          0    1044496
enterprise:~ # swapoff /swap
enterprise:~ # free
          total       used       free     shared    buffers     cached
Mem:        513448     467036      46412          0      63536     258672
-/+ buffers/cache:     144828     368620
Swap:      1028120          0    1028120

Auf jeden Fall sollten Sie eine Swap-Datei nur dann löschen, wenn Sie sie vorher mit swapoff deaktiviert haben.

Wie üblich ist dieser Befehl nicht von Dauer. Nach einem Reboot ist der Swap-Bereich wieder inaktiv. Die Swap-Bereich müssen also bei jedem Start initalisiert werden. Dies geschieht mit dem Befehl swapon -a in einer der Startdateien.

swapon -a liest die Informationen aus der Datei /etc/fstab aus. Wenn dort Informationen des Typs

/dev/hda6       swap    swap    sw 0 0

bzw.

/dev/hdb1       swap    swap    pr=42 0 0

dann werden die jeweiligen Swap-Bereiche beim Booten initialisiert. Sie sollten für jeden neu angelegten Swap-Bereich einen Eintrag zur /etc/fstab hinzufügen.

Multiboot-Umgebung mit Windows XP, Windows 2000, SuSE Linux und Debian Sarge

Sunday, June 14, 2009

Thursday, June 11, 2009

Coral Content Distribution Network

The Coral Content Distribution Network, sometimes called Coral Cache or Coral, is a free peer-to-peer content distribution network. Coral uses the bandwidth of volunteers to mirror web content, often to avoid the Slashdot Effect or to reduce the load on websites in general.

Operation
One of Coral's key goals is to avoid ever creating 'hot spots' of very high traffic, as these might dissuade volunteers from running the software out of a fear that spikes in server load may occur. It achieves this through an indexing abstraction called a distributed sloppy hash table (DSHT); DSHTs create self-organizing clusters of nodes that fetch information from each other to avoid communicating with more distant or heavily-loaded servers.

The sloppy hash table refers to the fact that coral is made up of concentric rings of distributed hash tables (DHTs), each ring representing a wider and wider geographic range (or rather, ping range). The DHTs are composed of nodes all within some latency of each other (for example, a ring of nodes within 20 milliseconds of each other). It avoids hot spots (the 'sloppy' part) by only continuing to query progressively larger sized rings if they are not overburdened. In other words, if the two top-most rings rings are experiencing too much traffic, a node will just ping closer ones: when a node that is overloaded is reached, upward progression stops. This minimises the occurrence of hot spots, with the disadvantage that knowledge of the system as a whole is reduced.
Requests from users are directed to a relatively close node, which then finds the file on the coral DSHT and forwards it to the user.

Usage
A website can be accessed through the Coral Cache by adding .nyud.net to the hostname in the site's URL, resulting in what is known as a 'coralized link'. So, for example, http://example.com becomes http://example.com.nyud.net.

History
The project has been in an open beta testing phase since March 2004, during which it has been hosted on PlanetLab, a large scale distributed research network of 400 servers but not, as ultimately intended, third party volunteer systems. Of those 400 servers, about 275 are currently running Coral. The source code is freely available under the terms of the GNU GPL.
Coral Cache gained notoriety in the aftermath of the 2004 Indian Ocean earthquake, when it was used to allow access to otherwise inaccessible videos of the resulting tsunami.

Problems
Some web filtering software packages, such as Websense and OpenDNS, block access to the Coral Cache as it is seen as a form of proxy avoidance.

About backups

Real men don't use backups, they post their stuff on a public ftp server and let the rest of the world make copies. --- Linus Torvalds

The Helmer Story

Microwulf: A Personal, Portable Beowulf Cluster
Clustermonkey
bccd.cs.uni.edu
littlefe project
-----------------------------------------------
The story of Helmer: A linux cluster in a IKEA Helmer cabinet
Helmer (Ikea of Sweden)
Width: 28 cm
Depth: 43 cm
Height: 69 cm
Helmer Data Sheet

Disk cloning in progress. I used Fedora 8, and the command "dd" to clone the discs from the bootable System rescue CD disc.

> dd if=/dev/sda of=/dev/sdb

Done! I use the software Dr Queue as batch job dispatcher.
All connected to a 8 port 3 com gigabit switch.
Common storage using nfs to a FreeNAS server running on a Via C7 machine (that just need 20 W power .. another story :)
Instead of power switch I used a simple cable to the "pwr" jumper on motherboard. (Wires taped on right side)

Instructions of how I did the DrQueue setup is here:
DrQueueHOW-TO.pdf
The most amazing is that this machine just cost as a better standard PC, but has 24 cores that run each at 2.4 Ghz, a total of 48GB ram, and just need 400W of power!! This means that it hardly gets warm, and make less noise then my desktop pc.
Render jobs that took all night, now gets done in 10-12 min.
..next one will be in red.. www.sfe.se

Update 1:
It has been crazy last days. I have got allot of questions regarding details, construction and software setup. I'll do a better page as soon... or I build the Red Helmer II :) Would be fun to use the AMD 16 core Bulldozer cpu x 6 = 96 core in a box :)))
If a hardware manufacturer/pr-guy happened to read this. I'm very happy to receive hardware play around with ;)
Update 2:
It has happened! I filled the ram, and all boards begun to swap. During this the power consumption was up to 800W. Running now a while, I noticed that H1 board (bottom one) gets hotter than the other boards. I think this is because the other boards are cooled from the fan below also.
Update 3:
Well, general planning and webpage have begun on Red Helmer II - thank you Google :)
Update 4:
First alternative hardware for Red Helmer is selected, and will do about 12Tflops. (64x times faster then Helmer 1) and cost about the same :) Stay tuned for more!
Update 5:
A hardware god may help me, and then Helmer II will do about 50 TFLOPS!!!! please please, may the force be with me :)

More Helmer pics here

Blog
Some render tests result here:
The storming sea scene file 24 frames in resolution 4000x4000 pixels.
- On a MacPro 2 x DualCore Xenon 2.66 Ghz with 4 GB ram
took 552 minutes (9.2 h)
- Helmer did same 24 frames in 4k format in 64 min.
Some approximate numbers give Helmer a floating point capacity of 186 Gflops
A better spelled version of this page is here (by Dan - Thanks)

Some design test of Helmer II here

My PC is on fire!

See the Video!
(Excerpts from "Elephants dream")

STORY: The video features our two characters, Proog and Emo, locked in a dispute over Emo’s broken PC. Proog, a computer repairmen, refuses to fix Emo’s computer until his last bill has been paid. But, Emo refuses to pay Proog’s previous bill until his computer is working!

LYRICS:
Hello, it's true
Your Dell, won't boot
And I made, something that runs
To show you, that you're screwed

Hello, hello
My PC, it won't load
I will not pay, your lousy bill
And I throw it at the wall

When you leave my screen it fades to grey
Turned it on today, now my data's gone away
When you make my PC load and play
Then your lousy bill I'll pay

My PC, My PC, My PC, is on fire!
My PC, My PC, My PC, is on fire!

I know, it seems
My bill's extreme
And I bought
Something to fix the colors, on your screen

Hello, hello
My PC, it won't load
I will not pay, your lousy bill
And I throw it at the wall

When you leave my screen it fades to grey
Turned it on today, now my data's gone away
When you make my PC load and play
Then your lousy bill I'll pay

My PC, My PC, My PC, is on fire!
My PC, My PC, My PC, is on fire!
This video, called "My PC Is On Fire", was inspried by Brookers hilarious "Crazed Numa Fan" video. It's a parody of "Ma Ya Hi", the English version of "Numa Ye" that pays tribute to the Dell laptop that burst into flames in Japan. It uses animation footage from the Elephants Dream creative commons movie project.

Read about and see the complete original animation film

Wednesday, June 10, 2009

32-bit or 64-bit processor?

How to determine if your system contains a 32-bit or 64-bit processor.
1.  On the Start menu:
   1a. For Windows* 2000, select Settings and then
       select Control Panel.
   1b. For Windows* XP or later operating systems,
       select Control Panel.
   1c. Open the 'System' applet (you may first have to
       select 'Switch to Classic View').
2.  Select the 'Hardware' tab.
3.  Select the 'Device Manager' button.
4.  The processor type will be indicated by the value under
   the 'Computer' section on the 'General' tab.

Tuesday, June 9, 2009

AMD64 technology

Source

AMD64 technology, originally called x86-64, is a set of extensions that allows the CPU to run as a 64-bit microprocessor. The AMD64 technology includes the following extensions:

Micro-architecture improvements: wider general-purpose registers, 8 additional 64-bit registers, and 8 additional SSE (XMM) registers.
New 64-bit instructions
New Long mode that includes two sub-modes:
- 64-bit mode: in this mode the CPU can execute only 64-bit applications.
- Compatibility mode: In this mode the CPU can execute existing 32-bit and 16-bit applications, while running under control of 64-bit operating system.
To operate in the Long mode a 64-bit Operating System is required.

The advantages of 64-bit mode over the 32-bit mode:

Better performance due to wider register width, bigger number of general and SSE registers, and cleaner architecture.
Larger size of addressable memory. 32-bit microprocessors cannot address more than 4 GB of physical memory. K8-based microprocessors (Athlon 64, Opteron, etc) in 64-bit mode can access up to 1 TB of memory, and K10-based processors (Phenom, Third Generation Opteron) can access up to 256 TB of memory.

Intel released their own set of 64-bit extensions which was called Extended Memory 64 technology (EM64T). In 2006 the EM64T was renamed to Intel 64. Intel's EM64T and "Intel 64" are mostly compatible with the AMD64 technology.

Windows Services

Thanks to blackviper.com!
Includes complete explanations of each service and advice on which services you can safely disable.

Windows 7 RC1 Service Configurations ~ Updated: May 26, 2009
Windows Vista Service Pack 2 Service Configurations ~ Updated: June 8, 2009
Windows XP x64 (64-bit) Service Pack 2 Service Configurations ~ Updated: February 26, 2009
Windows XP x86 (32-bit) Service Pack 3 Service Configurations ~ Updated: February 26, 2009
Windows 2000 Service Pack 4 Service Configurations ~ Updated: February 26, 2009

Saturday, June 6, 2009

VMWare running native XP on SATA disk

There have been a few attempts at documenting the process of running a windows install directly from the hard disk via VMWare running on a GNU/Linux host. The most publicized attempt was made “digg famous” here: Running a Windows Partition in VWware — they all fall flat in various ways. The previous example could only run on systems with IDE, and not SATA drives, which are becoming ubiquitous, and on top of that it was unnecessarily complicated.

This is part One, part Two is here:

VMWare running native XP on SATA disk, part 2.

Resources:
http://vmware.com/download/server/drivers_tools.html

http://digg.com/linux_unix/Running_a_Windows_Partition_in_VMware

http://forums.gentoo.org/viewtopic-t-246371-start-25.html?sid=ae86f6d7c87732ca4661ca0cf2731d35

http://ubuntuforums.org/showthread.php?p=3642297

http://sanbarrow.com/phpBB2/viewtopic.php?t=930&start=0&sid=2bb0f1e76a0e57cf7d6a0547b3deaf20

Friday, June 5, 2009

DRIVER_POWER_STATE_FAILURE

Stop error 0x0000009F causes
Troubleshooting
More

Networking with Windows Server 2003

Setup Network Users in Windows 2003 Server

How to configure DNS for Internet access:

How to Start with a Stand-Alone Server Running Windows Server 2003
The stand-alone server running Windows Server 2003 becomes a DNS server for your network. In the first step, you assign this server a static Internet Protocol (IP) address. DNS servers must not use dynamically assigned IP addresses because a dynamic change of address could cause clients to lose contact with the DNS server.

Step 1: Configure TCP/IP

Click Start, point to Control Panel, point to Network Connections, and then click Local Area Connection.
Click Properties.
Click Internet Protocol (TCP/IP), and then click Properties.
Click the General tab.
Click Use the following IP address, and then type the IP address, subnet mask, and default gateway address in the appropriate boxes.
Click Advanced, and then click the DNS tab.
Click Append primary and connection specific DNS suffixes.
Click to select the Append parent suffixes of the primary DNS suffix check box.
Click to select the Register this connection's addresses in DNS check box.

Note that DNS servers running Windows Server 2003 must point to themselves for DNS. If this server needs to resolve names from its Internet service provider (ISP), you must configure a forwarder. Forwarders are discussed in the How to Configure Forwarders section later in this article.
Click OK three times.

NOTE: If you receive a warning from the DNS Caching Resolver service, click OK to dismiss the warning. The caching resolver is trying to contact the DNS server, but you have not finished configuring the server.

Step 2: Install Microsoft DNS Server

Click Start, point to Control Panel, and then click Add or Remove Programs.
Click Add or Remove Windows Components.
In the Components list, click Networking Services (but do not select or clear the check box), and then click Details.
Click to select the Domain Name System (DNS) check box, and then click OK.
Click Next.
When you are prompted, insert the Windows Server 2003 CD-ROM into the computer's CD-ROM or DVD-ROM drive.
On the Completing the Windows Components Wizard page, click Finish when Setup is complete.
Click Close to close the Add or Remove Programs window.

Wednesday, June 3, 2009

Anti-virus for Linux

Avast for Linux: http://www.avast.com
AVG free : http://www.grisoft.com
Avira for Unix: http://www.avira.com/en/pages/index.php
Clam Av: http://www.clamav.net/download
For windows: Kaspersky antivirus 2009 Gratis

MSN instant messenger: virus y errores

Infección
Quien reciba alguna de estas líneas en el MSN Live Messenger:
Mira esta foto con el corte de cabello...
Estas foto son tuoyo?
Mira mis fotos desnuda
Picture of me and my friend
My friend took nice photos of me
You Should see em loL
Check out my sexy books
Wow! look at this old picture i found
Acompañado de un archivo zip para descargar.. y lo acepta... instala así algún tipo de virus o dropper o troyano, quien contactará a todos los contactos del ususario y mandará una copia de sí mismo...
Eliminación
Descargar
MSNFix
MSN Photo Virus Remover Software
Deshabilitar "restaurar sistema" en todas las unidades
Iniciar el equipo en modo seguro.
Ejecutar y seguir instrucciones de cada programa

Si falta algo, ir a www.altroblog.com (MSN E-fix) o MSN repair (website):
Msn Repair è una piccola applicazione (560 kb) che in pochi secondi ripara i più comuni errori di Windows Live Messenger e Msn Messenger, che non permettono agli utenti di effettuare correttamente l’accesso.

VMware Server 2.0.1

Source
www.vmware.com
Binaries

For Windows

VMware Server 2
Version 2.0.1 | 156745 - 03/31/09

507 MB EXE image VMware Server 2 for Windows Operating Systems. A master installer file containing all Windows components of VMware Server.md5sum: d0eefaa79e42d13a693c4d732a460ba4(¹)

VIX API 1.6 for Windows.
Version 1.6.2 | 156745 - 03/31/09

37 MB EXE image md5sum: ad531ed3c37c0a50fb915981f83ca133(¹)

For Linux

VMware Server 2 for Linux Operating Systems.
Version 2.0.1 | 156745 - 03/31/09

465 MB RPM image md5sum: eb42331bbd9be30848826b8cab73e0ca(¹)

VMware Server 2 for Linux Operating Systems.
Version 2.0.1 | 156745 - 03/31/09

466 MB TAR image md5sum: be96bc1696f4cef67755bfd2553ce233(¹)

VMware Server 2 for Linux Operating Systems 64-bit version.
Version 2.0.1 | 156745 - 03/31/09

434 MB RPM image md5sum: 697a792c70d50e98a347c06b323bd20b(¹)

The core application needed to run VMware Server 2, 64-bit version.
Version 2.0.1 | 156745 - 03/31/09

436 MB TAR image md5sum: f40498229772910d6a6788b7803f9c38(¹)

VIX API 1.6 for Linux.
Version 1.6.2 | 156745 - 03/31/09

17 MB TAR image md5sum: 2ef6174b90cdd9a2832b57dbe94cfbb1(¹)

64-bit VIX API 1.6 for Linux.
Version 1.6.2 | 156745 - 03/31/09

21 MB TAR image md5sum: 454aeba273f9a89c578223c95b262323(¹)

Virtualizing SBS 2003 Standard Edition on Linux host

Virtualizing SBS 2003 Standard Edition R2 on Debian Linux Lenny host
Debian Linux Host with VMWare 2.0.1 (http://www.petri.co.il/forums/showthread.php?t=36217)
Just installed SBS 2003 Standard Edition R2 (OEM) as guest on VMWare 2.0.1 - Host OS is Linux Debian 5 "Lenny" 64-bit
Works like a charm

The Hardware is a AMD Phenom II 940 processor with 8 gb ram, MOBO is ASUS M4N78 PRO, nVidia Geforce 8300, Integrated VGA, PCI-Express, Dual DR2-667/800/1066, Socket AM2+, Phenom II Supported

communities.vmware.com

Windows 2003 R2 from standard to enterprise

Source
www.computing.net (more related to windows 2003)
Upgrading

windows 2003 standard edition R2 SP2 32bit
and i need to upgrade it to the enterprise edition
because i have 8GB RAM physically installed and the standard edition only recognizes 4GB.
When I launch the installer of the enterprise CD i get the following error:
“Setup cannot run in program compatibility mode. To run Setup normally, go to My Computer, double-click the CD icon, and then double-click the Setup.exe file”.
Please note that I tried to run setup by double clicking the executable but I directly received the same error.

Solution

First please refer to the following supported upgrade path:

http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/supportedpaths.mspx

Please also note you can only upgrade to Enterprise 32bit from your system.

http://support.microsoft.com/kb/810613

If you can meet the upgrade requirements, please try steps below:

1. Insert the Windows Server 2003 Enterprise CD.

2. Click Start, point to Accessories, and then click Program Compatibility Wizard.

3. In the wizard, click Next.

4. Choose “I want to use the program in the CD-ROM drive” and click Next.

5. Choose “Do not apply a compatibility mode” and click Next.

6. Click Next.

7. Check the box before “Allow non-administrators to run this program” and click Next.

8. Click Next.

Now you can double-click the executable file to install Windows Server 2003 Enterprise again.

If the issue persists, please let me know if your Windows Server 2003 Standard and Enterprise are retail or OEM versions. Does your Windows Server 2003 Enterprise include R2 and SP2?

Hope it helps.

Tim Quan MSFT

ODBC 32 bit driver under the Windows x64

Source

You have a Windows 2003 server (64-bits) and you want to use a 32 bits ODBC driver: one that is usually found in the administrative panel for ODBC on Windows or an external ODBC driver
Well if you open the board of directors of HBO Windows 2003 server 64, you may not find most of your usual drivers.
Similarly if you install an ODBC driver external 32-bit installation will go well but you probably do not see in the panel.
However if you open the administrative panel ODBC under Windows 2003 (64 bits), you may not find all your usual drivers.
Note that you may not find external drivers (32 bits) in the panel even it gets installed on your computer.
In fact, the boards of directors of the pilots 64-bit and 32 bit are separated on this version of Windows. One you find through administrative tools, the panel for 64-bit
The administrative panels for 64 bits and 32 bits drivers are separate on the windows. In the windows 2003 (64 bits), you will find the panel for ODBC 64 bits.
To access the panel 32 bits drivers, your should run the following command :
c:\windows\syswow64\odbcad32.exe

Windows unatended installation

Source

The two basic principles of Windows system administration:

Tuesday, June 2, 2009

Server 2k3 SP2 Administration Toolkit

The Administration Tools Pack allows administrators to install the Windows Server 2003 SP2 management tools onto a computer running Windows XP Professional or a Windows Server 2003 family operating system to perform remote server management functions.

Windows Server 2003 Service Pack 2 Administration Tools Pack for x64 editions
http://www.microsoft.com/downloads/d...DisplayLang=en

Windows Server 2003 Service Pack 2 Administration Tools Pack for x86 editions:
http://www.microsoft.com/downloads/d...9-3f101e533d95

Windows CD Volume Labels

Source

Windows 2003 CD Volume Labels

- View Windows Server 2003 SP1 CD Labels (TTID#355)
- View Windows Server 2003 R2 Labels (TTID#387)

Acronyms and Abbreviations
CCP	Compliance Checking Program (Upgrade Version)
CHK	Checked Build
EVL	Evaluation Version
FPP	Full Packaged Product (Retail Version)
MPC	Microsoft Product Code
OEM	Original Equipment Manufacturer
PID	Product ID After the Product Key is validated in the Setup program, the Setup program builds a unique PID which is assigned to the computer. A PID contains the Microsoft Product Code (MPC) and the three characters channel ID value.
RTM	Release To Manufacturing
SEL	Select (License for 250 or more PCs)
SLP	System-Locked Preinstallation Royalty OEM vendors can distribute Windows products by using System-Locked Preinstallation Product Keys so that end users can bypass product activations.
VLK	Volume License (Product) Key
VOL	Volume (License)
WPA	Windows Product Activation

Windows XP CD Volume Labels

Look at the first few digits of your installed product ID under the already installed OS. It can tell you what version you have installed. Most start with 55

Windows XP Home Retail WXHFPP_EN 55277
Windows XP Home Retail SP1 XRMHFPP_EN 55277
Windows XP Home Retail SP1a X1AHFPP_EN 55277
Windows XP Home Retail SP2 VRMHFPP_EN 55277
Windows XP Home Upgrade WXHCCP_EN 55285
Windows XP Home Upgrade SP1 XRMHCCP_EN 55285
Windows XP Home Upgrade SP1a X1AHCCP_EN 55285
Windows XP Home Upgrade SP2 VRMHCCP_EN 55285
Windows XP Home OEM WXHOEM_EN 55277
Windows XP Home OEM SP1 XRMHOEM_EN 55277
Windows XP Home OEM SP1a X1AHOEM_EN 55277
Windows XP Home OEM SP2 VRMHOEM_EN 55277
Windows XP Home OEM SP2 VRMHOEM_EN 76477
Windows XP Home Volume WXHVOL_EN 55274
Windows XP Home Volume SP1 XRMHVOL_EN 55274
Windows XP Home Volume SP1a X1AHVOL_EN 55274
Windows XP Home Volume SP2 VRMHVOL_EN 55274

Windows XP Home (SP2) DELL System Install XP2_PER_ENG
Windows XP Pro (SP2) DELL System Install XP2_PRO_ENG

Windows XP Pro Retail WXPFPP_EN 55274
Windows XP Pro Retail SP1 XRMPFPP_EN 55274
Windows XP Pro Retail SP1a X1APFPP_EN 55274
Windows XP Pro Retail SP2 VRMPFPP_EN 55274
Windows XP Pro Upgrade WXPCCP_EN 55276
Windows XP Pro Upgrade SP1 XRMPCCP_EN 55276
Windows XP Pro Upgrade SP1a X1APCCP_EN 55276
Windows XP Pro Academic Upgrade SP1 X1APCCP_EN 55276
Windows XP Pro Upgrade SP2 VRMPCCP_EN 55276
Windows XP Pro Academic Upgrade SP2 VRMPCCP_EN 76488
Windows XP Pro OEM WXPOEM_EN 55274
Windows XP Pro OEM SP1 XRMPOEM_EN 55274
Windows XP Pro OEM SP1a X1APOEM_EN 55274
Windows XP Pro OEM SP2 VRMPOEM_EN 55274
Windows XP Pro Volume WXPVOL_EN 55274
Windows XP Pro Volume SP1 XRMPVOL_EN 55274
Windows XP Pro Volume SP1a X1APVOL_EN 55274
Windows XP Pro Volume SP2 VRMPVOL_EN 55274
Windows XP Pro MSDN WXPFPP_EN 55274
Windows XP Pro MSDN SP1 XRMPFPP_EN 55274
Windows XP Pro MSDN SP1a X1APFPP_EN 55274
Windows XP Pro MSDN SP2 VRMPFPP_EN 55274
Windows XP Pro Evaluation WXPEVL_EN

Bienvenido! - Willkommen! - Welcome!

Wednesday, June 24, 2009

Tuesday, June 23, 2009

Sunday, June 21, 2009

Saturday, June 20, 2009

Friday, June 19, 2009

Thursday, June 18, 2009

Wednesday, June 17, 2009

Tuesday, June 16, 2009

Inhaltsverzeichnis

Monday, June 15, 2009

Verwenden von Swap

Experten-Info:

Sunday, June 14, 2009

Thursday, June 11, 2009

Wednesday, June 10, 2009

Tuesday, June 9, 2009

Saturday, June 6, 2009

Friday, June 5, 2009

Step 1: Configure TCP/IP

Step 2: Install Microsoft DNS Server

Wednesday, June 3, 2009

Tuesday, June 2, 2009

Tux & Cía. -Ventas

Search This Blog

Tux & Cía.

Which Security SW do you use?

Network tools

[Your PC]

Piador

Me and Linus Torvalds' work

Free&Open Source SW

Blog Archive

Labels

Comics

NeoCounter

About Me

Nerd or Dren?

Live Traffic Map

Recommended Reading

The Power of Knowledge-El Poder del Conocimiento-Die Macht des Wissens

Visitantes-Besucher-Visitors