Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) by gbr-app-1.alpinelinux.org (Postfix) with ESMTPS id 678BF223843 for <~alpine/users@lists.alpinelinux.org>; Sat, 4 Apr 2026 16:24:21 +0000 (UTC) Received: from fews04-sea.riseup.net (fews04-sea-pn.riseup.net [10.0.1.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4fp1BW2Czmz9vV8 for <~alpine/users@lists.alpinelinux.org>; Sat, 4 Apr 2026 16:24:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=riseup.net; s=squak; t=1775319859; bh=uu3saHw6JRLTZpSdomroBCo7nsCGvrhJ12k3WREZnHU=; h=Subject:From:To:Date:In-Reply-To:References:From; b=lXga4z0pFVBrBDyiBEGsiRf/pHptfDHvJ+j6v0wxUQ8ohOSjRIMch8wbR71V3Toj0 W16VSTE+nKsUbSJP5S8/dV9u3OgZiMHrNA+oWIKxPMP0Cj2A+D7nPdN7mvLyU3BGQ2 +RJIeBSG5a0NCMsvKA8S1wNNN8v2uhX+cBYU350A= X-Riseup-User-ID: AE5A0ED2D9E77EF9B0B04F7D35AA94CC101131AE9B18FC05E02B80D355D53034 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews04-sea.riseup.net (Postfix) with ESMTPSA id 4fp1BV4cK8z60dB for <~alpine/users@lists.alpinelinux.org>; Sat, 4 Apr 2026 16:24:18 +0000 (UTC) Message-ID: <403dd9491003856588f75504445987a791c4a07e.camel@riseup.net> Subject: Re: Why'd you go with Alpine Linux? From: Ralf Mardorf To: ~alpine/users@lists.alpinelinux.org Date: Sat, 04 Apr 2026 18:24:14 +0200 In-Reply-To: <71cf328f-c6da-4537-a772-d4518e6d2a0a@web.de> References: <2838510e48dd7564e67dcb67562b968ccc4a9724.camel@riseup.net> <9a06befe-edba-45af-8226-487b26b8564f@web.de> <0a012799b4793f0e8f5f54a843bf8e6094807238.camel@riseup.net> <71cf328f-c6da-4537-a772-d4518e6d2a0a@web.de> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 OT: On Sat, 2026-04-04 at 14:55 +0200, Wolfgang Klein wrote: > And by the way: a disks spin down time can be set using "hdparm -S" Yes, it is possible to control hard drives. The problem lies in the firmware of the new controllers (USB-to-SATA) in the latest enclosures. It used to be difficult to find enclosures that didn=E2=80=99t have this problem, but some manufacturers did offer such enclosures. BTW none of the HDDs or SSDs I=E2=80=99ve ever bought go into sleep mode. Standby mode = was always disabled by default. I have 10 FANTEC DB-ALU3e enclosures with good firmware, but they are no longer manufactured, and all recommendations for enclosures from other companies that I received in mailing lists ot that are mentioned by internet forums are obsolete. I have contacted the support of each of these companies. At least one support representative tried to pull the wool over my eyes. They claimed that Windows could disable the controller=E2=80=99s standby mo= de. That=E2=80=99s nonsense, of course. There are, of course, various workaroun= ds. I=E2=80=99ll have no choice but to use also workarounds in the future, but = I actually dislike them, because a workaround for something that could have been done right in the first place is always bullshit. One of the many workarounds that other users use, funny enough, bash mentioned in a FreeBSD mailing list: -------- Forwarded Message -------- Cc: FreeBSD Questions Subject: Re: PS: Not that SATA to USB controller question again Date: 02/06/2026 03:10:48 PM [snip] in /etc/rc.local: /root/bin/dyski.sh & /root/bin/dyski.sh: #!/usr/local/bin/bash while true;do for x in fi1 data fi2 fi3;do dd if=3D/dev/label/$x of=3D/dev/null bs=3D4k count=3D1 >/dev/null 2>/dev= /null done sleep 120 done problem solved