From owner-freebsd-gnome@FreeBSD.ORG Sun Jan 5 10:36:24 2014 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8A813B9 for ; Sun, 5 Jan 2014 10:36:24 +0000 (UTC) Received: from portscout.freebsd.org (portscout.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 768661338 for ; Sun, 5 Jan 2014 10:36:24 +0000 (UTC) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.14.7/8.14.7) with ESMTP id s05AaOZV031338 for ; Sun, 5 Jan 2014 10:36:24 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.14.7/8.14.7/Submit) id s05AaOvj031337; Sun, 5 Jan 2014 10:36:24 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201401051036.s05AaOvj031337@portscout.freebsd.org> X-Authentication-Warning: portscout.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Sun, 5 Jan 2014 10:36:24 +0000 From: portscout@FreeBSD.org To: gnome@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 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: Sun, 05 Jan 2014 10:36:24 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/gnome@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ devel/libgsf | 1.14.28 | 1.14.29 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-gnome@FreeBSD.ORG Sun Jan 5 18:20:08 2014 Return-Path: Delivered-To: gnome@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6EA0DEF; Sun, 5 Jan 2014 18:20:08 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 455B917D2; Sun, 5 Jan 2014 18:20:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s05IK8dQ091465; Sun, 5 Jan 2014 18:20:08 GMT (envelope-from edwin@freefall.freebsd.org) Received: (from edwin@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s05IK8QU091464; Sun, 5 Jan 2014 18:20:08 GMT (envelope-from edwin) Date: Sun, 5 Jan 2014 18:20:08 GMT Message-Id: <201401051820.s05IK8QU091464@freefall.freebsd.org> To: edwin@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, gnome@FreeBSD.org From: edwin@FreeBSD.org Subject: Re: ports/185519: [UPDATE] archivers/file-roller to v2.32.2 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: Sun, 05 Jan 2014 18:20:08 -0000 Synopsis: [UPDATE] archivers/file-roller to v2.32.2 Responsible-Changed-From-To: freebsd-ports-bugs->gnome Responsible-Changed-By: edwin Responsible-Changed-When: Sun Jan 5 18:20:08 UTC 2014 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=185519 From owner-freebsd-gnome@FreeBSD.ORG Sun Jan 5 20:12:28 2014 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4DD924D5 for ; Sun, 5 Jan 2014 20:12:28 +0000 (UTC) Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003: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 1A7C71FF0 for ; Sun, 5 Jan 2014 20:12:28 +0000 (UTC) Received: by mail-ob0-f171.google.com with SMTP id wp18so17695775obc.30 for ; Sun, 05 Jan 2014 12:12:27 -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=XVP9iKlkcuJbjaFBa1gFpqXifb1P6SCh6mUAnCg1pt8=; b=fM/LUyUOM+/9zZNe2YEPnYIv7c5OQIjumXPL+0Y4kgvQBDHPMx2uk510Bsm669y4GV JbzeZbHsFi5RM+m8gZt1sOJGS8Ar1hXl5e/uhfYPU4WbPo3V+Qc6F9L1jVBMlLxNCqzw 4AhzZFmNJabUojDTH8Cn4JPu6+mvPIA+UB/yAtKLBsWXe4OZ3GlJ5m2TANi2lGzOBhWD r0zMTeU3OxID+d2iShuyhKOPDPATaXZ5YJ+MSYRg4w9RodQRPnQxtNW/Z7z8aYpKGunb 4OWTowC8sYiaUEvEdefRBccYuM+3Ipo1wCYQlsLDAY0THb50DVGZAROLorzzSOMPOdc8 DGfQ== MIME-Version: 1.0 X-Received: by 10.182.87.42 with SMTP id u10mr68041688obz.22.1388952747347; Sun, 05 Jan 2014 12:12:27 -0800 (PST) Sender: pali.gabor@gmail.com Received: by 10.182.22.44 with HTTP; Sun, 5 Jan 2014 12:12:27 -0800 (PST) Date: Sun, 5 Jan 2014 21:12:27 +0100 X-Google-Sender-Auth: VcY0e6Yv2Ti_E0HoEZQpWXLEix4 Message-ID: Subject: Your Q4 Status Report From: Gabor Pali To: gnome@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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: Sun, 05 Jan 2014 20:12:28 -0000 Dear GNOME/FreeBSD maintainers, Please prepare a report for submission to monthly@ about the things you have done between last October and last December. We are looking forward to your submission until January 14, 2014. 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 From owner-freebsd-gnome@FreeBSD.ORG Mon Jan 6 07:02:10 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 E8306D09 for ; Mon, 6 Jan 2014 07:02:10 +0000 (UTC) Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 834161D13 for ; Mon, 6 Jan 2014 07:02:10 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id a1so2237748wgh.5 for ; Sun, 05 Jan 2014 23:02:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=/3tiZjm9AHPbtcmW3AlNoLXlMBEUrXOn/xFT3AEOfZg=; b=VJpqBR0XiMVWLds25KFF1hueDj/5AjtJl35GLrAnZr4Ic5F2SXQdbTUmg4b51yXN9c kGj8++lT2KHetDmWhL9bKUOc9q9RhPDqLm0CxVibNwCNALyJJmnjZ79xmii+Lebi9UPv w96778v1aWSjTBW6NkKUvCsqL3sXVt4U7umuEYdxy7G9KEDMQsva1GgGJ9p4tGDPGJ9Q CZbbXGuoZ8kFuWWt9OxQ2qr6jN1I00FWhF9poAMTlcdmSxqJIjT7MxGq8vgaeVjjrEgu oQr1mnfYqFKWPu9uG/B/ZtIp2HDpEH4dxM2ogYxy4rvcxku2S01v1nK25khZBni1H/i+ RSFg== X-Received: by 10.194.23.201 with SMTP id o9mr45050wjf.67.1388991728392; Sun, 05 Jan 2014 23:02:08 -0800 (PST) MIME-Version: 1.0 Sender: villa.alberto@gmail.com Received: by 10.216.10.73 with HTTP; Sun, 5 Jan 2014 23:01:48 -0800 (PST) In-Reply-To: References: From: Alberto Villa Date: Mon, 6 Jan 2014 10:01:48 +0300 X-Google-Sender-Auth: Wg2Davj-WKpLL34_WHR0p2hZMzY Message-ID: Subject: Re: hal, ntfs, and 10.0-RC3 To: Kevin Oberman Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD GNOME Users 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 07:02:11 -0000 2014/1/6 Kevin Oberman : > 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. > > 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. I've done some work on HAL in past months, so I have a view on the matter. HAL uses sysctl for disks detection, so it's up to the system to list all the available drives. I'll try to have a look in next days, but my wild guess (since I've not been using ntfs-3g for years) is that ntfs-3g unloads its module when all mounts are removed, thus making the drives undetectable again. Is that correct? -- Alberto Villa, FreeBSD committer http://people.FreeBSD.org/~avilla From owner-freebsd-gnome@FreeBSD.ORG Mon Jan 6 10:56:19 2014 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 22AD6E4E for ; Mon, 6 Jan 2014 10:56:19 +0000 (UTC) Received: from portscout.freebsd.org (portscout.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0E6CF1E8F for ; Mon, 6 Jan 2014 10:56:19 +0000 (UTC) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.14.7/8.14.7) with ESMTP id s06AuIif054808 for ; Mon, 6 Jan 2014 10:56:18 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.14.7/8.14.7/Submit) id s06AuIYO054804; Mon, 6 Jan 2014 10:56:18 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201401061056.s06AuIYO054804@portscout.freebsd.org> X-Authentication-Warning: portscout.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Mon, 6 Jan 2014 10:56:18 +0000 From: portscout@FreeBSD.org To: gnome@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 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 10:56:19 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/gnome@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ textproc/link-grammar | 4.7.4 | 4.8.5 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-gnome@FreeBSD.ORG Mon Jan 6 11:07:07 2014 Return-Path: Delivered-To: gnome@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 32D94886 for ; Mon, 6 Jan 2014 11:07:07 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1E5A710C8 for ; Mon, 6 Jan 2014 11:07:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s06B76WN045632 for ; Mon, 6 Jan 2014 11:07:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s06B76Pd045630 for gnome@FreeBSD.org; Mon, 6 Jan 2014 11:07:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 6 Jan 2014 11:07:06 GMT Message-Id: <201401061107.s06B76Pd045630@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: gnome@FreeBSD.org Subject: Current problem reports assigned to gnome@FreeBSD.org 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 11:07:07 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/185519 gnome [UPDATE] archivers/file-roller to v2.32.2 o ports/185442 gnome math/gnumeric 1.12.9 coredumps when trying to open a f o ports/185400 gnome mail/evolution-exchange required deprecated db41 o ports/185287 gnome [patch] sysutils/upower: pkg-plist fix, MANPAGES optio o ports/185252 gnome x11-toolkits/pango can't find fonts o ports/185206 gnome x11-toolkits/py-gtk2 missing dependency with py-gobjec o ports/185083 gnome x11-toolkits/vte and bison o ports/184362 gnome x11/mate-terminal crash o ports/184179 gnome sysutils/tracker-client build error - what is linux? o ports/184025 gnome x11/gnome2: 'pkg install gnome2' Failure o ports/183856 gnome x11-fonts/fontconfig has some recursion issues? o ports/183536 gnome [patch] x11-fonts/fontconfig on armv6 o ports/183422 gnome deskutils/notification-daemon 0.7.2 asserts on any not o ports/183399 gnome Bad Makefile in /usr/ports/x11/gnome-desktop o ports/182995 gnome x11/gnome-applets fails to package if WITH_GNOME is no o ports/182954 gnome [patch] x11-toolkits/pango: update to version 1.36.0, o ports/182953 gnome [patch] graphics/cairo: update to version 1.12.16, sup o ports/182405 gnome error to build graphics/poppler-glib o ports/182203 gnome news/pan will not compile on 10.0-ALPHA1 o ports/182118 gnome mail/evolution regularly core dumps o ports/182069 gnome [PATCH] devel/py-gobject: Fix GFlags messages o ports/181958 gnome cannot install graphics/gimp pkg o ports/181629 gnome [PATCH] sysutils/tracker-client was setting itself at o ports/181561 gnome net-im/telepathy-idle fails to build in poudriere o ports/181446 gnome x11/gnome2: Error occurrs when using a GUI frontent fo o ports/181349 gnome cairo.h missing in graphics/librsvg o ports/181278 gnome deskutils/notification-daemon: Notification Daemon dum o ports/181266 gnome cannot update net-im/telepathy-glib-0.18.2 to 0.20.2 o ports/181095 gnome net-p2p/transmission-gtk fails to start o ports/181054 gnome graphics/gimp port build fails o ports/180604 gnome devel/xdg-utils: xdg-screensaver depends on dcop o ports/180601 gnome graphics/gegl is missing DOCS option from Makefile o ports/180596 gnome [patch] devel/libnotify: remove gtk20 and gettext depe o ports/180459 gnome Port devel/py-dbus ' wrong PORTDOCS logic and pkg-plis o ports/180348 gnome devel/dbus fails if existing user found o ports/180114 gnome Error building net-im/loudmouth o ports/180062 gnome graphics/clutter-gtk compilation failure o ports/179786 gnome graphics/poppler and xpdf contain conflicting files o ports/179500 gnome finance/gnucash does not install database dependencies f ports/179400 gnome [PATCH] print/freetype2: Add Infinality patches o ports/179348 gnome [PATCH] graphics/passepartout: Trim docs, add FAM opti o ports/179124 gnome [PATCH] graphics/cairomm: Convert to OptionsNG, trim d o ports/178796 gnome irc/xchat fails to link with gcc46/47 o ports/178699 gnome [fix] devel/xdg-utils fails without ${LOCALBASE}/share o ports/178698 gnome graphics/gimp: package dependencies failing o ports/178098 gnome sysutils/polkit will not build if glib20 is too old o ports/178023 gnome [patch] graphics/cairo: add a fix for text redrawing i o ports/177458 gnome devel/gobject-introspection coredumping things o ports/177226 gnome devel/glib20 update: gnome-gmail-notifier won't start o ports/177086 gnome www/webkit-gtk3 does not build o ports/170410 gnome devel/gvfs: gvfs-hal-volume-monitor crashes when new m o ports/167199 gnome x11-fm/nautilus 2.32.2.1 Gnome2.32 Doesn't auto mount p ports/161164 gnome [PATCH] devel/glade3: update to 3.10.0 p ports/159928 gnome Updates graphics/clutter to 1.6.16 f ports/148244 gnome x11/gnome2: gnome desktop and HAL prevent umount witho s ports/145301 gnome [patch] sysutils/hal: /usr/local/etc/rc.d/hald startup 56 problems total. From owner-freebsd-gnome@FreeBSD.ORG Mon Jan 6 12:18:09 2014 Return-Path: Delivered-To: freebsd-gnome@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C78C0FDB for ; Mon, 6 Jan 2014 12:18:09 +0000 (UTC) Received: from exprod8ob108.obsmtp.com (exprod8ob108.obsmtp.com [64.18.3.95]) by mx1.freebsd.org (Postfix) with SMTP id 9CD8E1A57 for ; Mon, 6 Jan 2014 12:18:09 +0000 (UTC) Received: from localhost.localdomain ([199.187.125.26]) by exprod8ob108.postini.com ([64.18.7.12]) with SMTP ID DSNKUsqfAK6pScfxpzZVsDAjC7ErvfQKLGSv@postini.com; Mon, 06 Jan 2014 04:18:08 PST X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=127.0.0.1; To: freebsd-gnome@FreeBSD.org Subject: FreeBSD GNOME Project News - FreeBSD GNOME News Sy RSS/XML Feed Found X-PHP-Originating-Script: 0:xmlsender.php From: info@findthatfile.com X-Mailer: PHP/5.3.3Date : Sunday 5th of January 2014 11:47:01 PM Date: Sun, 05 Jan 2014 23:47:01 -0500 Message-ID: <1388983621_3788@findthatfile.com> X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: info@findthatfile.com 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 12:18:09 -0000 Find That File RSS/XML indexing bot has located the following public feeds and will be indexing them shortly. http://www.freebsd.org/gnome/rss.xml http://www.dk.freebsd.org/gnome/rss.xml http://www.jp.freebsd.org/www.FreeBSD.org/gnome/rss.xml http://freebsd.maxnet.ua/gnome/rss.xml http://www.br.freebsd.org/gnome/rss.xml http://www.de.freebsd.org/gnome/rss.xml http://www.si.freebsd.org/gnome/rss.xml http://www.lv.freebsd.org/gnome/rss.xml http://www.ch.freebsd.org/gnome/rss.xml http://www2.ru.freebsd.org/gnome/rss.xml http://freebsd.mirror.solnet.ch/gnome/rss.xml http://ftp11.us.freebsd.org/gnome/rss.xml http://adsn.vstyle.co.il/gnome/rss.xml http://dumper.iqm.unicamp.br/gnome/rss.xml http://adsm.vstyle.co.il/gnome/rss.xml http://www.freebsd.cz/gnome/rss.xml http://freebsd.isc.org/gnome/rss.xml http://freebsd.home4u.ch/gnome/rss.xml http://ftp.iqm.unicamp.br/gnome/rss.xml http://freebsd.org/gnome/rss.xml http://www.at.freebsd.org/gnome/rss.xml http://freebsd.giga.net.tw/gnome/rss.xml http://freebsd.server-king.de/gnome/rss.xml http://freebsd.unixtech.be/gnome/rss.xml http://freebsd.perm.ru/gnome/rss.xml http://freebsd.rinet.ru/gnome/rss.xml http://freebsd.mlc.edu.tw/gnome/rss.xml http://www.cz.freebsd.org/gnome/rss.xml http://freebsd.ki.iif.hu/gnome/rss.xml http://fbsd.perm.ru/gnome/rss.xml http://www2.es.freebsd.org/gnome/rss.xml --------- Find That File Media Search - http://www.findthatfile.com EDU, Library and GOV Media Search - http://edu.findthatfile.com * If you wish to add more content to be indexed use our online form at : http://www.findthatfile.com/addmedia.php * Removals or blocked domains can be submitted online at : http://www.findthatfile.com/removemedia.php From owner-freebsd-gnome@FreeBSD.ORG Mon Jan 6 15:22:01 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 C43835FE; Mon, 6 Jan 2014 15:22:01 +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 93B691A49; Mon, 6 Jan 2014 15:22:01 +0000 (UTC) Received: by mail-pb0-f43.google.com with SMTP id rq2so18613359pbb.2 for ; Mon, 06 Jan 2014 07:21:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=SKyBxDEoDjm+50Vnoojxhx7cr4RI7eFuQzkoJ3Nak4o=; b=05FEEoNwWTUVWLlw9jgHSOxV5ZaRRDFJicm1ok79bg4tBSNCLAHNH1dh50lLmER2oG qp8k+5ckA47r34lEKv9UKscn8M8SWCdqNEblZhQQmmb6Lbvpt4IHjcezx0nJXWUt5yhw WUR//Zz4Oy85+euhuIvWXQcbazvDKYdo9crBks+gkb52D19sE8m0/oWVTsmT2PR2OT6a W55+yywl6jVuDO0I0iN63zzKN+Zj3jaZ5M31IW5Z/PRxy3QoMr2d5Mk+Zz4mrjIUd/zk vAmwyWGFsdMXktC5fsUYOA02gjGtU4G+x2n/JiIhdfthPO9nXKw+RddoLHrrPtTuDdIo rHEA== MIME-Version: 1.0 X-Received: by 10.68.17.41 with SMTP id l9mr126439682pbd.76.1389021717037; Mon, 06 Jan 2014 07:21:57 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.67.23.101 with HTTP; Mon, 6 Jan 2014 07:21:56 -0800 (PST) In-Reply-To: References: Date: Mon, 6 Jan 2014 07:21:56 -0800 X-Google-Sender-Auth: xheCuEXuLnZQs-8DR4YChuvTDC8 Message-ID: Subject: Re: hal, ntfs, and 10.0-RC3 From: Kevin Oberman To: Alberto Villa Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD GNOME Users 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 15:22:01 -0000 On Sun, Jan 5, 2014 at 11:01 PM, Alberto Villa wrote: > 2014/1/6 Kevin Oberman : > > 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. > > > > 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. > > I've done some work on HAL in past months, so I have a view on the matter. > > HAL uses sysctl for disks detection, so it's up to the system to list > all the available drives. I'll try to have a look in next days, but my > wild guess (since I've not been using ntfs-3g for years) is that > ntfs-3g unloads its module when all mounts are removed, thus making > the drives undetectable again. Is that correct? > > Alberto, I don't believe this is the case. First, ntfs-3g is entirely user space. The only kernel code is in fusefs and it is loaded at boot time or compiled into the kernel. In any case, /dev/ntfs contains all of volumes, so the system recognizes the slices as NTFS file systems just fine. hald, on the other hand, does not even see the slices. I suspect that you are looking in th right direction, though, and that hald uses some different method of finding partitions than the system and that it fails to work with the latest fuse code. I would suspect it is somewhere in hal-storage, though I am far from certain. I do have an exfat partition and I wonder it that is impacting things. I does cause somethings odd to happen as it shows up as two slices in the "gpart list" output but I can't see why hald would suddenly be able to deal with it when I mount one slice.. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com From owner-freebsd-gnome@FreeBSD.ORG Mon Jan 6 17:47:18 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 4C64E7E7; Mon, 6 Jan 2014 17:47:18 +0000 (UTC) Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D99511922; Mon, 6 Jan 2014 17:47:17 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ah4FAKzrylKtJXHA/2dsb2JhbABYgws4uh6BDBZ0giUBAQEEeAEQCw4KCRYPCQMCAQIBDzYGAQwBBQIBAYdsAxG+Ww2EQheMfBkVgWUHhDcBA4lDjGiORgOFOINLHg X-IronPort-AV: E=Sophos;i="4.95,614,1384300800"; d="scan'208";a="10849906" Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by alln-iport-2.cisco.com with ESMTP; 06 Jan 2014 17:47:10 +0000 Received: from dhcp-10-150-53-233.cisco.com (dhcp-10-150-53-233.cisco.com [10.150.53.233]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id s06HlA4o009135; Mon, 6 Jan 2014 17:47:10 GMT Message-ID: <52CAEC1E.2070908@marcuscom.com> Date: Mon, 06 Jan 2014 12:47:10 -0500 From: Joe Marcus Clarke User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Alberto Villa , Kevin Oberman Subject: Re: hal, ntfs, and 10.0-RC3 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD GNOME Users 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 17:47:18 -0000 On 1/6/14, 2:01 AM, Alberto Villa wrote: > 2014/1/6 Kevin Oberman : >> 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. >> >> 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. > > I've done some work on HAL in past months, so I have a view on the matter. > > HAL uses sysctl for disks detection, so it's up to the system to list > all the available drives. I'll try to have a look in next days, but my > wild guess (since I've not been using ntfs-3g for years) is that > ntfs-3g unloads its module when all mounts are removed, thus making > the drives undetectable again. Is that correct? HAL uses libvolume_id to taste the volumes to determine the file system type. It relies on sysctl to enumerate the disks and volumes as you've pointed out. What does sysctl -b kern.geom.conftxt say? Each partition listed there should go through libvolume_id detection. Joe > -- PGP Key : http://www.marcuscom.com/pgp.asc From owner-freebsd-gnome@FreeBSD.ORG Mon Jan 6 18:55:57 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 F2F7D991; Mon, 6 Jan 2014 18:55:56 +0000 (UTC) Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C17171F51; Mon, 6 Jan 2014 18:55:56 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id fa1so18828893pad.24 for ; Mon, 06 Jan 2014 10:55:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=1DEb8c8e02MhWPvYosb5dpWugS5dWQ7N4HX9hOuPzVo=; b=ySY8Spgs3eEDHzoHMmcAehY6OuqiCfqAaOmco2e1NLAEa5+b3Pr0RI7hFzth+HtM/T E42ZoVIvLeLIe77j94e0huylvazVdPx+L4etY0x1QKQSXrUxlUXxDVICzSKCJJiD6Erx hR9URN2WckagKmxSnpvl3yzTEyJHQd4/hvF4upWHBK4/sJ3jq6YqQXlQDHtmx3LFDiJg +Cb9g7Nb1VyfHb9KqKq6PvMPAwd7957cSPTO0AKrZeGMdjNooaRU0FUPHCFvaOtZ0urz edwBp8VrmJ3idUBTqfXhfM6+UXSRAXEgvpcb3rrA4r4gO0q0GYdLzijK5C+r4KHuIzLO IX3A== MIME-Version: 1.0 X-Received: by 10.66.242.17 with SMTP id wm17mr466431pac.102.1389034556458; Mon, 06 Jan 2014 10:55:56 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.67.23.101 with HTTP; Mon, 6 Jan 2014 10:55:56 -0800 (PST) In-Reply-To: <52CAEC1E.2070908@marcuscom.com> References: <52CAEC1E.2070908@marcuscom.com> Date: Mon, 6 Jan 2014 10:55:56 -0800 X-Google-Sender-Auth: kZBQBmHM8WG0Tr-pqn2wvVRDGI8 Message-ID: Subject: Re: hal, ntfs, and 10.0-RC3 From: Kevin Oberman To: Joe Marcus Clarke Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD GNOME Users 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 18:55:57 -0000 On Mon, Jan 6, 2014 at 9:47 AM, Joe Marcus Clarke wrote: > On 1/6/14, 2:01 AM, Alberto Villa wrote: > > 2014/1/6 Kevin Oberman : > >> 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. > >> > >> 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. > > > > I've done some work on HAL in past months, so I have a view on the > matter. > > > > HAL uses sysctl for disks detection, so it's up to the system to list > > all the available drives. I'll try to have a look in next days, but my > > wild guess (since I've not been using ntfs-3g for years) is that > > ntfs-3g unloads its module when all mounts are removed, thus making > > the drives undetectable again. Is that correct? > > HAL uses libvolume_id to taste the volumes to determine the file system > type. It relies on sysctl to enumerate the disks and volumes as you've > pointed out. What does sysctl -b kern.geom.conftxt say? Each partition > listed there should go through libvolume_id detection. > > Joe > > Joe, Looks good to me, but hald does not seem to see it: 0 DISK ada0 750156374016 512 hd 1 sc 63 1 LABEL diskid/DISK-WD-WX21A61N8718 750156374016 512 i 0 o 0 2 PART diskid/DISK-WD-WX21A61N8718s4 16833839104 512 i 4 o 733319528448 ty ntfs xs MBR xt 7 2 PART diskid/DISK-WD-WX21A61N8718s3 241172480000 512 i 3 o 492147048448 ty ebr xs MBR xt 15 3 PART diskid/DISK-WD-WX21A61N8718s5 241171431424 512 i 1 o 1048576 ty ntfs xs MBREXT xt 7 2 PART diskid/DISK-WD-WX21A61N8718s2 490887708672 512 i 2 o 1259339776 ty ntfs xs MBR xt 7 2 PART diskid/DISK-WD-WX21A61N8718s1 1258291200 512 i 1 o 1048576 ty ntfs xs MBR xt 7 1 PART ada0s4 16833839104 512 i 4 o 733319528448 ty ntfs xs MBR xt 7 2 LABEL ntfs/Lenovo_Recovery 16833839104 512 i 0 o 0 1 PART ada0s3 241172480000 512 i 3 o 492147048448 ty ebr xs MBR xt 15 2 PART ada0s5 241171431424 512 i 1 o 1048576 ty ntfs xs MBREXT xt 7 1 PART ada0s2 490887708672 512 i 2 o 1259339776 ty ntfs xs MBR xt 7 2 LABEL ntfs/Windows7_OS 490887708672 512 i 0 o 0 1 PART ada0s1 1258291200 512 i 1 o 1048576 ty ntfs xs MBR xt 7 2 LABEL ntfs/SYSTEM_DRV 1258291200 512 i 0 o 0 # lshal | grep ada0 block.device = '/dev/ada0' (string) freebsd.device_file = '/dev/ada0' (string) So hald sees the disk, but none of the partitions (slices). Could the "2 PART ada0s5" be messing things up? The disk has only four slices (it's MBR formatted). I think I will boot Windows and see wat it says about the partitioning. # 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) Slice 1 is the weird SYSTEM_DRV, 2 is Windows7_OS, 3 is an exfat file system named "Media", and 4 is the "Lenovo_Recovery" file system. But geom sees a mysterious fifth one that it says is NTFS??? Still, a soon as I mount the seconds slice, hald "sees" all of them. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com From owner-freebsd-gnome@FreeBSD.ORG Mon Jan 6 19:09:02 2014 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8E85EEFB; Mon, 6 Jan 2014 19:09:02 +0000 (UTC) Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 42096112B; Mon, 6 Jan 2014 19:09:01 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiAFAOL+ylKtJXG+/2dsb2JhbABYgws4g1O2TYENFnSCJQEBAQQjVQEQCw4KAgIFFggDAgIJAwIBAgEPJQMBDQYNAQUCAQGHbAMRqUaVFA2EQheBKYtTGRWBZQeCb4FIBIlDgzCJOI5GA4U4g0se X-IronPort-AV: E=Sophos;i="4.95,614,1384300800"; d="scan'208";a="295575132" Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-8.cisco.com with ESMTP; 06 Jan 2014 19:09:00 +0000 Received: from dhcp-10-150-53-233.cisco.com (dhcp-10-150-53-233.cisco.com [10.150.53.233]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id s06J90uh010444; Mon, 6 Jan 2014 19:09:00 GMT Message-ID: <52CAFF4C.8020408@marcuscom.com> Date: Mon, 06 Jan 2014 14:09:00 -0500 From: Joe Marcus Clarke User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Kevin Oberman Subject: Re: hal, ntfs, and 10.0-RC3 References: <52CAEC1E.2070908@marcuscom.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: FreeBSD GNOME Users 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 19:09:02 -0000 On 1/6/14, 1:55 PM, Kevin Oberman wrote: > On Mon, Jan 6, 2014 at 9:47 AM, Joe Marcus Clarke > wrote: > > On 1/6/14, 2:01 AM, Alberto Villa wrote: > > 2014/1/6 Kevin Oberman >: > >> 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. > >> > >> 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. > > > > I've done some work on HAL in past months, so I have a view on the > matter. > > > > HAL uses sysctl for disks detection, so it's up to the system to list > > all the available drives. I'll try to have a look in next days, but my > > wild guess (since I've not been using ntfs-3g for years) is that > > ntfs-3g unloads its module when all mounts are removed, thus making > > the drives undetectable again. Is that correct? > > HAL uses libvolume_id to taste the volumes to determine the file system > type. It relies on sysctl to enumerate the disks and volumes as you've > pointed out. What does sysctl -b kern.geom.conftxt say? Each partition > listed there should go through libvolume_id detection. > > Joe > > > Joe, > > Looks good to me, but hald does not seem to see it: > > 0 DISK ada0 750156374016 512 hd 1 sc 63 > 1 LABEL diskid/DISK-WD-WX21A61N8718 750156374016 512 i 0 o 0 > 2 PART diskid/DISK-WD-WX21A61N8718s4 16833839104 512 i 4 o 733319528448 > ty ntfs xs MBR xt 7 > 2 PART diskid/DISK-WD-WX21A61N8718s3 241172480000 512 i 3 o 492147048448 > ty ebr xs MBR xt 15 > 3 PART diskid/DISK-WD-WX21A61N8718s5 241171431424 512 i 1 o 1048576 ty > ntfs xs MBREXT xt 7 > 2 PART diskid/DISK-WD-WX21A61N8718s2 490887708672 512 i 2 o 1259339776 > ty ntfs xs MBR xt 7 > 2 PART diskid/DISK-WD-WX21A61N8718s1 1258291200 512 i 1 o 1048576 ty > ntfs xs MBR xt 7 > 1 PART ada0s4 16833839104 512 i 4 o 733319528448 ty ntfs xs MBR xt 7 > 2 LABEL ntfs/Lenovo_Recovery 16833839104 512 i 0 o 0 > 1 PART ada0s3 241172480000 512 i 3 o 492147048448 ty ebr xs MBR xt 15 > 2 PART ada0s5 241171431424 512 i 1 o 1048576 ty ntfs xs MBREXT xt 7 > 1 PART ada0s2 490887708672 512 i 2 o 1259339776 ty ntfs xs MBR xt 7 > 2 LABEL ntfs/Windows7_OS 490887708672 512 i 0 o 0 > 1 PART ada0s1 1258291200 512 i 1 o 1048576 ty ntfs xs MBR xt 7 > 2 LABEL ntfs/SYSTEM_DRV 1258291200 512 i 0 o 0 > # lshal | grep ada0 > block.device = '/dev/ada0' (string) > freebsd.device_file = '/dev/ada0' (string) > > So hald sees the disk, but none of the partitions (slices). Could the "2 > PART ada0s5" be messing things up? The disk has only four slices (it's > MBR formatted). I think I will boot Windows and see wat it says about > the partitioning. > # 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) > Slice 1 is the weird SYSTEM_DRV, 2 is Windows7_OS, 3 is an exfat file > system named "Media", and 4 is the "Lenovo_Recovery" file system. But > geom sees a mysterious fifth one that it says is NTFS??? Still, a soon > as I mount the seconds slice, hald "sees" all of them. > -- > R. Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com I don't suppose you have a 9.X output of the conftxt? This is one area where HAL could use an update to use confxml or the like. It's tied to the output of conftxt and thus the format of it. I have a feeling this format is different. I'll have to look over the code... Joe -- PGP Key : http://www.marcuscom.com/pgp.asc From owner-freebsd-gnome@FreeBSD.ORG Mon Jan 6 22:50:40 2014 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6567D9DD; Mon, 6 Jan 2014 22:50:40 +0000 (UTC) Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 31F101243; Mon, 6 Jan 2014 22:50:40 +0000 (UTC) Received: by mail-pb0-f52.google.com with SMTP id uo5so19157355pbc.39 for ; Mon, 06 Jan 2014 14:50:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=H6HslgI2COWPRHxa6oGjYr78kKILxpPLTcLfCnLOsTU=; b=dJxnYpUsVe/2CTD6lpTs+VvHyARvq156tN/80JRJFz9BxNDVgIxNHSyJD9bX9PFzPc VbdAcbeRJVgQTCtniGRk9LRrQfwcbZOJbt6PyCOFbfPGGj4SHfHPlQ+nhWqNMCNCIKzz ih7UFr0txD+6gkT7JqL48ZEVI4jjmjGX9oOYwmCfNaJbbKoYDoOnWhzjr5oJv5Md0aCK wbdnZTPUu0seCa7azTwfFLK/0DBtz07LbxTLTpFAvIIzb08d6H+rsYyRrzobLpH9XBUM JT3ZaDPT4rR+rUwA72olvGJIv+o1yxPe/kgLHn9qvzdErGmZANAISEQmUCyPGMg3cKC4 MhSQ== MIME-Version: 1.0 X-Received: by 10.68.227.36 with SMTP id rx4mr10339145pbc.164.1389048639728; Mon, 06 Jan 2014 14:50:39 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.67.23.101 with HTTP; Mon, 6 Jan 2014 14:50:39 -0800 (PST) In-Reply-To: <52CAFF4C.8020408@marcuscom.com> References: <52CAEC1E.2070908@marcuscom.com> <52CAFF4C.8020408@marcuscom.com> Date: Mon, 6 Jan 2014 14:50:39 -0800 X-Google-Sender-Auth: VQgmZnuHEzdrkjUvkdi9XQljPy0 Message-ID: Subject: Re: hal, ntfs, and 10.0-RC3 From: Kevin Oberman To: Joe Marcus Clarke Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD GNOME Users 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 22:50:40 -0000 On Mon, Jan 6, 2014 at 11:09 AM, Joe Marcus Clarke wrote: > On 1/6/14, 1:55 PM, Kevin Oberman wrote: > > On Mon, Jan 6, 2014 at 9:47 AM, Joe Marcus Clarke > > wrote: > > > > On 1/6/14, 2:01 AM, Alberto Villa wrote: > > > 2014/1/6 Kevin Oberman > >: > > >> 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. > > >> > > >> 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. > > > > > > I've done some work on HAL in past months, so I have a view on the > > matter. > > > > > > HAL uses sysctl for disks detection, so it's up to the system to > list > > > all the available drives. I'll try to have a look in next days, > but my > > > wild guess (since I've not been using ntfs-3g for years) is that > > > ntfs-3g unloads its module when all mounts are removed, thus making > > > the drives undetectable again. Is that correct? > > > > HAL uses libvolume_id to taste the volumes to determine the file > system > > type. It relies on sysctl to enumerate the disks and volumes as > you've > > pointed out. What does sysctl -b kern.geom.conftxt say? Each > partition > > listed there should go through libvolume_id detection. > > > > Joe > > > > > > Joe, > > > > Looks good to me, but hald does not seem to see it: > > > > 0 DISK ada0 750156374016 512 hd 1 sc 63 > > 1 LABEL diskid/DISK-WD-WX21A61N8718 750156374016 512 i 0 o 0 > > 2 PART diskid/DISK-WD-WX21A61N8718s4 16833839104 512 i 4 o 733319528448 > > ty ntfs xs MBR xt 7 > > 2 PART diskid/DISK-WD-WX21A61N8718s3 241172480000 512 i 3 o 492147048448 > > ty ebr xs MBR xt 15 > > 3 PART diskid/DISK-WD-WX21A61N8718s5 241171431424 512 i 1 o 1048576 ty > > ntfs xs MBREXT xt 7 > > 2 PART diskid/DISK-WD-WX21A61N8718s2 490887708672 512 i 2 o 1259339776 > > ty ntfs xs MBR xt 7 > > 2 PART diskid/DISK-WD-WX21A61N8718s1 1258291200 512 i 1 o 1048576 ty > > ntfs xs MBR xt 7 > > 1 PART ada0s4 16833839104 512 i 4 o 733319528448 ty ntfs xs MBR xt 7 > > 2 LABEL ntfs/Lenovo_Recovery 16833839104 512 i 0 o 0 > > 1 PART ada0s3 241172480000 512 i 3 o 492147048448 ty ebr xs MBR xt 15 > > 2 PART ada0s5 241171431424 512 i 1 o 1048576 ty ntfs xs MBREXT xt 7 > > 1 PART ada0s2 490887708672 512 i 2 o 1259339776 ty ntfs xs MBR xt 7 > > 2 LABEL ntfs/Windows7_OS 490887708672 512 i 0 o 0 > > 1 PART ada0s1 1258291200 512 i 1 o 1048576 ty ntfs xs MBR xt 7 > > 2 LABEL ntfs/SYSTEM_DRV 1258291200 512 i 0 o 0 > > # lshal | grep ada0 > > block.device = '/dev/ada0' (string) > > freebsd.device_file = '/dev/ada0' (string) > > > > So hald sees the disk, but none of the partitions (slices). Could the "2 > > PART ada0s5" be messing things up? The disk has only four slices (it's > > MBR formatted). I think I will boot Windows and see wat it says about > > the partitioning. > > # 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) > > Slice 1 is the weird SYSTEM_DRV, 2 is Windows7_OS, 3 is an exfat file > > system named "Media", and 4 is the "Lenovo_Recovery" file system. But > > geom sees a mysterious fifth one that it says is NTFS??? Still, a soon > > as I mount the seconds slice, hald "sees" all of them. > > -- > > R. Kevin Oberman, Network Engineer, Retired > > E-mail: rkoberman@gmail.com > > I don't suppose you have a 9.X output of the conftxt? This is one area > where HAL could use an update to use confxml or the like. It's tied to > the output of conftxt and thus the format of it. I have a feeling this > format is different. I'll have to look over the code... > > Nope. I'm afraid I blew away my 9 backup yesterday to prep to update to RC4. And, to make matters worse, after re-booting, I can no longer get my network to run so my system is pretty useless until I can figure out what I messed up. (Also had to fix a flat on my bike. Guess it's just not my day.) Using confxml would make a lot of sense, but it does not look like HAL has much of a future. Is it used on MATE? Pretty sure that it is not on Gnome3. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com From owner-freebsd-gnome@FreeBSD.ORG Mon Jan 6 23:15:12 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 460E7E9B; Mon, 6 Jan 2014 23:15:12 +0000 (UTC) Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F0BD914E0; Mon, 6 Jan 2014 23:15:11 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkQFADo4y1KtJXHB/2dsb2JhbABYgws4g1O2U4ELFnSCJQEBAQQjVQEQCw4KAgIFFggDAgIJAwIBAgEPJQMBDQYNAQUCAQGHbAMRqVqVHw2EZBeBKYtTGRV6IkkHgm+BSASJQ4MwiTiORgOFOINLHoEt X-IronPort-AV: E=Sophos;i="4.95,615,1384300800"; d="scan'208";a="10920843" Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by alln-iport-6.cisco.com with ESMTP; 06 Jan 2014 23:15:10 +0000 Received: from dhcp-10-150-53-233.cisco.com (dhcp-10-150-53-233.cisco.com [10.150.53.233]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id s06NF9Mr011849; Mon, 6 Jan 2014 23:15:09 GMT Message-ID: <52CB38FD.4050806@marcuscom.com> Date: Mon, 06 Jan 2014 18:15:09 -0500 From: Joe Marcus Clarke User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Kevin Oberman Subject: Re: hal, ntfs, and 10.0-RC3 References: <52CAEC1E.2070908@marcuscom.com> <52CAFF4C.8020408@marcuscom.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: FreeBSD GNOME Users 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 23:15:12 -0000 On 1/6/14, 5:50 PM, Kevin Oberman wrote: > > > > On Mon, Jan 6, 2014 at 11:09 AM, Joe Marcus Clarke > wrote: > > On 1/6/14, 1:55 PM, Kevin Oberman wrote: > > On Mon, Jan 6, 2014 at 9:47 AM, Joe Marcus Clarke > > > >> wrote: > > > > On 1/6/14, 2:01 AM, Alberto Villa wrote: > > > 2014/1/6 Kevin Oberman > > >>: > > >> 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. > > >> > > >> 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. > > > > > > I've done some work on HAL in past months, so I have a view > on the > > matter. > > > > > > HAL uses sysctl for disks detection, so it's up to the > system to list > > > all the available drives. I'll try to have a look in next > days, but my > > > wild guess (since I've not been using ntfs-3g for years) is that > > > ntfs-3g unloads its module when all mounts are removed, thus > making > > > the drives undetectable again. Is that correct? > > > > HAL uses libvolume_id to taste the volumes to determine the > file system > > type. It relies on sysctl to enumerate the disks and volumes > as you've > > pointed out. What does sysctl -b kern.geom.conftxt say? Each > partition > > listed there should go through libvolume_id detection. > > > > Joe > > > > > > Joe, > > > > Looks good to me, but hald does not seem to see it: > > > > 0 DISK ada0 750156374016 512 hd 1 sc 63 > > 1 LABEL diskid/DISK-WD-WX21A61N8718 750156374016 512 i 0 o 0 > > 2 PART diskid/DISK-WD-WX21A61N8718s4 16833839104 512 i 4 o > 733319528448 > > ty ntfs xs MBR xt 7 > > 2 PART diskid/DISK-WD-WX21A61N8718s3 241172480000 512 i 3 o > 492147048448 > > ty ebr xs MBR xt 15 > > 3 PART diskid/DISK-WD-WX21A61N8718s5 241171431424 512 i 1 o 1048576 ty > > ntfs xs MBREXT xt 7 > > 2 PART diskid/DISK-WD-WX21A61N8718s2 490887708672 512 i 2 o 1259339776 > > ty ntfs xs MBR xt 7 > > 2 PART diskid/DISK-WD-WX21A61N8718s1 1258291200 512 i 1 o 1048576 ty > > ntfs xs MBR xt 7 > > 1 PART ada0s4 16833839104 512 i 4 o 733319528448 ty ntfs xs MBR xt 7 > > 2 LABEL ntfs/Lenovo_Recovery 16833839104 512 i 0 o 0 > > 1 PART ada0s3 241172480000 512 i 3 o 492147048448 ty ebr xs MBR xt 15 > > 2 PART ada0s5 241171431424 512 i 1 o 1048576 ty ntfs xs MBREXT xt 7 > > 1 PART ada0s2 490887708672 512 i 2 o 1259339776 ty ntfs xs MBR xt 7 > > 2 LABEL ntfs/Windows7_OS 490887708672 512 i 0 o 0 > > 1 PART ada0s1 1258291200 512 i 1 o 1048576 ty ntfs xs MBR xt 7 > > 2 LABEL ntfs/SYSTEM_DRV 1258291200 512 i 0 o 0 > > # lshal | grep ada0 > > block.device = '/dev/ada0' (string) > > freebsd.device_file = '/dev/ada0' (string) > > > > So hald sees the disk, but none of the partitions (slices). Could > the "2 > > PART ada0s5" be messing things up? The disk has only four slices (it's > > MBR formatted). I think I will boot Windows and see wat it says about > > the partitioning. > > # 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) > > Slice 1 is the weird SYSTEM_DRV, 2 is Windows7_OS, 3 is an exfat file > > system named "Media", and 4 is the "Lenovo_Recovery" file system. But > > geom sees a mysterious fifth one that it says is NTFS??? Still, a soon > > as I mount the seconds slice, hald "sees" all of them. > > -- > > R. Kevin Oberman, Network Engineer, Retired > > E-mail: rkoberman@gmail.com > > > > I don't suppose you have a 9.X output of the conftxt? This is one area > where HAL could use an update to use confxml or the like. It's tied to > the output of conftxt and thus the format of it. I have a feeling this > format is different. I'll have to look over the code... > > Nope. I'm afraid I blew away my 9 backup yesterday to prep to update to > RC4. And, to make matters worse, after re-booting, I can no longer get > my network to run so my system is pretty useless until I can figure out > what I messed up. (Also had to fix a flat on my bike. Guess it's just > not my day.) > > Using confxml would make a lot of sense, but it does not look like HAL > has much of a future. Is it used on MATE? Pretty sure that it is not on > Gnome3. In hf-storage.c in hald/freebsd, go to line 431. Change this "if" block to: if ((! strcmp(fields[1], "LABEL") || ! strcmp(fields[1], "BSD") || ! strcmp(fields[1], "PART")) && (! strncmp(fields[2], "ufsid/", strlen("ufsid/")) || ! strncmp(fields[2], "ufs/", strlen("ufs/")) ! strncmp(fields[2], "diskid/", strlen("diskid/")))) Rebuild hal, and see if that helps. Joe > -- > R. Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com -- PGP Key : http://www.marcuscom.com/pgp.asc From owner-freebsd-gnome@FreeBSD.ORG Mon Jan 6 23:23:23 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 76F4448F; Mon, 6 Jan 2014 23:23:23 +0000 (UTC) Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 41EDC15DF; Mon, 6 Jan 2014 23:23:23 +0000 (UTC) Received: by mail-pd0-f181.google.com with SMTP id p10so18744322pdj.12 for ; Mon, 06 Jan 2014 15:23:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=djxRPmJoYAXiOCIQPMu8A0vpKt7J38FOgEuzguOls7I=; b=AnctIu30MPZMSEWdSDgueceFEb009IeQQNy+s4ETWs808yrsO1Y4ZZaqXfO+VRqKR9 ui3mI3slqPoBYOoHOGhygqUczpTpNN0ZjFrBa39VsPsNk+sYbS3aqIJDeh3gF2dw+Qoi NimPcSqQNoT2XP/VVzxXlzC6FA7SBSEDoQMYNUoCYz6K3jvLwaoV7454QemBc2h8FA3l cCTDDqa29skxv/OVauRKVNHhJZdDTA+oQ2o9rc/iT8AhlbUqQOfvLJuVuu/KOCKQpfYT 5IMT0GkqQoR1ZuKW1ALTBh61eFCsuhFPWmhLD+V5tSzQERKATm9FdetITJtN8VeNqxlN R/0A== MIME-Version: 1.0 X-Received: by 10.69.19.225 with SMTP id gx1mr131254323pbd.62.1389050602255; Mon, 06 Jan 2014 15:23:22 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.67.23.101 with HTTP; Mon, 6 Jan 2014 15:23:22 -0800 (PST) In-Reply-To: <52CB38FD.4050806@marcuscom.com> References: <52CAEC1E.2070908@marcuscom.com> <52CAFF4C.8020408@marcuscom.com> <52CB38FD.4050806@marcuscom.com> Date: Mon, 6 Jan 2014 15:23:22 -0800 X-Google-Sender-Auth: 0ygxbTRl8u8Yz_tPoK39__ToJ8M Message-ID: Subject: Re: hal, ntfs, and 10.0-RC3 From: Kevin Oberman To: Joe Marcus Clarke Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD GNOME Users 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 23:23:23 -0000 On Mon, Jan 6, 2014 at 3:15 PM, Joe Marcus Clarke wrote: > On 1/6/14, 5:50 PM, Kevin Oberman wrote: > > > > > > > > On Mon, Jan 6, 2014 at 11:09 AM, Joe Marcus Clarke > > wrote: > > > > On 1/6/14, 1:55 PM, Kevin Oberman wrote: > > > On Mon, Jan 6, 2014 at 9:47 AM, Joe Marcus Clarke > > > > > >> > wrote: > > > > > > On 1/6/14, 2:01 AM, Alberto Villa wrote: > > > > 2014/1/6 Kevin Oberman > > > > >>: > > > >> 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. > > > >> > > > >> 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. > > > > > > > > I've done some work on HAL in past months, so I have a view > > on the > > > matter. > > > > > > > > HAL uses sysctl for disks detection, so it's up to the > > system to list > > > > all the available drives. I'll try to have a look in next > > days, but my > > > > wild guess (since I've not been using ntfs-3g for years) is > that > > > > ntfs-3g unloads its module when all mounts are removed, thus > > making > > > > the drives undetectable again. Is that correct? > > > > > > HAL uses libvolume_id to taste the volumes to determine the > > file system > > > type. It relies on sysctl to enumerate the disks and volumes > > as you've > > > pointed out. What does sysctl -b kern.geom.conftxt say? Each > > partition > > > listed there should go through libvolume_id detection. > > > > > > Joe > > > > > > > > > Joe, > > > > > > Looks good to me, but hald does not seem to see it: > > > > > > 0 DISK ada0 750156374016 512 hd 1 sc 63 > > > 1 LABEL diskid/DISK-WD-WX21A61N8718 750156374016 512 i 0 o 0 > > > 2 PART diskid/DISK-WD-WX21A61N8718s4 16833839104 512 i 4 o > > 733319528448 > > > ty ntfs xs MBR xt 7 > > > 2 PART diskid/DISK-WD-WX21A61N8718s3 241172480000 512 i 3 o > > 492147048448 > > > ty ebr xs MBR xt 15 > > > 3 PART diskid/DISK-WD-WX21A61N8718s5 241171431424 512 i 1 o > 1048576 ty > > > ntfs xs MBREXT xt 7 > > > 2 PART diskid/DISK-WD-WX21A61N8718s2 490887708672 512 i 2 o > 1259339776 > > > ty ntfs xs MBR xt 7 > > > 2 PART diskid/DISK-WD-WX21A61N8718s1 1258291200 512 i 1 o 1048576 > ty > > > ntfs xs MBR xt 7 > > > 1 PART ada0s4 16833839104 512 i 4 o 733319528448 ty ntfs xs MBR xt > 7 > > > 2 LABEL ntfs/Lenovo_Recovery 16833839104 512 i 0 o 0 > > > 1 PART ada0s3 241172480000 512 i 3 o 492147048448 ty ebr xs MBR xt > 15 > > > 2 PART ada0s5 241171431424 512 i 1 o 1048576 ty ntfs xs MBREXT xt 7 > > > 1 PART ada0s2 490887708672 512 i 2 o 1259339776 ty ntfs xs MBR xt 7 > > > 2 LABEL ntfs/Windows7_OS 490887708672 512 i 0 o 0 > > > 1 PART ada0s1 1258291200 512 i 1 o 1048576 ty ntfs xs MBR xt 7 > > > 2 LABEL ntfs/SYSTEM_DRV 1258291200 512 i 0 o 0 > > > # lshal | grep ada0 > > > block.device = '/dev/ada0' (string) > > > freebsd.device_file = '/dev/ada0' (string) > > > > > > So hald sees the disk, but none of the partitions (slices). Could > > the "2 > > > PART ada0s5" be messing things up? The disk has only four slices > (it's > > > MBR formatted). I think I will boot Windows and see wat it says > about > > > the partitioning. > > > # 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) > > > Slice 1 is the weird SYSTEM_DRV, 2 is Windows7_OS, 3 is an exfat > file > > > system named "Media", and 4 is the "Lenovo_Recovery" file system. > But > > > geom sees a mysterious fifth one that it says is NTFS??? Still, a > soon > > > as I mount the seconds slice, hald "sees" all of them. > > > -- > > > R. Kevin Oberman, Network Engineer, Retired > > > E-mail: rkoberman@gmail.com > > > > > > > I don't suppose you have a 9.X output of the conftxt? This is one > area > > where HAL could use an update to use confxml or the like. It's tied > to > > the output of conftxt and thus the format of it. I have a feeling > this > > format is different. I'll have to look over the code... > > > > Nope. I'm afraid I blew away my 9 backup yesterday to prep to update to > > RC4. And, to make matters worse, after re-booting, I can no longer get > > my network to run so my system is pretty useless until I can figure out > > what I messed up. (Also had to fix a flat on my bike. Guess it's just > > not my day.) > > > > Using confxml would make a lot of sense, but it does not look like HAL > > has much of a future. Is it used on MATE? Pretty sure that it is not on > > Gnome3. > > In hf-storage.c in hald/freebsd, go to line 431. Change this "if" block > to: > > if ((! strcmp(fields[1], "LABEL") || > ! strcmp(fields[1], "BSD") || > ! strcmp(fields[1], "PART")) && > (! strncmp(fields[2], "ufsid/", strlen("ufsid/")) || > ! strncmp(fields[2], "ufs/", strlen("ufs/")) > ! strncmp(fields[2], "diskid/", strlen("diskid/")))) > > Rebuild hal, and see if that helps. > > Joe > Joe, Shouldn't there be an OR (||) after the next to last line? (I'm going to assume so and build that way.) Thanks! -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com From owner-freebsd-gnome@FreeBSD.ORG Tue Jan 7 00:01:11 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 8E28D6A0; Tue, 7 Jan 2014 00:01:11 +0000 (UTC) Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4C9F71909; Tue, 7 Jan 2014 00:01:10 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkQFAIJCy1KtJXG+/2dsb2JhbABYgws4g1O2WIEMFnSCJQEBAQQjVQEQCw4KAgIFFggDAgIJAwIBAgEPJQMBDQYNAQUCAQGHbAMRqVuVHg2EZBeBKYtTGRV6IkkHgm+BSASJQ4MwiTiORgOFOINLHoEt X-IronPort-AV: E=Sophos;i="4.95,615,1384300800"; d="scan'208";a="295699791" Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-4.cisco.com with ESMTP; 07 Jan 2014 00:01:09 +0000 Received: from dhcp-10-150-53-233.cisco.com (dhcp-10-150-53-233.cisco.com [10.150.53.233]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id s07019CH004202; Tue, 7 Jan 2014 00:01:09 GMT Message-ID: <52CB43C5.6030303@marcuscom.com> Date: Mon, 06 Jan 2014 19:01:09 -0500 From: Joe Marcus Clarke User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Kevin Oberman Subject: Re: hal, ntfs, and 10.0-RC3 References: <52CAEC1E.2070908@marcuscom.com> <52CAFF4C.8020408@marcuscom.com> <52CB38FD.4050806@marcuscom.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: FreeBSD GNOME Users 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: Tue, 07 Jan 2014 00:01:11 -0000 On 1/6/14, 6:23 PM, Kevin Oberman wrote: > On Mon, Jan 6, 2014 at 3:15 PM, Joe Marcus Clarke > wrote: > > On 1/6/14, 5:50 PM, Kevin Oberman wrote: > > > > > > > > On Mon, Jan 6, 2014 at 11:09 AM, Joe Marcus Clarke > > > >> wrote: > > > > On 1/6/14, 1:55 PM, Kevin Oberman wrote: > > > On Mon, Jan 6, 2014 at 9:47 AM, Joe Marcus Clarke > > > > > > > > >>> wrote: > > > > > > On 1/6/14, 2:01 AM, Alberto Villa wrote: > > > > 2014/1/6 Kevin Oberman > > > > > > > >>>: > > > >> 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. > > > >> > > > >> 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. > > > > > > > > I've done some work on HAL in past months, so I have a > view > > on the > > > matter. > > > > > > > > HAL uses sysctl for disks detection, so it's up to the > > system to list > > > > all the available drives. I'll try to have a look in next > > days, but my > > > > wild guess (since I've not been using ntfs-3g for > years) is that > > > > ntfs-3g unloads its module when all mounts are > removed, thus > > making > > > > the drives undetectable again. Is that correct? > > > > > > HAL uses libvolume_id to taste the volumes to determine the > > file system > > > type. It relies on sysctl to enumerate the disks and > volumes > > as you've > > > pointed out. What does sysctl -b kern.geom.conftxt say? > Each > > partition > > > listed there should go through libvolume_id detection. > > > > > > Joe > > > > > > > > > Joe, > > > > > > Looks good to me, but hald does not seem to see it: > > > > > > 0 DISK ada0 750156374016 512 hd 1 sc 63 > > > 1 LABEL diskid/DISK-WD-WX21A61N8718 750156374016 512 i 0 o 0 > > > 2 PART diskid/DISK-WD-WX21A61N8718s4 16833839104 512 i 4 o > > 733319528448 > > > ty ntfs xs MBR xt 7 > > > 2 PART diskid/DISK-WD-WX21A61N8718s3 241172480000 512 i 3 o > > 492147048448 > > > ty ebr xs MBR xt 15 > > > 3 PART diskid/DISK-WD-WX21A61N8718s5 241171431424 512 i 1 o > 1048576 ty > > > ntfs xs MBREXT xt 7 > > > 2 PART diskid/DISK-WD-WX21A61N8718s2 490887708672 512 i 2 o > 1259339776 > > > ty ntfs xs MBR xt 7 > > > 2 PART diskid/DISK-WD-WX21A61N8718s1 1258291200 512 i 1 o > 1048576 ty > > > ntfs xs MBR xt 7 > > > 1 PART ada0s4 16833839104 512 i 4 o 733319528448 ty ntfs xs > MBR xt 7 > > > 2 LABEL ntfs/Lenovo_Recovery 16833839104 512 i 0 o 0 > > > 1 PART ada0s3 241172480000 512 i 3 o 492147048448 ty ebr xs > MBR xt 15 > > > 2 PART ada0s5 241171431424 512 i 1 o 1048576 ty ntfs xs > MBREXT xt 7 > > > 1 PART ada0s2 490887708672 512 i 2 o 1259339776 ty ntfs xs > MBR xt 7 > > > 2 LABEL ntfs/Windows7_OS 490887708672 512 i 0 o 0 > > > 1 PART ada0s1 1258291200 512 i 1 o 1048576 ty ntfs xs MBR xt 7 > > > 2 LABEL ntfs/SYSTEM_DRV 1258291200 512 i 0 o 0 > > > # lshal | grep ada0 > > > block.device = '/dev/ada0' (string) > > > freebsd.device_file = '/dev/ada0' (string) > > > > > > So hald sees the disk, but none of the partitions (slices). > Could > > the "2 > > > PART ada0s5" be messing things up? The disk has only four > slices (it's > > > MBR formatted). I think I will boot Windows and see wat it > says about > > > the partitioning. > > > # 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) > > > Slice 1 is the weird SYSTEM_DRV, 2 is Windows7_OS, 3 is an > exfat file > > > system named "Media", and 4 is the "Lenovo_Recovery" file > system. But > > > geom sees a mysterious fifth one that it says is NTFS??? > Still, a soon > > > as I mount the seconds slice, hald "sees" all of them. > > > -- > > > R. Kevin Oberman, Network Engineer, Retired > > > E-mail: rkoberman@gmail.com > > > > > >> > > > > I don't suppose you have a 9.X output of the conftxt? This is > one area > > where HAL could use an update to use confxml or the like. > It's tied to > > the output of conftxt and thus the format of it. I have a > feeling this > > format is different. I'll have to look over the code... > > > > Nope. I'm afraid I blew away my 9 backup yesterday to prep to > update to > > RC4. And, to make matters worse, after re-booting, I can no > longer get > > my network to run so my system is pretty useless until I can > figure out > > what I messed up. (Also had to fix a flat on my bike. Guess it's just > > not my day.) > > > > Using confxml would make a lot of sense, but it does not look like HAL > > has much of a future. Is it used on MATE? Pretty sure that it is > not on > > Gnome3. > > In hf-storage.c in hald/freebsd, go to line 431. Change this "if" > block to: > > if ((! strcmp(fields[1], "LABEL") || > ! strcmp(fields[1], "BSD") || > ! strcmp(fields[1], "PART")) && > (! strncmp(fields[2], "ufsid/", strlen("ufsid/")) || > ! strncmp(fields[2], "ufs/", strlen("ufs/")) > ! strncmp(fields[2], "diskid/", strlen("diskid/")))) > > Rebuild hal, and see if that helps. > > Joe > > > Joe, > > Shouldn't there be an OR (||) after the next to last line? (I'm going > to assume so and build that way.) Whoops. Yeah, add the ||. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc From owner-freebsd-gnome@FreeBSD.ORG Tue Jan 7 00:10:16 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 741DCB7B; Tue, 7 Jan 2014 00:10:16 +0000 (UTC) Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3E96619E4; Tue, 7 Jan 2014 00:10:16 +0000 (UTC) Received: by mail-pb0-f44.google.com with SMTP id rq2so19163936pbb.31 for ; Mon, 06 Jan 2014 16:10:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=A+84ElJ+gDuHuEHwwWcqIIMBvVpZp5c9x1dbbGBNUOc=; b=yLydba4Pz3heXwLwCp7OcQ0X+/X3GLMEBgy3GLRWRwahBlM8hlgCTWuWi+Q+DEG1eM xh4p3jiEqlaZEOG4kRCJleYMa7HI1FKuiGNg/BQHGP9VGUOVtwzFgEh8UrBlmmHnovOP IClpuNGUzubzzKXwpqZV3cSnKcHKg1VSeb7djapUIvyIkrt0KoNUt6owlxjpvn38G4VH 86WNR3IgK9WEaJdSdzgwNwIZqeNGtkU4+2papZP0RBhgz3HCsx9oMVfh8B1/jEXnYeRS eVbp5J4grgk58UUKUp4bOpLjkWI+ypoAwKjUmOHfvDAqxbWFQ6sVrPOTtWz+pRKEF2GL 3FHQ== MIME-Version: 1.0 X-Received: by 10.66.242.17 with SMTP id wm17mr1404658pac.102.1389053415530; Mon, 06 Jan 2014 16:10:15 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.67.23.101 with HTTP; Mon, 6 Jan 2014 16:10:15 -0800 (PST) In-Reply-To: References: <52CAEC1E.2070908@marcuscom.com> <52CAFF4C.8020408@marcuscom.com> <52CB38FD.4050806@marcuscom.com> Date: Mon, 6 Jan 2014 16:10:15 -0800 X-Google-Sender-Auth: xbRl1ihFwN_Sl7IMmvtrfI13wvM Message-ID: Subject: Re: hal, ntfs, and 10.0-RC3 From: Kevin Oberman To: Joe Marcus Clarke Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD GNOME Users 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: Tue, 07 Jan 2014 00:10:16 -0000 On Mon, Jan 6, 2014 at 3:23 PM, Kevin Oberman wrote: > On Mon, Jan 6, 2014 at 3:15 PM, Joe Marcus Clarke wrote: > >> On 1/6/14, 5:50 PM, Kevin Oberman wrote: >> > >> > >> > >> > On Mon, Jan 6, 2014 at 11:09 AM, Joe Marcus Clarke < >> marcus@marcuscom.com >> > > wrote: >> > >> > On 1/6/14, 1:55 PM, Kevin Oberman wrote: >> > > On Mon, Jan 6, 2014 at 9:47 AM, Joe Marcus Clarke >> > >> > > >> >> wrote: >> > > >> > > On 1/6/14, 2:01 AM, Alberto Villa wrote: >> > > > 2014/1/6 Kevin Oberman > > >> > > >>: >> > > >> 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. >> > > >> >> > > >> 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. >> > > > >> > > > I've done some work on HAL in past months, so I have a view >> > on the >> > > matter. >> > > > >> > > > HAL uses sysctl for disks detection, so it's up to the >> > system to list >> > > > all the available drives. I'll try to have a look in next >> > days, but my >> > > > wild guess (since I've not been using ntfs-3g for years) is >> that >> > > > ntfs-3g unloads its module when all mounts are removed, thus >> > making >> > > > the drives undetectable again. Is that correct? >> > > >> > > HAL uses libvolume_id to taste the volumes to determine the >> > file system >> > > type. It relies on sysctl to enumerate the disks and volumes >> > as you've >> > > pointed out. What does sysctl -b kern.geom.conftxt say? Each >> > partition >> > > listed there should go through libvolume_id detection. >> > > >> > > Joe >> > > >> > > >> > > Joe, >> > > >> > > Looks good to me, but hald does not seem to see it: >> > > >> > > 0 DISK ada0 750156374016 512 hd 1 sc 63 >> > > 1 LABEL diskid/DISK-WD-WX21A61N8718 750156374016 512 i 0 o 0 >> > > 2 PART diskid/DISK-WD-WX21A61N8718s4 16833839104 512 i 4 o >> > 733319528448 >> > > ty ntfs xs MBR xt 7 >> > > 2 PART diskid/DISK-WD-WX21A61N8718s3 241172480000 512 i 3 o >> > 492147048448 >> > > ty ebr xs MBR xt 15 >> > > 3 PART diskid/DISK-WD-WX21A61N8718s5 241171431424 512 i 1 o >> 1048576 ty >> > > ntfs xs MBREXT xt 7 >> > > 2 PART diskid/DISK-WD-WX21A61N8718s2 490887708672 512 i 2 o >> 1259339776 >> > > ty ntfs xs MBR xt 7 >> > > 2 PART diskid/DISK-WD-WX21A61N8718s1 1258291200 512 i 1 o 1048576 >> ty >> > > ntfs xs MBR xt 7 >> > > 1 PART ada0s4 16833839104 512 i 4 o 733319528448 ty ntfs xs MBR >> xt 7 >> > > 2 LABEL ntfs/Lenovo_Recovery 16833839104 512 i 0 o 0 >> > > 1 PART ada0s3 241172480000 512 i 3 o 492147048448 ty ebr xs MBR >> xt 15 >> > > 2 PART ada0s5 241171431424 512 i 1 o 1048576 ty ntfs xs MBREXT xt >> 7 >> > > 1 PART ada0s2 490887708672 512 i 2 o 1259339776 ty ntfs xs MBR xt >> 7 >> > > 2 LABEL ntfs/Windows7_OS 490887708672 512 i 0 o 0 >> > > 1 PART ada0s1 1258291200 512 i 1 o 1048576 ty ntfs xs MBR xt 7 >> > > 2 LABEL ntfs/SYSTEM_DRV 1258291200 512 i 0 o 0 >> > > # lshal | grep ada0 >> > > block.device = '/dev/ada0' (string) >> > > freebsd.device_file = '/dev/ada0' (string) >> > > >> > > So hald sees the disk, but none of the partitions (slices). Could >> > the "2 >> > > PART ada0s5" be messing things up? The disk has only four slices >> (it's >> > > MBR formatted). I think I will boot Windows and see wat it says >> about >> > > the partitioning. >> > > # 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) >> > > Slice 1 is the weird SYSTEM_DRV, 2 is Windows7_OS, 3 is an exfat >> file >> > > system named "Media", and 4 is the "Lenovo_Recovery" file system. >> But >> > > geom sees a mysterious fifth one that it says is NTFS??? Still, a >> soon >> > > as I mount the seconds slice, hald "sees" all of them. >> > > -- >> > > R. Kevin Oberman, Network Engineer, Retired >> > > E-mail: rkoberman@gmail.com >> > > >> > >> > I don't suppose you have a 9.X output of the conftxt? This is one >> area >> > where HAL could use an update to use confxml or the like. It's >> tied to >> > the output of conftxt and thus the format of it. I have a feeling >> this >> > format is different. I'll have to look over the code... >> > >> > Nope. I'm afraid I blew away my 9 backup yesterday to prep to update to >> > RC4. And, to make matters worse, after re-booting, I can no longer get >> > my network to run so my system is pretty useless until I can figure out >> > what I messed up. (Also had to fix a flat on my bike. Guess it's just >> > not my day.) >> > >> > Using confxml would make a lot of sense, but it does not look like HAL >> > has much of a future. Is it used on MATE? Pretty sure that it is not on >> > Gnome3. >> >> In hf-storage.c in hald/freebsd, go to line 431. Change this "if" block >> to: >> >> if ((! strcmp(fields[1], "LABEL") || >> ! strcmp(fields[1], "BSD") || >> ! strcmp(fields[1], "PART")) && >> (! strncmp(fields[2], "ufsid/", strlen("ufsid/")) || >> ! strncmp(fields[2], "ufs/", strlen("ufs/")) >> ! strncmp(fields[2], "diskid/", strlen("diskid/")))) >> >> Rebuild hal, and see if that helps. >> >> Joe >> > > Joe, > > Shouldn't there be an OR (||) after the next to last line? (I'm going to > assume so and build that way.) > > Thanks! > -- > R. Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com > Well, it's better. lshal does list two volumes on the disk, but not the other two. Fortunately, I don't care about the other two. Unfortunately, even though they are now listed, they don't get mounted. I see that mounting the FAT32 volume requires the "-o large" option, but using mount_ntfs mounts the other just fine. Now that I understand where the data is parsed, I'll play around a bit and see if I can figure out what's wrong. Thanks again! -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com From owner-freebsd-gnome@FreeBSD.ORG Tue Jan 7 08:28:11 2014 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2DD79448 for ; Tue, 7 Jan 2014 08:28:11 +0000 (UTC) Received: from portsmon.freebsd.org (portsmon.freebsd.org [IPv6:2001:1900:2254:206a::50:3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 040891E14 for ; Tue, 7 Jan 2014 08:28:11 +0000 (UTC) Received: from portsmon.freebsd.org ([127.0.1.104]) by portsmon.freebsd.org (8.14.7/8.14.7) with ESMTP id s078SA15048928 for ; Tue, 7 Jan 2014 08:28:10 GMT (envelope-from linimon@FreeBSD.org) Date: Tue, 7 Jan 2014 08:28:10 GMT Message-Id: <201401070828.s078SA15048928@portsmon.freebsd.org> From: linimon@FreeBSD.org To: gnome@freebsd.org Subject: FreeBSD ports that you maintain which are currently marked broken X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: portmgr-feedback@FreeBSD.org List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jan 2014 08:28:11 -0000 Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: x11/gnome-shell broken because: Doesn't build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=gnome-shell If these errors are ones that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Every effort has been made to make sure that these error reports really do correspond to a port that you maintain. However, due to the fact that this is an automated process, it may indeed generate false matches. If one of these errors fits that description, please forward this email to the author of this software, Mark Linimon , so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. From owner-freebsd-gnome@FreeBSD.ORG Tue Jan 7 11:12:25 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 05C0850B for ; Tue, 7 Jan 2014 11:12:25 +0000 (UTC) Received: from portscout.freebsd.org (portscout.freebsd.org [IPv6:2001:1900:2254:206a::50:6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E574E1CE1 for ; Tue, 7 Jan 2014 11:12:24 +0000 (UTC) Received: from portscout.freebsd.org ([127.0.1.123]) by portscout.freebsd.org (8.14.7/8.14.7) with ESMTP id s07BCOxF033011 for ; Tue, 7 Jan 2014 11:12:24 GMT (envelope-from portscout@FreeBSD.org) Received: (from portscout@localhost) by portscout.freebsd.org (8.14.7/8.14.7/Submit) id s07BCOWr033006; Tue, 7 Jan 2014 11:12:24 GMT (envelope-from portscout@FreeBSD.org) Message-Id: <201401071112.s07BCOWr033006@portscout.freebsd.org> X-Authentication-Warning: portscout.freebsd.org: portscout set sender to portscout@FreeBSD.org using -f Content-Disposition: inline Content-Transfer-Encoding: 8bit Content-Type: text/plain MIME-Version: 1.0 Date: Tue, 7 Jan 2014 11:12:24 +0000 From: portscout@FreeBSD.org To: gnome@freebsd.org Subject: FreeBSD ports you maintain which are out of date X-Mailer: portscout/0.8.1 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: Tue, 07 Jan 2014 11:12:25 -0000 Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/gnome@freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ deskutils/mate-utils | 1.6.0 | 1.6.1 ------------------------------------------------+-----------------+------------ editors/mate-text-editor | 1.6.0 | 1.6.2 ------------------------------------------------+-----------------+------------ x11/mate-terminal | 1.6.1 | 1.6.2 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. From owner-freebsd-gnome@FreeBSD.ORG Tue Jan 7 22:20:08 2014 Return-Path: Delivered-To: gnome@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5E3DE701; Tue, 7 Jan 2014 22:20:08 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2CB4C14A2; Tue, 7 Jan 2014 22:20:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s07MK8AQ050582; Tue, 7 Jan 2014 22:20:08 GMT (envelope-from edwin@freefall.freebsd.org) Received: (from edwin@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s07MK8Bw050581; Tue, 7 Jan 2014 22:20:08 GMT (envelope-from edwin) Date: Tue, 7 Jan 2014 22:20:08 GMT Message-Id: <201401072220.s07MK8Bw050581@freefall.freebsd.org> To: edwin@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, gnome@FreeBSD.org From: edwin@FreeBSD.org Subject: Re: ports/185563: [UPDATE] games/gweled to v0.9.1 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: Tue, 07 Jan 2014 22:20:08 -0000 Synopsis: [UPDATE] games/gweled to v0.9.1 Responsible-Changed-From-To: freebsd-ports-bugs->gnome Responsible-Changed-By: edwin Responsible-Changed-When: Tue Jan 7 22:20:07 UTC 2014 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=185563 From owner-freebsd-gnome@FreeBSD.ORG Wed Jan 8 04:09:40 2014 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9507550F for ; Wed, 8 Jan 2014 04:09:40 +0000 (UTC) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 36A5B1739 for ; Wed, 8 Jan 2014 04:09:39 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id s0849WkM079801 for ; Tue, 7 Jan 2014 20:09:33 -0800 (PST) (envelope-from yuri@rawbw.com) Message-ID: <52CCCF7C.1020703@rawbw.com> Date: Tue, 07 Jan 2014 20:09:32 -0800 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: gnome@freebsd.org Subject: Automatic gdm login leaves Xorg in hung state on 11 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Wed, 08 Jan 2014 04:09:40 -0000 gdm+gnome with automatic login enabled leave black screen with "wait" cursor. (Without automatic login they work fine) I tried this only on 11, so not sure if this is 11-specific. Auto-login was enabled in custom.conf: [daemon] AutomaticLoginEnable = true AutomaticLogin = acct_name Yuri From owner-freebsd-gnome@FreeBSD.ORG Wed Jan 8 10:20:10 2014 Return-Path: Delivered-To: gnome@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7F4D2E43; Wed, 8 Jan 2014 10:20:10 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 541651797; Wed, 8 Jan 2014 10:20:10 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s08AKAVa036549; Wed, 8 Jan 2014 10:20:10 GMT (envelope-from edwin@freefall.freebsd.org) Received: (from edwin@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s08AKAeI036548; Wed, 8 Jan 2014 10:20:10 GMT (envelope-from edwin) Date: Wed, 8 Jan 2014 10:20:10 GMT Message-Id: <201401081020.s08AKAeI036548@freefall.freebsd.org> To: edwin@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, gnome@FreeBSD.org From: edwin@FreeBSD.org Subject: Re: ports/185575: [patch] devel/anjuta check autogen fix 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: Wed, 08 Jan 2014 10:20:10 -0000 Synopsis: [patch] devel/anjuta check autogen fix Responsible-Changed-From-To: freebsd-ports-bugs->gnome Responsible-Changed-By: edwin Responsible-Changed-When: Wed Jan 8 10:20:10 UTC 2014 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=185575 From owner-freebsd-gnome@FreeBSD.ORG Wed Jan 8 13:29:54 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 3743593C; Wed, 8 Jan 2014 13:29:54 +0000 (UTC) Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9DA9818D0; Wed, 8 Jan 2014 13:29:53 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id l18so519208wgh.17 for ; Wed, 08 Jan 2014 05:29:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=qLPuKLE4YDxuEBVC8EsiqJEOoLSD4IOJqoV8Ai/wm6E=; b=DussuPzamEf1gR0H/hbynMAlAiyYPpJqgYkzL54chZDBGC+waFhnPbM/Ky0R+nDdm8 fipWEivShMG+5Mkgy2WPMwAivF7u6FzIon1ozZ1Z85RWK0eLhPsEwV3ah/z0x9QMGgpa i67+xZMzzlOOEnIvLPOyNsGIIBlHeE7GMLfZePxO/8keZq8O6Ke/EzblkW2l06KwULdK 5pd/RrggdOdguJN0883GT8punEqAaVbMKo21Z0620jyBlDi6Hgz+hXIR3L2fAG0VoNmg tEYvM15z/8v0Q6EHEiR8OVbOo/tuYO5C5owBlVd3GwATsrgWKk6+JKxktIHLNXUx5xVQ L/hw== X-Received: by 10.180.104.42 with SMTP id gb10mr21382379wib.51.1389187792143; Wed, 08 Jan 2014 05:29:52 -0800 (PST) Received: from [10.0.2.15] (LNantes-156-74-19-50.w82-127.abo.wanadoo.fr. [82.127.90.50]) by mx.google.com with ESMTPSA id e5sm33303994wja.15.2014.01.08.05.29.50 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Jan 2014 05:29:51 -0800 (PST) Message-ID: <52CD52B9.5030001@gmail.com> Date: Wed, 08 Jan 2014 14:29:29 +0100 From: David Demelier User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: gnome@freebsd.org, kwm@freebsd.org Subject: Third attempt: remove useless section in ports/Mk/bsd.mate.mk Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Wed, 08 Jan 2014 13:29:54 -0000 Hello folks, It's the third time that I try to tell you to remove a forgotten section in ports/Mk/bsd.mate.mk. I did it with my personal address markand@malikania.fr but I guess it felt under your spam folder. So I try to recall you for the last time : It's not really important, but there is a section to remove in bsd.mate.mk see : ####################################################### # # *** WARNING: Disable MARCUSCOM before merge in FreeBSD! # Please also remove this section before merging into FreeBSD. # #MARCUSCOM_CVS=yes Regards, From owner-freebsd-gnome@FreeBSD.ORG Wed Jan 8 14:09:48 2014 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A188FF81; Wed, 8 Jan 2014 14:09:48 +0000 (UTC) Received: from mail-vb0-x232.google.com (mail-vb0-x232.google.com [IPv6:2607:f8b0:400c:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4DA601D3F; Wed, 8 Jan 2014 14:09:48 +0000 (UTC) Received: by mail-vb0-f50.google.com with SMTP id w18so1167548vbj.23 for ; Wed, 08 Jan 2014 06:09:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9GaheR3rxc2NTlEKLb7OsbeLtX7jNc+zIoV5gSy/M6o=; b=zxUgHvUC6CP4au4XQ8Xir5d+PxIvdylb9w6EgcEPzKgtRZlaF+RQwfKRitO9Br9Ezh NCsBWd4pq5hwFODAOFH0T/3MbcCWp5pZrFvbGSo37Qc8Ysx80HdKleuxA8kDDttvDGuM M5icmjdVtYuJneYWUpw6Qo+v+CO/eEKmRSdpYc3ibOnbPH287Eq7o79HAGOgRZrhmbcT 9ZqDoKq7qacU14FpTFZBMAJ7VNW6ZU4H426T6B4dF6RHPemY+BkbzG8u+RFV2FEcN5GK yg5QgIc46HorbxzUF929f1spxZKZsdUJCTQhqb/R7rJvzdtgElLJ2wQtIsubMrQF71i5 fKow== MIME-Version: 1.0 X-Received: by 10.52.120.81 with SMTP id la17mr2859056vdb.44.1389190187116; Wed, 08 Jan 2014 06:09:47 -0800 (PST) Received: by 10.58.189.36 with HTTP; Wed, 8 Jan 2014 06:09:47 -0800 (PST) In-Reply-To: <52CD52B9.5030001@gmail.com> References: <52CD52B9.5030001@gmail.com> Date: Wed, 8 Jan 2014 08:09:47 -0600 Message-ID: Subject: Re: Third attempt: remove useless section in ports/Mk/bsd.mate.mk From: Jeremy Messenger To: David Demelier Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD GNOME Users , Koop Mast 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: Wed, 08 Jan 2014 14:09:48 -0000 On Wed, Jan 8, 2014 at 7:29 AM, David Demelier wrote: > Hello folks, > > It's the third time that I try to tell you to remove a forgotten section in > ports/Mk/bsd.mate.mk. I did it with my personal address markand@malikania.fr > but I guess it felt under your spam folder. So I try to recall you for the > last time : It is not important as it doesn't affect anything at all. I don't know why you are complaining about it for third times. Once is good enough. > It's not really important, but there is a section to remove in bsd.mate.mk > see : > > ####################################################### > # > # *** WARNING: Disable MARCUSCOM before merge in FreeBSD! > # Please also remove this section before merging into FreeBSD. > # > #MARCUSCOM_CVS=yes > > Regards, > _______________________________________________ > freebsd-gnome@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-gnome > To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.org" From owner-freebsd-gnome@FreeBSD.ORG Wed Jan 8 15:04:27 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 2EE3B92E; Wed, 8 Jan 2014 15:04:27 +0000 (UTC) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 925AA1256; Wed, 8 Jan 2014 15:04:26 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id n12so1567024wgh.14 for ; Wed, 08 Jan 2014 07:04:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=cuc7pMeLkJJSGA0uEeeX85dmmzBj/tAFR58NHHt3PMk=; b=yD3a6lqwQpOiPFC5/ICuCB/pVVBf3H3o+SwtMwR2ffVWQQkL2LAekDDwvljEv8wZ7c W1FYn6vzHAASMU/w1I+iweN1TzujiQHybH6XEiWnWKpk3GJt0oTTKggoxezuUS06tTUv SM1FzZaTnfVmpGxF9ZHbSEkfK9gQbi56izBZdDhEBEWa7lp7slq277xSbu8kIMAzi+mY c0Z9gEO+PEhD0SV1BtMhZWQDOvutn3fsvJ43Pjxr+3aSx0Jl++fboIY5zRovlsLwQ/P/ flYyXegPYq2/KuWLFaIFZPlxTWZLo5yPNROIFXz6w0jFMiVKsZNxC7tbLbrsumRXTUtr tNuA== X-Received: by 10.180.106.165 with SMTP id gv5mr21802868wib.32.1389193464967; Wed, 08 Jan 2014 07:04:24 -0800 (PST) Received: from [10.0.2.15] (LNantes-156-74-19-50.w82-127.abo.wanadoo.fr. [82.127.90.50]) by mx.google.com with ESMTPSA id fa6sm9336477wid.1.2014.01.08.07.04.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Jan 2014 07:04:24 -0800 (PST) Message-ID: <52CD68F7.3050003@gmail.com> Date: Wed, 08 Jan 2014 16:04:23 +0100 From: David Demelier User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Jeremy Messenger Subject: Re: Third attempt: remove useless section in ports/Mk/bsd.mate.mk References: <52CD52B9.5030001@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD GNOME Users , Koop Mast 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: Wed, 08 Jan 2014 15:04:27 -0000 On 08/01/2014 15:09, Jeremy Messenger wrote: > On Wed, Jan 8, 2014 at 7:29 AM, David Demelier wrote: >> Hello folks, >> >> It's the third time that I try to tell you to remove a forgotten section in >> ports/Mk/bsd.mate.mk. I did it with my personal address markand@malikania.fr >> but I guess it felt under your spam folder. So I try to recall you for the >> last time : > It is not important as it doesn't affect anything at all. I don't know > why you are complaining about it for third times. Once is good enough. > But because it's written in the section ;-). And as said earlier I thought my mails were put in spam as it usually. It is just for being as clean as possible, not a real complain :-). Cheers, >> It's not really important, but there is a section to remove in bsd.mate.mk >> see : >> >> ####################################################### >> # >> # *** WARNING: Disable MARCUSCOM before merge in FreeBSD! >> # Please also remove this section before merging into FreeBSD. >> # >> #MARCUSCOM_CVS=yes >> >> Regards, >> _______________________________________________ >> freebsd-gnome@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-gnome >> To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.org" From owner-freebsd-gnome@FreeBSD.ORG Thu Jan 9 19:00:08 2014 Return-Path: Delivered-To: gnome@smarthost.ysv.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 D01A1105; Thu, 9 Jan 2014 19:00:08 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A5304135A; Thu, 9 Jan 2014 19:00:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s09J08WL002824; Thu, 9 Jan 2014 19:00:08 GMT (envelope-from edwin@freefall.freebsd.org) Received: (from edwin@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s09J08GH002823; Thu, 9 Jan 2014 19:00:08 GMT (envelope-from edwin) Date: Thu, 9 Jan 2014 19:00:08 GMT Message-Id: <201401091900.s09J08GH002823@freefall.freebsd.org> To: edwin@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, gnome@FreeBSD.org From: edwin@FreeBSD.org Subject: Re: ports/185613: [UPDATE] accessibility/gnome-speech, add license information 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: Thu, 09 Jan 2014 19:00:08 -0000 Synopsis: [UPDATE] accessibility/gnome-speech, add license information Responsible-Changed-From-To: freebsd-ports-bugs->gnome Responsible-Changed-By: edwin Responsible-Changed-When: Thu Jan 9 19:00:08 UTC 2014 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=185613 From owner-freebsd-gnome@FreeBSD.ORG Fri Jan 10 10:22:07 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 75A3E734 for ; Fri, 10 Jan 2014 10:22:07 +0000 (UTC) Received: from mail-pb0-x24e.google.com (mail-pb0-x24e.google.com [IPv6:2607:f8b0:400e:c01::24e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 505F91D6D for ; Fri, 10 Jan 2014 10:22:07 +0000 (UTC) Received: by mail-pb0-f78.google.com with SMTP id uo5so43989pbc.1 for ; Fri, 10 Jan 2014 02:22:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:message-id:date:subject:from:to:content-type; bh=VhQVuzENnX9z6q8EMtbA34RWIboXszImyuKQThyVqUE=; b=BY20STqJqTYQtBlDW4UzBbl9uDEVaFQvTCcxxfhUbmRx5zQHg+yS4DnI6g7z5PQmSt smhsqW+iV/gLIKjc6lSJ3VpkYK5O2EFit0A0kHeIlzMLA/AtyxXXWfn0dZa0692Hm+G4 EQ8t6oLM4LXSyxW0JJ1iQl4iVrjC+h61mM2mn/rfZVvH/sLR4egHmZCJJvu0Ot6Tzdqk 5mj8/DRQQJHgyAAg/SiMY4pXkGJHdr1fQtGA0CcEqE7982cBQYcJa8SMr6nAN+I6GPf7 cSIhdXevJB5f61gX3yxDktQDhl4L7Kf4WfKXEGFu09n/3sOXsc02yWJOhfnKPkub2wD1 u4GQ== MIME-Version: 1.0 X-Received: by 10.66.163.67 with SMTP id yg3mr464471pab.45.1389349326950; Fri, 10 Jan 2014 02:22:06 -0800 (PST) Message-ID: <047d7bacbe0e1a146904ef9b196d@google.com> Date: Fri, 10 Jan 2014 10:22:06 +0000 Subject: www.freebsd.org From: Lilly Officer To: gnome@freebsd.org Content-Type: text/plain; charset=windows-1252; format=flowed; delsp=yes Content-Transfer-Encoding: base64 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: Fri, 10 Jan 2014 10:22:07 -0000 SGksDQoNCkkgd2FudGVkIHRvIHNlbmQgeW91IGEgcXVpY2sgbm90ZS4gV2l0aCBhIGZldyBzaW1w bGUgY2hhbmdlcyB0byBtYWtlIHlvdXINCnNpdGUgbW9yZSBTRU8tZnJpZW5kbHkgSZJtIHN1cmUg eW91IGNhbiBjb252ZXJ0IG1vcmUgdmlzaXRvcnMgaW50byBsZWFkcw0KYW5kIGdldCBpdCBwbGFj ZWQgaGlnaGVyIGluIHRoZSBvcmdhbmljIHNlYXJjaCByZXN1bHRzLCBmb3Iga2V5d29yZHMgdGhh dA0KbWF0dGVyIHRvIHlvdSB0aGUgbW9zdC4NCg0KV2UgYXJlIGFuIEF1c3RyYWxpYW4gYmFzZWQg Y29tcGFueSB3aXRoIGEgZ3JlYXQgaW4taG91c2UgdGVjaG5pY2FsIHRlYW0gd2hvDQpyZWFsbHkg a25vdyB0aGVpciBzdHVmZiBhYm91dCBzZWFyY2ggZW5naW5lIG9wdGltaXphdGlvbi4NCg0KV291 bGQgeW91IGxpa2UgYSBiaXQgbW9yZSBpbmZvcm1hdGlvbiBhYm91dCBob3cgdG8gZ2l2ZSB5b3Vy IHdlYnNpdGUgYQ0KYm9vc3Qgd2l0aCBiZXR0ZXIgU0VPPw0KDQpCZXN0IHJlZ2FyZHMsDQoNCkxp bGx5IE9mZmljZXINClNFTy9XRUIgU3BlY2lhbGlzdA0KRTogbGlsbHlvZmZpY2VyMUBnbWFpbC5j b20NCg0KW2ltYWdlOiBMaW5rZWRJbl0gW2ltYWdlOiBGYWNlYm9va10gW2ltYWdlOiBUd2l0dGVy XSBbaW1hZ2U6IFNreXBlXQ0KICAgICAgICAgICAgIFMgICAgRSAgIE8gICAgICAgICAgICAgKlNl YXJjaCBFbmdpbmUgT3B0aW1pemF0aW9uKg0KKkAgKlFVRUVOU0xBTkQsIE5TVywgVklDVE9SSUEs IFNPVVRIIEFVU1RSQUxJQSwgV0VTVEVSTiBBVVNUUkFMSUEsIE5PUlRIRVJODQpURVJSSVRPUlks IFRBU01BTklBLCBBQ1QNCg0KV2UgcmVzcGVjdCB5b3VyIHByaXZhY3kgYW5kIHdhbnQgdG8gbWFr ZSBzdXJlIHlvdSBhcmUgYXdhcmUgb2YgYSBmZXcNCnRoaW5ncy4gQnkgcmVwbHlpbmcgdG8gdGhp cyBlbWFpbCwgeW91IGF1dGhvcml6ZSBvdXIgQXVzdHJhbGlhbiBhZmZpbGlhdGVzDQp0aGF0IGNh biBoZWxwIHdpdGggeW91ciBwcm9qZWN0IHRvIGNhbGwgeW91IGF0IHRoZSBudW1iZXIgeW91IHBy b3ZpZGVkLCBhbmQNCnlvdSB1bmRlcnN0YW5kIHRoYXQgdGhleSBtYXkgdXNlIGF1dG9tYXRlZCBw aG9uZSB0ZWNobm9sb2d5IHRvIGNhbGwgeW91LiBBdA0Kbm8gdGltZSBhcmUgeW91IHJlcXVpcmVk IHRvIG1ha2UgYSBwdXJjaGFzZS4NClVuc3Vic2NyaWJlDQo= From owner-freebsd-gnome@FreeBSD.ORG Sat Jan 11 14:06:18 2014 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 31927AB8 for ; Sat, 11 Jan 2014 14:06:18 +0000 (UTC) Received: from sender1.zohomail.com (sender1.zohomail.com [72.5.230.95]) by mx1.freebsd.org (Postfix) with ESMTP id 13E681533 for ; Sat, 11 Jan 2014 14:06:17 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version; b=ud1ZtiiCKwxjvaZYndznzhlvh/U8x7EgOgoL9eTIztF1osGgUnz3j9Dj9fcBZZsZs2zJ5crmNuCq f9WO/XfDS5Apb+dfDRM3SOvVUMoAXv4V64+iUq8qCx5tdSOFnrOv Received: from [192.168.11.5] (213.111.120.236 [213.111.120.236]) by mx.zohomail.com with SMTPS id 1389449170466699.4089641108303; Sat, 11 Jan 2014 06:06:10 -0800 (PST) Subject: Re: Mate port From: clutton To: freebsd-gnome@freebsd.org In-Reply-To: <1385962190.48649.11.camel@eva02.mbsd> References: <5295C276.8050209@yandex.ru> <1385962190.48649.11.camel@eva02.mbsd> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-b6YTjH+foBk1K8tgwhx0" Date: Sat, 11 Jan 2014 16:05:59 +0200 Message-ID: <1389449159.6065.45.camel@eva02.mbsd> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Zoho-Virus-Status: 1 X-ZohoMail: Ss SS_10 UW UB UW UB SGR3_1_26113_291 X-ZohoMail-Owner: <1389449159.6065.45.camel@eva02.mbsd>+zmo_0_ X-ZohoMail-Sender: 213.111.120.236 X-ZohoMailClient: External 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: Sat, 11 Jan 2014 14:06:18 -0000 --=-b6YTjH+foBk1K8tgwhx0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, 2013-12-02 at 07:29 +0200, clutton wrote: [---] Ok, finally I've found a time to fix my mate desktop. make-keyring doesn't work, fixing /usr/local/etc/pam.d/gdm, and removing suid bit from mate-keyring-daemon binary will make it work. But there's a better solution: 1) http://wiki.mate-desktop.org/mate-keyring 2) Make sure that you've unchecked all mate-keyring daemons from System->Preferences->Startup Application, and gnome-keyring daemons must be checked. It will use gnome-keyring for mate session. 1) Then, there is http://wiki.mate-desktop.org/replace_unity_by_mate some xdg settings, in case you need it. I believe that mate 1.8 has some kind of keyring hack included. --=-b6YTjH+foBk1K8tgwhx0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAABAgAGBQJS0U/HAAoJECNkWbjnbjuiS+oP/Roi2qg1U4KGAnuBof2UHCrA zW1db8lMWecMiz7+Nu3OIkhO0zuDPYLsRrMu3rxsDUpWllnMFJZ8cGCqd6kgjFvJ OW+taVBkJW6vIShpDFC2790CB/FGqStyJn7EXsWII6Z7wVC+vKWsJ4yErzMkQBUp aQi1YfFvs5QQ+NhjOZGT8PFuBZxQS001tLPvViHcqqiHCQu35oDaqqhaZOvLNsVI TWdFMMl6uW1I646GdovCL9nkDeiyYpijjyIC+A7FL68T1ZInEzgILoMLRvcLkYnw rnj4rCrlIYbE02Xi+64uD+RPAkRkMdBa8iQAwEmJA3itGpZiXs6nwU403dxX+7SB E+Uuju8zIHHsheweX6B4nPfbPvmsgKdzp/GkBbIldCR0qTjvrHn+vLODpdUEmAZD ucJ7QyDDOQCv8k5giQ2+G+gqXQGgKcjV2LJr7BoroPClGIuxsR4A1xQzK3ki0xFm eSqbfMVWwfdmuNTJCEu6fCsWGnsPAeP/lN2G+6UmGojgYE5ElHZq8WSzK1MvgVMa RT7rdXKSCKQVIlnTickfSbj7lFrHr8QQUtvQavHWVS6fexrio7/y4H5dYkn8rT8W H7DJNF40t1ehnHzG6zJYvIs0mk1Lpjrlw6B9x/dqGoBU1eaxQ40qhFA/5lZC0fqh 1BQYIJ5yeDW0Yv9EKlYp =XeAk -----END PGP SIGNATURE----- --=-b6YTjH+foBk1K8tgwhx0--