From owner-freebsd-gnome@FreeBSD.ORG Mon Jan 6 06:48:09 2014 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 725ADA58 for ; Mon, 6 Jan 2014 06:48:09 +0000 (UTC) Received: from mail-pb0-x22b.google.com (mail-pb0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4AECA1B15 for ; Mon, 6 Jan 2014 06:48:09 +0000 (UTC) Received: by mail-pb0-f43.google.com with SMTP id rq2so18137541pbb.2 for ; Sun, 05 Jan 2014 22:48:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=Za9lsXGLs9rzPjwGKEFFgiPKwKove11+wWcajj4T7vg=; b=uKbBCX5tTfxKx5Nz6TcFWzxZst0qNK5JrAL4vIxRZP2weAV5z1PLfKU+kLpj2EVAqS LclThtMJ9UeAg+GDrgdLxABnLkXSIIYWUj3m+V/m7yok1scR5i3KdXUg2n3/+secz7s0 JhMfncRxWPQsZLqngfZCqksz6CGcMwWW+6Pr1oXu7ExQVgAWYq8nd49w3iUCYX7YF/w7 FYMAvvvWe1+1DMqD5oHkKsXUv4Cc7GIcPagfCMIiY2Unxw15mIw2HIfUIyHkN7QJ9sYi A1l5K5dMMRRZRKaljGCKc0sPU3zSHDESdQNy71oqMa/AgAQIUoB0TN5O+vAzrBU+bi8w mRQw== MIME-Version: 1.0 X-Received: by 10.68.17.41 with SMTP id l9mr121964931pbd.76.1388990886729; Sun, 05 Jan 2014 22:48:06 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.67.23.101 with HTTP; Sun, 5 Jan 2014 22:48:06 -0800 (PST) Date: Sun, 5 Jan 2014 22:48:06 -0800 X-Google-Sender-Auth: 5LG3EU0lgN71_7OSA7-8SX60Bho Message-ID: Subject: hal, ntfs, and 10.0-RC3 From: Kevin Oberman To: FreeBSD GNOME Users Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jan 2014 06:48:09 -0000 Oops! Posted this to stable@ by mistake. gnome@ is where I meant to send it. Since I updated to 10.0-RC3 (from 9), hald no longer works with my ntfs partitions. I can mount them manually with ntfs-3g, but when not mounted, hal does not see them at all. > ls /dev/ntfs Lenovo_Recovery SYSTEM_DRV Windows7_OS > gpart show ada0 => 63 1465149105 ada0 MBR (699G) 63 1985 - free - (993K) 2048 2457600 1 ntfs (1.2G) 2459648 958765056 2 ntfs (457G) 961224704 471040000 3 ebr (225G) 1432264704 32878592 4 ntfs (16G) 1465143296 5872 - free - (2.9M) > lshal | grep ada0 block.device = '/dev/ada0' (string) freebsd.device_file = '/dev/ada0' (string) > lshal | grep Windows7 Exit 1 I mount on NTFS partition and: > lshal | grep ada0 block.device = '/dev/ada0' (string) freebsd.device_file = '/dev/ada0' (string) block.device = '/dev/ada0s1' (string) block.device = '/dev/ada0s2' (string) block.device = '/dev/ada0s3' (string) block.device = '/dev/ada0s5' (string) block.device = '/dev/ada0s4' (string) > lshal | grep Windows7 block.device = '/dev/ntfs/Windows7_OS' (string) info.product = 'Windows7_OS' (string) volume.label = 'Windows7_OS' (string) After a umount, all slices vanish again. Might this be fall-out of the removal of ntfs (read-only) support? I have not looked through the hald sources to see how it detects these slices. I do find it interesting that mounting one NTFS file system causes all of the other ones appear to hald. Any suggestions? -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com