Camaleón <noela...@gmail.com> writes: >> 2) Should it be considered a bug that grub files are written when boot >> is not mounted. Seems like if the routine notices (which it does) >> that those files are absent, should there not be further code to >> check for boot being mounted? >> It seems it should not be possible for `/boot/grub' to be created on >> an empty boot. Not during an update. > > If the package is installed and the config file needs to be updated the > upgrade routine uses to ask what to do (keep the old file, compare both, > replace it with the nre one...). If the partition where the file lies is > not mounted then it's up to the admin user what to do.
Yes, all that happened. I finally said OK to the new one since I had never edited the old one, I figured a new default would be ok too. But about boot not being mounted... well yes, it was my doing. Old habits die hard. In the gentoo world, where I came from keeping boot unmounted is a common practice... it once was on debian too. Some yrs ago when I fiddled with debian it was quite common and I'm pretty sure was recommended even. Some say it is more secure that way. And since Its easily done then seem like a net gain. Being new to grub2 I wasn't fully aware the grub.cfg resided on boot. Some of the config files for grub do not. Or at least that is so on ubuntu where I stopped awhile before coming to debian. So I didn't automatically think about mounting boot. But also much of an update happens more or less unseen so I wasn't watching that closely either. For example, I hadn't noticed that grub was to be upgraded. But even while that duty (mounting boot) may be seen as an admin chore, still there should be some warning or the like... no? I mean it seems like it would be seen as a problem and unexpected, to find boot utterly empty on an upgrade, that is a running OS, UNLESS it was umounted, and in that case its clearly not smart to write new files to the mount point. >> 3) About etc resolv.conf being rendered useless during update: That >> two seems like it should be bug > > You mean it changed its content without asking in the middle of the > upgrade? That sounds risky :-? Not in the middle no. More like at or near the end. There was never any warning about not being able to download pkgs, When I first tried to mail the OP of this thread is when I noticed I was off line. That was shortly after the update had finished. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8762i9dvc0....@newsguy.com
