Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Jan 2017 17:32:49 -0700 (MST)
From:      Warren Block <wblock@wonkity.com>
To:        Ian Lepore <ian@freebsd.org>
Cc:        "Andrey V. Elsukov" <bu7cher@yandex.ru>, freebsd-hackers@freebsd.org, Slawa Olhovchenkov <slw@zxy.spb.ru>
Subject:   Re: How to safely remove rest of GTP?
Message-ID:  <alpine.BSF.2.20.1701301625040.85129@wonkity.com>
In-Reply-To: <1485812227.3017.19.camel@freebsd.org>
References:  <20161230124407.GN37118@zxy.spb.ru> <d79b8568-72e8-415e-4923-14e3c730267e@FreeBSD.org> <alpine.BSF.2.20.1701300851400.85129@wonkity.com> <1793b0ec-3a86-5c9a-b275-aa93cd9d230e@yandex.ru> <1485796999.3017.7.camel@freebsd.org>  <91788d86-c85b-a893-0185-5d6efd8bca7e@yandex.ru> <1485812227.3017.19.camel@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 30 Jan 2017, Ian Lepore wrote:

> On Tue, 2017-01-31 at 00:33 +0300, Andrey V. Elsukov wrote:
>> On 30.01.2017 20:23, Ian Lepore wrote:
>>>
>>>>
>>>> other type of partition table in the same time. So, if you use
>>>> 'gpart
>>>> destroy' - you want to explicitly destroy it.
>>>>
>>> The question to ask here is why are you the only one who can't see
>>> or
>>> understand that a user is NOT going to use a "destroy" command on a
>>>  disk containing live data?  Especially given the confusing
>>> vagueness
>>> of the gpart docs.
>> Because I have read the docs and understood them? Did you tried do
>> that 
>> instead of attacking me each time, when geom/gpart is discussed? I'm 
>> even not an author  of this. If you don't like the existing 
>> documentation, the sources are open, read them and write better 
>> documentation.
>>
>
> Every time someone says they can't understand how to do something with
> gpart, you imply that the problem is all theirs, because the
> documentation is clear.  The documentation is NOT clear, and every time
> you say so, I'm going to point out it is not.

I am interested in improving gpart documentation, if you have specific 
suggestions.

Beyond that, these responses seem unnecessarily harsh and personal.
From owner-freebsd-hackers@freebsd.org  Tue Jan 31 01:53:54 2017
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E276CCC7FEF
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Tue, 31 Jan 2017 01:53:54 +0000 (UTC)
 (envelope-from yaneurabeya@gmail.com)
Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com
 [IPv6:2607:f8b0:400e:c00::241])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id BC50AFD2;
 Tue, 31 Jan 2017 01:53:54 +0000 (UTC)
 (envelope-from yaneurabeya@gmail.com)
Received: by mail-pf0-x241.google.com with SMTP id 19so25005625pfo.3;
 Mon, 30 Jan 2017 17:53:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:subject:from:in-reply-to:date:cc
 :content-transfer-encoding:message-id:references:to;
 bh=kbGn7Gzb2/bEzGdWwz484+5feTa9qwyvlsHLGP3+WV4=;
 b=th4pu1ue3ozb8PGtWfj8ettEF/PMNZX9xg1YKbQGQkz/fcYaiZEmlRtMus/88WYBrf
 dGkKyI4ZJyU4sTNLgzWBo8qWQx9L3wHlaR4y85gGR19Bulyd7cCPBhejJZItomYzH5Tj
 sBgBcpFXBm3udEj7OFlbxrLaWg9adsmz12nKUKXS0Va26AoxYz7HT1wJNMJQgJfXMJLu
 k4kaGQs5cUXlRkJ8i8R3aKfgg2KaiO+mwbOcaz5lnBX1axgWGqomiYbVATRN8OOexGrd
 M6nS0vOJk96cWDW2YO7CQrgm25bs7UtTmdvgXa1BoHCVkE7ea4EcNoDSupw8DEVETJO+
 7v3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc
 :content-transfer-encoding:message-id:references:to;
 bh=kbGn7Gzb2/bEzGdWwz484+5feTa9qwyvlsHLGP3+WV4=;
 b=VCQsRDEjtvls+q4fnYz314XJsSCjm4ipoJwVXvMSTazr2Ij6hUk1EIO5ymkqDoq7+p
 bf4n1/VBMQlQ4uRsUx/HN77/3baUkgCblk414jDhixZ88czCwTQcY7SSJnrd0WBNcULp
 EqA/LqtpKWB4FBT2OxFHauoPp16Qq9kcMn/J2jtda/M5WVhH9WKEreasTVhNK4USDvv0
 3ffJzIy6EbVR/6M62EnugconGSL0GTBKaO4UlOAD7YybJ0RTc33T0HEhr4g5W6syr43K
 nmJzOyjtlzSkx+RXiqtkvKXu7GQAEiHcicFNXV9RZ0evtJMw7FaF4RyEMW0ttCoK4Epp
 g0aQ==
X-Gm-Message-State: AIkVDXLJ/4HRAuf4FK8TnXpMEPB3pb54+XhZWGLevp5thCXQWNCu3exFUMUi2Km4Oopvmw==
X-Received: by 10.99.117.90 with SMTP id f26mr27379177pgn.62.1485827634239;
 Mon, 30 Jan 2017 17:53:54 -0800 (PST)
Received: from ?IPv6:2607:fb90:f41:fefa:d47f:9ef9:7da8:eb97?
 ([2607:fb90:f41:fefa:d47f:9ef9:7da8:eb97])
 by smtp.gmail.com with ESMTPSA id p15sm35550982pfk.58.2017.01.30.17.53.53
 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Mon, 30 Jan 2017 17:53:53 -0800 (PST)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: How to delete read only files.
From: Ngie Cooper <yaneurabeya@gmail.com>
X-Mailer: iPhone Mail (14D27)
In-Reply-To: <1485821962.3017.32.camel@freebsd.org>
Date: Mon, 30 Jan 2017 17:53:52 -0800
Cc: Balaji Palaniswami <heisenbug.bala@gmail.com>, freebsd-hackers@freebsd.org
Content-Transfer-Encoding: 7bit
Message-Id: <81EF95CB-126E-401B-B293-177D74804703@gmail.com>
References: <CAB0r=audiCeUGDiCu9y_d=O7p86wXRnqN1GGXrSs+6UC+xe=OA@mail.gmail.com>
 <1485821962.3017.32.camel@freebsd.org>
To: Ian Lepore <ian@freebsd.org>
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>;
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2017 01:53:55 -0000


> On Jan 30, 2017, at 16:19, Ian Lepore <ian@freebsd.org> wrote:
> 
>> On Mon, 2017-01-30 at 16:12 -0800, Balaji Palaniswami wrote:
>> Hi,
>> 
>> I am trying to delete read only files.
>> 
>> # pwd
>> /usr/home/bp/nfsroot/lib
>> # whoami
>> root
>> # ls
>> libc.so.7       libcrypt.so.5   libthr.so.3
>> # ls -ltr
>> total 3264
>> -r--r--r--  1 root  wheel  1460592 Jan 29 12:07 libc.so.7
>> -r--r--r--  1 root  wheel    51640 Jan 29 12:07 libcrypt.so.5
>> -r--r--r--  1 root  wheel   109568 Jan 29 12:08 libthr.so.3
>> # rm -rf libc.so.7
>> rm: libc.so.7: Operation not permitted
>> 
>> # chmod 777 libc.so.7
>> chmod: libc.so.7: Operation not permitted
>> 
>> Please suggest me some ways to delete these files.
>> 
>> Thanks,
>> Balaji
> 
> Those libraries typically have the 'schg' flag set on them, as do some
> others in the tree.  If you need to wipe everything under nfsroot, the
> typical incantation is
> 
>   rm -rf nfsroot/ ; chflags -R noschg nfsroot/; rm -rf nfsroot/
> 
> that deletes everything it can first, then changes the flags on what's
> left, then deletes them too.  (Doing the noschg first requires
> examining/changing 145,000 files.)

chflags -R 0 covers the nouchg case as well.

Cheers,
-Ngie



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1701301625040.85129>