From owner-freebsd-hackers Tue Apr 2 13:23:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA27547 for hackers-outgoing; Tue, 2 Apr 1996 13:23:49 -0800 (PST) Received: from horst.bfd.com ([204.160.242.10]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA27540 Tue, 2 Apr 1996 13:23:45 -0800 (PST) Received: from harlie.bfd.com (bastion.bfd.com [204.160.242.2]) by horst.bfd.com (8.7.3/8.7.3) with SMTP id NAA19539; Tue, 2 Apr 1996 13:23:55 -0800 (PST) Date: Tue, 2 Apr 1996 13:23:40 -0800 (PST) From: "Eric J. Schwertfeger" To: Terry Lambert cc: Brett Glass , terry@lambert.org, freebsd-hardware@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Hacked kernel with option to disable "green" mode In-Reply-To: <199604021823.LAA16657@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Apr 1996, Terry Lambert wrote: > Well, then there he goes -- send the 0xFB out that way -- does the 0xFB > have to go out at the start, or could we, for instance, send it after > initialization? > > It seems to me the best place for disabling "green" mode would be in > a user hack to the /etc/rc.local. Exactly. hdparm (8) does this for Linux, and that is how it is usually set up. Call the command in rc.local, no kernel hacking other than the interface to allow root processes to send commands to the drive (not sure hdparm is a generic ioctl interface or not).