Friday, September 30, 2011
Thursday, September 29, 2011
Since Openbox 3.50 this is possible, icons in your right click openbox menu.
First install openbox-menu from AUR: https://aur.archlinux.org/packages.php?ID=31605
packer -S openbox-menu
Sunday, September 25, 2011
Problems with MBR
- Only 4 primary partitions or 3 primary + 1 extended partitions with many logical partitions can be defined. If you have 3 primary + 1 extended partitions, and you have some free space outside the extended partition area, you cannot create a new partition over that space.
- Within the extended partition, the logical partitions meta-data is stored in a linked-list structure. If one link is lost, all the logical partitions following that metadata is lost.
- MBR supports only 1 byte partition type codes which leads to many collisions.
- MBR stores partition sector information using 32-bit LBA values. This LBA length along with 512 byte sector size (more commonly used) limits the maximum addressable size of the disk to be 2TB. Any space beyond 2TB cannot be defined in a partition if MBR partitioning is used.
Advantages of GPT
- Uses GUIDs to identify partition types - No collisions.
- Provides a unique disk GUID and partition GUID for each partition - A good filesystem-independent way of referencing partitions and disks.
- Minimum of 128 partition table entries - No need for extended and logical partitions.
- Uses 64-bit LBA for storing Sector numbers - maximum addressable disk size is 2 ZiB.
- Stores a backup header and partition table at the end of the disk that aids in recovery if the main copy is clobbered.
- CRC32 checksums to detect errors and corruption of the partition table.
Archlinux provides three bootloaders GRUB-Legacy, GRUB2 and Syslinux. The default bootloader of the Arch Linux installer, GRUB-Legacy, does not support GPT.
GPT specific instructions
GRUB2 in BIOS-GPT configuration requires a BIOS Boot Partition to embed its core.img in the absence of 32 KiB post MBR gap in GPT partitioned systems.
Create a 1 MiB (minimum size - 2 MiB recommended if you use LVM and/or RAID etc.) partition using cgdisk or GNU Parted with no filesystem. The location of the partition in the partition table does not matter but it should be within the first 2 TiB region of the GPT disk. It is advisable to put it somewhere in the beginning of the disk before the /boot partition. Set the partition type to "EF02" in cgdisk or set
This partition is used by GRUB2 only in BIOS-GPT setups. No such partition type exists in case of MBR partitioning (at least not for GRUB2). This partition is also not required if the system is UEFI based, as no embedding takes place in that case. Neither GRUB-legacy nor SYSLINUX require this partition.source: https://wiki.archlinux.org/index.php/GPT
Comment: more possibilities are 'paid' by a significantly more intricate disk preparation scenario.
Friday, September 23, 2011
gvfs for thunar: https://wiki.archlinux.org/index.php/Thunar#GVFS_and_trash_issue
Tuesday, September 13, 2011
For instance this desktop for 600 euri:
Het belangrijkste van deze desktop is het lage geluid dat hij produceert wanneer de computer is ingeschakeld is.
Computer kast Cooler Master Midi Tower Silencio 550 ATX, No PSU (zwart)
Aansluitingen voorkant USB3.0 x 1, USB2.0 x 1, Mic x1, Audio x 1, SD card reader x 1
Voeding Be Quiet Pure Power L7 300W
Moederboord Asus P8H67-M EVO B3 iH67, SATA600 RAID, USB3.0
Processor Intel Core i3 2100T 2.50GHz 3MB
Intern geheugen Corsair 2x2GB, DDR3, PC12800, CL9, XMS3
Hardeschijf SSD OCZ SSD 2.5", 40GB, SATA, Vertex 2
Hardeschijf HDD Western Digital Harddisk 3.5" 500gb, SATA600, 7200rpm, WD10EALX
Optical Lite-On DVD-/+/RAM IHAS124-19 24x/24x/12x SATA
Maten (W) 210 x (H) 415.5 x (D) 505.0 mm
Friday, September 2, 2011
A .pacnew file may be created during a package upgrade (pacman -Syu, pacman -Su or pacman -U) to avoid overwriting a file which already exists and was previously modified by the user. When this happens a message like the following will appear in the output of pacman:
warning: /etc/pam.d/usermod installed as /etc/pam.d/usermod.pacnew
A .pacsave file may be created during a package removal (pacman -R), or by a package upgrade (the package must be removed first). When the pacman database has record that a certain file owned by the package should be backed up it will create a .pacsave file. When this happens pacman outputs a message like the following:warning: /etc/pam.d/usermod saved as /etc/pam.d/usermod.pacsave
These files require manual intervention from the user and it is good practice to handle them right after every package upgrade or removal. If left unhandled, improper configurations can result in improper function of the software, or the software being unable to run altogether.
to check out what needs manual adaptation
- ► 2013 (33)
- ► 2012 (29)
- ▼ September (7)
- ► 2010 (90)
- ► 2009 (62)
- ► 2008 (123)
- Exclusion of liability Regarding StillStupid: The use you make of the guides, tips and downloads that you listed on this web site or on another website to which I refer is entirely at your own risk. In no way can I be held liable for damage or consequential damages of any kind, which occurs as a result of that use.