From unknown Fri Mar 29 12:02:10 2024 Received: (at 222) by bugs.devuan.org; 27 Jan 2020 12:41:49 +0000 Return-Path: Delivered-To: devuanbugs@dyne.org Received: from tupac3.dyne.org [195.169.149.119] by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4) for (single-drop); Mon, 27 Jan 2020 12:41:49 +0000 (UTC) Received: from mail-lf1-f50.google.com (mail-lf1-f50.google.com [209.85.167.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by vm6.ganeti.dyne.org (Postfix) with ESMTPS id 455AFF60A17 for <222@bugs.devuan.org>; Mon, 27 Jan 2020 13:38:03 +0100 (CET) Authentication-Results: vm6.ganeti.dyne.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="QnngmJgH"; dkim-atps=neutral Received: by mail-lf1-f50.google.com with SMTP id z18so6080005lfe.2 for <222@bugs.devuan.org>; Mon, 27 Jan 2020 04:38:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:reply-to:to:date:in-reply-to:references :organization:user-agent:mime-version:content-transfer-encoding; bh=aoaLpjDW7RiUAVqgjW0Sf3jJCsw9zj0xI7IcSOypLGU=; b=QnngmJgHgy63dUWFjIOn3UjwmZbasnWz1j0xZ1TKYFuYtnlbQxoKblekn53zjMPmcW K8VJbbFUSDWWfJcDd7pGDw2heU0IbM7rc7Ugtk/UBdFDrQcRPa6Pck4+8Vqj8FaaIMJO NKcNLZ7K7dINMvBwiojxKLK/PzGUZ8JiMO2F3q2ileOM3+McDHvVQ96n3Qbc1DI25BiN ociRU+uIoGjqCuzMHtv0A9XfFoL9B+GggXULuhqVVVioci1MdCl6ZTOKxTd9eOdw5sUU Y4A1c9JxG5wF9bF9T5aVxFMVIh6TkPMGUvVIiF75ACvux62ICN7CdJa9hxFvdeJ9gDVE OrEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:reply-to:to:date :in-reply-to:references:organization:user-agent:mime-version :content-transfer-encoding; bh=aoaLpjDW7RiUAVqgjW0Sf3jJCsw9zj0xI7IcSOypLGU=; b=Hm5kPi9Ijxe1LBqQuoIIzjLgAySFPunaRc5e0Ob6OvuOjIV0vdJjQ//mxu0tazbi2z RTGVuo/LGZYtLxtTghG5bDTT3SL5Dtu2bjRnYS8219zAYhihSoHcssn88I5uQsBBieIw J2zebN8+UVUY7r7clArZTnuzbQ2Y1Wa1tHCajpQiSq2CPB1VE9sSLICTt5aLcp9c6aKn tjN8SEro144364NcZpX3Fww0SCLUtVCHAuIpq1DiW9QMb71AE5dVQ5IDis7N6B/aTDJ6 /Z+iub5kERj9sZLrOYWBieWvwRzeNZaxELheTOKK6/N5ZV2zSCPDp2odyy4FPAtT6qX3 uzrg== X-Gm-Message-State: APjAAAUu0gKxgcDDoXizNeJXYT5V1GR9mgSCioW5ccalfi9ydAE1p2ov sqpPgZDE5ysZn4ZpwlnJwbyB7ZtX X-Google-Smtp-Source: APXvYqwBhZ/UJQYU6D6lbR8Ne6L67h/Ir0PLP6XyE/JRdZCvRexDgHE+FsAFZq62RBYSfwnRTIjb6A== X-Received: by 2002:ac2:4199:: with SMTP id z25mr2639116lfh.26.1580128682369; Mon, 27 Jan 2020 04:38:02 -0800 (PST) Received: from G3620.lan (178-78-231-178.customers.ownit.se. [178.78.231.178]) by smtp.gmail.com with ESMTPSA id t27sm8189206ljd.26.2020.01.27.04.38.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 Jan 2020 04:38:01 -0800 (PST) Message-ID: Subject: Re: [Devuan-bugs] bug#222: hdparm rules use DEVNAME only From: Svante Signell Reply-To: svante.signell@gmail.com To: 222@bugs.devuan.org Date: Mon, 27 Jan 2020 13:39:14 +0100 In-Reply-To: References: Organization: Home Content-Type: text/plain; charset="ISO-8859-1" User-Agent: Evolution 3.30.5-1.1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_PASS,WEIRD_QUOTING autolearn=disabled version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org Package: eudev Version: 3.2.2.13 tags 222 moreinfo Dear Ralph and kalle-del-haye, Can you confirm if this bug is still relevant for eudev? Latest version available is: 3.2.9-4. According to https://dev1galaxy.org/viewtopic.php?pid=10379#p10379 it seems like this bug can be closed. Thanks! On Mon, 2018-06-25 at 21:56 +1000, Where all about bugs in Devuan packages is reported wrote: > Package: eudev > Version: 3.2.2-13 > > Lodged on behalf of @kalle-delhaye: > https://dev1galaxy.org/viewtopic.php?pid=10379#p10379 > > """" > One week later - I've found the (or my?) fault. > > When I upgraded my server from Debian Jessie to Devuan Ascii i reused > the working settings in hdparm.conf. > But in Ascii, hdparm.conf is read by a script started by a eudev rule > and is working with /dev/sd? definitions only. > No /dev/disk/by-label, no /dev/disk/by-uuid or any other links in /dev/disk. > > That's because the little eudev script reading hdparm.conf is using only > the $DEVNAME environment variable from eudev to parse the settings. And > $DEVNAME is /dev/sda, for example. > > The sd? links in /dev can change for a specific disk, so I think its not > a good idea to remove the by-label or by-uuid posibilities from hdparm.conf. > As a workaround you can make your own eudev rule for partitions using > the variable $ID_FS_LABEL or $ID_FS_UUID for example. > I will try this when I find some time. > """"