Messages in this thread | | | Subject | Re: True story: "gconfig" removed root folder... | From | Doug McNaught <> | Date | Thu, 15 Jan 2004 10:20:46 -0500 |
| |
Roman Zippel <zippel@linux-m68k.org> writes:
> On Thu, 15 Jan 2004, Ozan Eren Bilgen wrote: > >> Today I downloaded 2.6.1 kernel and tried to configure it with "make >> gconfig". After all changes I selected "Save As" and clicked "/root" >> folder to save in. Then I clicked "OK", without giving a file name. I >> expected that it opens root folder and lists contents. But this magic >> configurator removed (rm -Rf) my root folder and created a file named >> "root". It was a terrible experience!.. > > I only did a quick check with menuconfig. Are you sure it's really > removed? It should still be there as "/root.old". > I probably should change the behaviour of the save routine to behave > differently for directories as argument, but it doesn't remove it. > (Changing gconfig to only accept files in the save request would probably > be nice too...)
The real lesson here is "don't compile your kernel as root". There's no need to do so.
-Doug - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |