Исходное сообщение
"Опрос для расстановки приоритетов в развитии FreeBSD" Отправлено анонн, 28-Апр-19 16:51
> У большинства бздунов уже деменция ;) > https://www.zdnet.com/article/mandrake-linux-9-2-kills-some-.../ > CD-ROM > An instruction sent by the operating system core, or kernel, erases the drives' firmware, Ну совсем одно и то же, че. Зачем тогда так далеко ходить в 2003? Или "Леннарт хороший, леннарт ненарочно!" https://lwn.net/Articles/674940/ The problem was first reported to the Arch Linux forums in a thread that has been moved so that it is only available to registered users. Essentially, the user "9233" reported running:     rm -rf --no-preserve-root / The reason given was to "get rid of the pretty bloated Arch installation" on an MSI notebook. As noted in the post, there are plenty of other ways to accomplish that (e.g. reformat the partition), but that was the one chosen. After doing so, the system would no longer even start up the firmware after a power cycle, thus it couldn't boot or even allow the firmware settings to be changed.

Ваше сообщение
Имя*:
EMail:	Для отправки ответов на email укажите знак ! перед адресом, например, !user@host.ru (!! - не показывать email). Более тонкая настройка отправки ответов производится в профиле зарегистрированного участника форума.
Заголовок*:
Сообщение*:	>> У большинства бздунов уже деменция ;) >> https://www.zdnet.com/article/mandrake-linux-9-2-kills-some-cd-rom-drives/ >> CD-ROM >> An instruction sent by the operating system core, or kernel, erases the drives' firmware, > Ну совсем одно и то же, че. > Зачем тогда так далеко ходить в 2003? Или "Леннарт хороший, леннарт ненарочно!" > https://lwn.net/Articles/674940/ > The problem was first reported to the Arch Linux forums in a > thread that has been moved so that it is only available > to registered users. Essentially, the user "9233" reported running: > rm -rf --no-preserve-root / > The reason given was to "get rid of the pretty bloated Arch > installation" on an MSI notebook. As noted in the post, there > are plenty of other ways to accomplish that (e.g. reformat the > partition), but that was the one chosen. After doing so, the > system would no longer even start up the firmware after a > power cycle, thus it couldn't boot or even allow the firmware > settings to be changed.
	Введите код, изображенный на картинке: