On Sat, Nov 28, 2015 at 6:12 AM, mr_L4N <serverp...@gmail.com> wrote: > I've add rescue in grub2 setting, same error with others many strange > problems, the last with resolv.conf. What's happens? I want to modify it to > add mine dns servers; open the file, modify it, but is impossible to save > because system says "file not exist". >
Is your keyboard working? Simply by adding rescue to your kernel line? Or did you resolve the other issue (if so I'm curious as to what it turned out to be). Are you SURE you were switching to another virtual console earlier? This means text mode with just a login prompt and no x11. If keyboard works with rescue and not otherwise you might still be looking at an x11 console (hit ctrl-alt-F1 to switch). As far as resolv.conf goes: If you're using networkd then you need to start/enable systemd-resolved (if it isn't already started), and then do an "ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf" to create it. Most other network managers directly modify the file in /etc, but systemd-resolved maintains a file in /run instead (on the principle that daemons shouldn't be storing temporary state in /etc). Getting the network up wasn't really the purpose of those notes (especially since everybody has their own preferences for network managers). > BTW i want to repeat all the step from the first with a new installation, > only a question: why you emerge @world before the kernel? I always emerged > kernel before, but Probably isn't the better choice. > That in particular is unlikely to matter. However, I often use a preconfigured world file in new installations that happens to have the kernel in it, so emerging @world brings in the kernel anyway. I do like to update @world before I go installing too much stuff because you create the risk of having to rebuild things if some key dependency gets updated later during the install. Also, I always do an emerge @world, but I don't always install a kernel (such as when installing a container/chroot). So, updating @world is part of the core install process in my thinking, and installing a kernel is just a supplement needed on systems that don't already have a kernel. But, again, that detail isn't likely to matter since the kernel just installs a bunch of sources that aren't linked to anything, and even a built kernel is statically linked for obvious reasons. -- Rich
