Slashdot Mirror

← Back to Domains

Domain: reactivated.net

Stories and comments across the archive that link to reactivated.net.

Comments · 7

  1. meanwhile, OLPC firmware gets edits to support XP by schwaang · · Score: 4, Interesting · on First Review of Intel's New Classmate PC

    Among other things, of course.
    OLPC seems to be plugging away as hard as ever since all that angst over XP.

    And some users are figuring out how to install regular linux desktops in an easier way. (Sugar's pretty hard for expert users to get used to.)

    Obligatory on-topic snark: does ClassmatePC come with a virus checker?

  2. Re:Linux needs system-wide color management by PitaBred · · Score: 1 · on Linux Alternatives To Apple's Aperture

    That's because they moved to udev, I believe. If you want the "old" functionality, you can probably tweak the udev rules yourself. It's not terribly difficult or hard to figure out. Probably just write a script, or hell, create persistent mountpoints since you likely only have a few hotplugged devices that you use.

  3. Re:Pictures by slater86 · · Score: 1 · on Child-Suitable Alternatives To Passwords?

    It might be easier to just use a different method. (PAM is very flexible after all)

    I currently own a Fujitsu Lifebook U1010 running debian. The inbuilt fingerprint scanner (made by AuthenTec i think) works great with fprint http://www.reactivated.net/fprint/wiki/Main_Page/

    I would assume that an off the shelf USB fingerprint scanner would work just as well and is much simpler

  4. Fingerprint Reader by Cyberax · · Score: 1 · on Child-Suitable Alternatives To Passwords?

    You can buy a cheap fingerprint reader, like: http://www.amazon.com/Microsoft-DG2-00002-Fingerprint-Reader/dp/B0002WPSB2 and set it up using http://www.reactivated.net/fprint/wiki/Main_Page

    I use it for my home computer without problems.

  5. Disabling Digital Persona encryption by Anonymous Coward · · Score: 0 · on Successful Alternatives To Password Authentication?

    Actually, the Digital Persona's Encryption can be bypassed by switching a single bit, so no need to hack the encryption method itself:

    http://www.reactivated.net/weblog/archives/2006/01 /breaking-encryption-the-easy-way/

    To change the firmware in windows and make any device insecure, just reverse the bit data and set the byte to 0. The below makes the 'insecure' device 'secure'

    if starting from scratch.
    1 - unzip MS software. (DP_PM_xxxxx, avail from Microsoft).
    2 - in *driver*, modify the *dpD0Bx01.dll* file (should be around 80kb) in a hex editor.
    3 - modify bit at 0xE9B7 from a 0 to a 1. save it.
    4- plug your MSFR in, and it should ask for drivers. point it to the stuff you unzipped/modified.

    if you already have it installed.
    1 - unplug your MSFP.
    2 - goto windows/system32/
    3 - modify the *dpD0Bx01.dll* file (should be around 80kb) in a hex editor.
    4 - modify bit at 0xE9B7 from a 0 to a 1. save it.
    5 - plug the MSFP back it.

    NOTE: Once you flip that one bit, the MS software will NOT work anymore. You can use GrFinger to verify that the image from the fingerprint ready is now encrypted. (before - fingerprint is visible; after - fingerprint is "noise")

  6. Solution: by Ayanami+Rei · · Score: 1 · on What's Fedora Up To? Ask the Project Leader

    ALWAYS label your volumes so they have UUIDs.
    Never put bare drives into a RAID. Partition them, set the drive-sized slice to 0xFD, and enjoy device name independance.

    Actually the answer you are looking for is udev. You could name your disks via their serial# or some such but there are too many guides and documents and scripts out there that rely on the simple first-seen-first-labeled sd[abcde...] nomenclature that they aren't going to make that the default.

    Check this out:
    http://www.reactivated.net/writing_udev_rules.html #sysfsmatch

  7. Most importantly, read the expert documentation. by atomic-penguin · · Score: 3, Informative · on Vanilla Kernel 2.6 Stability vs 2.4?
    You will need the appropriate hotplug utilities, get them here.

    The 2.6.8 kernel had an issue with CD writing (only root could do this). This has been corrected in later kernels. You may have to delv into the udev rules to get things setup the way you like. Read the fine HOWTO on writing rules for udev.

    My cd-rom did not get recognized after boot unless the ide-cd module was called before udev started. There was a mixup with tty and pty in the default udev rules around the time of switch between 2.6.7 and 2.6.8 and it obliterated the 'less' and 'man' commands. How convenient is it that I can't run 'man udev.rules'?
     
    I believe this has also been remedied since then. If in doubt I suggest taking the following steps.
    1. wget ftp://ftp.kernel.org/pub/linux/kernel/v2.4/linux-2 .6.x.tar.bz2
    2. tar jxvf linux-2.6.x.tar.bz2 && cd linux-2.6.x
    3. less README
    4. cd Documentation && less post-halloween-2.6.txt

     
    Title of the second document is "The post-halloween document. v0.48 (aka, 2.6 - what to expect)". That should tell you everything you need to know about upgrading from 2.4.