From owner-freebsd-gnome@FreeBSD.ORG Sun Jul 24 01:09:20 2011 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7304C106566B; Sun, 24 Jul 2011 01:09:20 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2068A8FC08; Sun, 24 Jul 2011 01:09:19 +0000 (UTC) Received: by gyf3 with SMTP id 3so2164096gyf.13 for ; Sat, 23 Jul 2011 18:09:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=x2bVq2WbX4dy7kzu0HZK8+5EzCJEZpWxHuOBoc+sgQQ=; b=dvX50QeQbzHvz3gC+Pl+cJ6p0uJbOFtMsFXTyMEAOzCr4JUf6pc7gdJdt2KhyqGKMz /wrpsq2C8F3J7qDOLB30t8NKh4PIQxuJ7T74H0zrkSYAJUxWBse3kCR8NpAE5QIjD80C fx1y5oTyLimlkOjh+IohdyqHwffK41g5TAJt4= MIME-Version: 1.0 Received: by 10.150.61.18 with SMTP id j18mr3230174yba.255.1311469759351; Sat, 23 Jul 2011 18:09:19 -0700 (PDT) Received: by 10.151.27.21 with HTTP; Sat, 23 Jul 2011 18:09:19 -0700 (PDT) In-Reply-To: References: <4E25E739.2020301@freebsd.org> <4E277870.8010506@freebsd.org> Date: Sat, 23 Jul 2011 18:09:19 -0700 Message-ID: From: Kevin Oberman To: Joe Marcus Clarke Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-gnome@freebsd.org Subject: Re: HAL issues X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Jul 2011 01:09:20 -0000 On Wed, Jul 20, 2011 at 10:18 PM, Kevin Oberman wrote: > On Wed, Jul 20, 2011 at 5:53 PM, Joe Marcus Clarke wrote: >> Give this patch a shot. >> >> http://www.marcuscom.com/downloads/patch-hald_freebsd_hf-storage.c > > Thanks, Joe. That did it. All three file systems now mount as they should. > Please feel free to commit. I'm sure that others have hit this, too, although > it is a rather odd case. Now that I have had time to digest the patch, I see why this does not show up much. 1. Most removable drives are FAT or NTFS and not GELI encrypted, so even the most basic case does not happen often. 2. If the only file system on the disk is GELI encrypted, it worked fine as hald took a different path when no other file systems were on the drive. So my problem was a GELI encrypted slice with another (actually two other) slices that were not encrypted. They were FAT and mounted on connection. I suspect I might have seen the same issue if I had two encrypted slices. The first to be geli attached probably would have mounted, but the second probably would have been ignored. Thanks again, Joe. Guess I'll report my other mounting issue, now. (No good deed goes unpunished.) -- R. Kevin Oberman, Network Engineer - Retired E-mail: kob6558@gmail.com