similar to: In A UEFI World, "rm -rf /" Can Brick Your System

On Mon, February 1, 2016 1:33 pm, m.roth at 5-cent.us wrote: > Excerpt: > Running rm -rf / on any UEFI Linux distribution can potentially > perma-brick your system. Yes, I kind of like "rm -rf /". If my memory doesn't fail me, long ago it was one of the tricky questions in sysadmin exam (not that anymore if I read what you, Michael, write further correctly...). Anyway,

On Mon, February 1, 2016 1:56 pm, Valeri Galtsev wrote: > > On Mon, February 1, 2016 1:33 pm, m.roth at 5-cent.us wrote: >> Excerpt: >> Running rm -rf / on any UEFI Linux distribution can potentially >> perma-brick your system. > > Yes, I kind of like "rm -rf /". If my memory doesn't fail me, long ago it > was one of the tricky questions in sysadmin

On 02/01/2016 01:59 PM, John R Pierce wrote: > would deleting the inode /sys/(whatever) actually modify UEFI memory? Yes. That is how the UEFI management interface works.

Once upon a time, m.roth at 5-cent.us <m.roth at 5-cent.us> said: > Excerpt: > Running rm -rf / on any UEFI Linux distribution can potentially > perma-brick your system. Did someone think running "rm -rf /" is a good idea? > Ok, *now* tell me why we shouldn't hate systemd? This has zero to do with systemd. This is a by-product of how the kernel driver and

In article <75D47FDC6A99F24F87A6465BAF326D5018C50F69 at COLUMBA02.user.uu.se>, Sorin Srbu <Sorin.Srbu at orgfarm.uu.se> wrote: > > -----Original Message----- > > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > > Behalf Of m.roth at 5-cent.us > > Sent: den 1 februari 2016 20:34 > > To: CentOS > > Subject: [CentOS] In A

John R Pierce wrote: > wait. would deleting the inode /sys/(whatever) actually modify UEFI > memory? sure, writing to those inodes could do all sorts of harm, but > deleting the inodes in the /sys filesystem, I'm not so sure this isn't a > tempest in a teapot so to speak. It's going to get /boot. And under there, it'll get /boot/EFI. mark

On Mon, 1 Feb 2016 13:44:48 -0600 Chris Adams wrote: > Did someone think running "rm -rf /" is a good idea? Quote from one of the people who commented on that article: QUOTE: You have this in a script: rm -rf "${DIRECTORY}"/ Now, you have a bug in the script and ${DIRECTORY} is not initialized. You then get rm -rf / executed. One should always ensure that DIRECTORY is

On Mon, February 1, 2016 4:24 pm, Gordon Messmer wrote: > On 02/01/2016 01:59 PM, John R Pierce wrote: >> would deleting the inode /sys/(whatever) actually modify UEFI memory? > > Yes. That is how the UEFI management interface works. Will doing rm -rf / actually delete anything in /sys? IMHO, not. The above command first will get to removing /dev, and it will delete /dev/sda1 or

> -----Original Message----- > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > Behalf Of m.roth at 5-cent.us > Sent: den 1 februari 2016 20:34 > To: CentOS > Subject: [CentOS] In A UEFI World, "rm -rf /" Can Brick Your System > > As a public service announcement, recursively removing all of your files > from / is no longer

On 2/1/2016 2:07 PM, m.roth at 5-cent.us wrote: > John R Pierce wrote: >> >wait. would deleting the inode/sys/(whatever) actually modify UEFI >> >memory? sure, writing to those inodes could do all sorts of harm, but >> >deleting the inodes in the /sys filesystem, I'm not so sure this isn't a >> >tempest in a teapot so to speak. > It's

wait. would deleting the inode /sys/(whatever) actually modify UEFI memory? sure, writing to those inodes could do all sorts of harm, but deleting the inodes in the /sys filesystem, I'm not so sure this isn't a tempest in a teapot so to speak. -- john r pierce, recycling bits in santa cruz

On Tue, 2 Feb 2016 10:18:09 +0000 (UTC) Tony Mountifield wrote: > killing the UEFI stuff stops you ever being able to do a re-install on that box. Is that correct? Apparently so. > Is there no way to do a factory reset of the BIOS? Apparently not. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

On 02/01/2016 01:48 PM, Valeri Galtsev wrote: > I just discovered that I couldn't even re-cite alphabet correctly today: > it is /bin that you loose, but /etc alphabetically goes after /dev, so > will not even loose your /etc, I'm pretty sure none of that is correct. Once "rm" launches, all of the libraries and files that it needs are memory mapped and reference

On Mon, February 1, 2016 4:23 pm, Gordon Messmer wrote: > On 02/01/2016 01:48 PM, Valeri Galtsev wrote: >> I just discovered that I couldn't even re-cite alphabet correctly today: >> it is /bin that you loose, but /etc alphabetically goes after /dev, so >> will not even loose your /etc, > > I'm pretty sure none of that is correct. Once "rm" launches,

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 do it, however. First of all, that other thread was about doing the same thing on UEFI machine.

On 02/05/16 14:55, Nathan Duehr wrote: > >> On Feb 2, 2016, at 17:57, Valeri Galtsev <galtsev at kicp.uchicago.edu> 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 Feb 2, 2016, at 17:57, Valeri Galtsev <galtsev at kicp.uchicago.edu> 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. http://www.phoronix.com/scan.php?page=news_item&px=UEFI-rm-root-directory ? Nate

Not all UEFI guests can survive conversion, because of lost bootloader information in UEFI NVRAM. But some guest can cope with this because they have a fallback bootloader and use UEFI Removable Media Boot Behavior. (see https://uefi.org/sites/default/files/resources/UEFI_Spec_2_8_A_Feb14.pdf 3.5.1.1 Removable Media Boot Behavior) to load. If UEFI firmware can't find a bootloader in its

Author: swilcox Repository: /hg/zfs-crypto/gate Revision: 89bb7eb80bb8cb92f0071ea0085e6aa3d116f7f6 Log message: 6361469 tsufs hang on rm -rf command Files: update: usr/src/cmd/fs.d/ufs/mkfs/mkfs.c

Hi Everyone, Recently i created a snapshot of an existing volume which had some amount of data. Now that after creating the snapshot i have tried deleting the same snapshot. But i am getting ENOTEMPTY for "rmdir". But when i see the actual files inside are deleted not the parent directory. From the code it looks like if (inode->i_size >