> On Feb 2, 2016, at 17:57, Valeri Galtsev wrote:
>
> Dear All,
>
> Suppose I executed the command
>
> rm -rf /
There was also this article recently that pointed out that if the box boots via
UEFI, you may brick the machine, depending on setup.
On Fri, February 5, 2016 1:55 pm, Nathan Duehr wrote:
>
>> On Feb 2, 2016, at 17:57, Valeri Galtsev
>> wrote:
>>
>> Dear All,
>>
>> Suppose I executed the command
>>
>> rm -rf /
>
> There was also this article recently that pointed out that if the box
> boots via UEFI,
On 02/05/16 14:55, Nathan Duehr wrote:
>
>> On Feb 2, 2016, at 17:57, Valeri Galtsev wrote:
>>
>> Dear All,
>>
>> Suppose I executed the command
>>
>> rm -rf /
>
> There was also this article recently that pointed out that if the box boots
> via UEFI, you may brick
On 02/05/2016 06:31 PM, Mark LaPierre wrote:
So let me get this straight. You are saying that you can make changes
to the MB ROM/EPROM/whatever hardware the vendor uses, by issuing an
erase command on a hard drive?
No, but you can erase the UEFI variables by issuing "rm" on them if the
OS
Dear All,
Suppose I executed the command
rm -rf /
on my CentOS 7 box. After it did what it could, how much damage will be
done to what I have (or _had_ rather ;-) on my hard drive?
I'm going to describe simple experiment which was prompted in another
thread. I need to say a few words before I
On 02/02/2016 04:57 PM, Valeri Galtsev wrote:
Suppose I executed the command
rm -rf /
on my CentOS 7 box. After it did what it could, how much damage will be
done to what I have (or _had_ rather ;-) on my hard drive?
In your experiment, rm processed /boot and /data first, and then /proc,
6 matches
Mail list logo