From owner-cvs-sbin Sun Mar 10 16:22:52 1996 Return-Path: owner-cvs-sbin Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA02697 for cvs-sbin-outgoing; Sun, 10 Mar 1996 16:22:52 -0800 (PST) Received: (from mpp@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA02676 Sun, 10 Mar 1996 16:22:31 -0800 (PST) Date: Sun, 10 Mar 1996 16:22:31 -0800 (PST) From: Mike Pritchard Message-Id: <199603110022.QAA02676@freefall.freebsd.org> To: CVS-committers, cvs-all, cvs-sbin Subject: cvs commit: src/sbin/mount mount.c Sender: owner-cvs-sbin@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk mpp 96/03/10 16:22:30 Modified: sbin/mount mount.c Log: Only restrict the user from doing something like "mount /mnt /mnt" for file system types that actually cause a panic (ufs, msdos, cd9660). This makes /proc mountable again. Revision Changes Path 1.11 +7 -4 src/sbin/mount/mount.c From owner-cvs-sbin Sun Mar 10 23:48:15 1996 Return-Path: owner-cvs-sbin Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA13725 for cvs-sbin-outgoing; Sun, 10 Mar 1996 23:48:15 -0800 (PST) Received: from veda.is (root@veda.is [193.4.230.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA13715 Sun, 10 Mar 1996 23:48:05 -0800 (PST) Received: (from adam@localhost) by veda.is (8.7.4/8.7.3) id HAA03163; Mon, 11 Mar 1996 07:47:55 GMT From: Adam David Message-Id: <199603110747.HAA03163@veda.is> Subject: Re: cvs commit: src/sbin/mount mount.c To: mpp@freefall.freebsd.org (Mike Pritchard) Date: Mon, 11 Mar 1996 07:47:52 +0000 (GMT) Cc: CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-sbin@freefall.freebsd.org In-Reply-To: <199603110022.QAA02676@freefall.freebsd.org> from Mike Pritchard at "Mar 10, 96 04:22:31 pm" X-Mailer: ELM [version 2.4ME+ PL10 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-cvs-sbin@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > mpp 96/03/10 16:22:30 > > Modified: sbin/mount mount.c > Log: > Only restrict the user from doing something like "mount /mnt /mnt" > for file system types that actually cause a panic (ufs, msdos, cd9660). > This makes /proc mountable again. > > Revision Changes Path > 1.11 +7 -4 src/sbin/mount/mount.c > # mount foo:/usr /usr mount: foo:: No such file or directory This problem exists with both revisions 1.11 and 1.10 Adam From owner-cvs-sbin Mon Mar 11 12:01:25 1996 Return-Path: owner-cvs-sbin Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA10060 for cvs-sbin-outgoing; Mon, 11 Mar 1996 12:01:25 -0800 (PST) Received: (from mpp@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA10016 Mon, 11 Mar 1996 12:01:19 -0800 (PST) Date: Mon, 11 Mar 1996 12:01:19 -0800 (PST) From: Mike Pritchard Message-Id: <199603112001.MAA10016@freefall.freebsd.org> To: CVS-committers, cvs-all, cvs-sbin Subject: cvs commit: src/sbin/mount mount.c Sender: owner-cvs-sbin@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk mpp 96/03/11 12:01:18 Modified: sbin/mount mount.c Log: Backout my changes to disallow "mount /mnt /mnt" until I can verify that nfs mounts work again (I locked up my home machine testing it and can't see what happened until I get home from work tonight). Revision Changes Path 1.12 +0 -22 src/sbin/mount/mount.c From owner-cvs-sbin Tue Mar 12 04:56:35 1996 Return-Path: owner-cvs-sbin Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA10854 for cvs-sbin-outgoing; Tue, 12 Mar 1996 04:56:35 -0800 (PST) Received: (from ache@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA10838 Tue, 12 Mar 1996 04:56:28 -0800 (PST) Date: Tue, 12 Mar 1996 04:56:28 -0800 (PST) From: "Andrey A. Chernov" Message-Id: <199603121256.EAA10838@freefall.freebsd.org> To: CVS-committers, cvs-all, cvs-sbin Subject: cvs commit: src/sbin/slattach slattach.c Sender: owner-cvs-sbin@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ache 96/03/12 04:56:28 Modified: sbin/slattach slattach.c Log: Re-open line after hangup in any case Revision Changes Path 1.19 +2 -15 src/sbin/slattach/slattach.c From owner-cvs-sbin Tue Mar 12 15:14:53 1996 Return-Path: owner-cvs-sbin Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA29261 for cvs-sbin-outgoing; Tue, 12 Mar 1996 15:14:53 -0800 (PST) Received: (from ache@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA29240 Tue, 12 Mar 1996 15:14:47 -0800 (PST) Date: Tue, 12 Mar 1996 15:14:47 -0800 (PST) From: "Andrey A. Chernov" Message-Id: <199603122314.PAA29240@freefall.freebsd.org> To: CVS-committers, cvs-all, cvs-sbin Subject: cvs commit: src/sbin/slattach slattach.8 slattach.c Sender: owner-cvs-sbin@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ache 96/03/12 15:14:47 Modified: sbin/slattach slattach.8 slattach.c Log: Properly distinguish 3 different cases: No redial command. Empty redial command. Non-empty redial command. Pointed-by: bde Revision Changes Path 1.11 +8 -2 src/sbin/slattach/slattach.8 1.20 +15 -8 src/sbin/slattach/slattach.c From owner-cvs-sbin Thu Mar 14 16:14:35 1996 Return-Path: owner-cvs-sbin Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA12930 for cvs-sbin-outgoing; Thu, 14 Mar 1996 16:14:35 -0800 (PST) Received: (from asami@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA12870 Thu, 14 Mar 1996 16:14:12 -0800 (PST) Date: Thu, 14 Mar 1996 16:14:12 -0800 (PST) From: Satoshi Asami Message-Id: <199603150014.QAA12870@freefall.freebsd.org> To: CVS-committers, cvs-all, cvs-sbin Subject: cvs commit: src/sbin/mount mount.c Sender: owner-cvs-sbin@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk asami 96/03/14 16:14:11 Modified: sbin/mount mount.c Log: Change the messages slightly when there is no "mount_type" executable found when the user specifies "mount -t type". Instead of printing out one message for each path element (/sbin, /usr/sbin), it prints out: mount: exec mount_type not found in /sbin, /usr/sbin: No such file or directory The code is quite long for such a stupid little piece of aesthesism but it is very straghtforward so I guess it's ok. Besides, I don't want to do a "char foo[100];" and have malloc break down when someone decides to add a few more paths to a variable that's far apart from this code. :) By the way, there is no malloc() off-by-one error for the '\0' at the end of the string although I don't explicitly add 1 to the length. The code allocates strlen(path element)+2 bytes for each path element, and doesn't use the last two bytes (for the delimiting ", "). Reviewed by: the list (I hope) Revision Changes Path 1.13 +19 -4 src/sbin/mount/mount.c