Moderator: Moderators
fdisk -l
grub-mkconfig -o /boot/grub/grub.cfg
huwie wrote:joeoden, many thanks for taking the time to post. However I have not made myself clear. Sabayon is gone; I had an urgent need to use Windows and after trying a few quick solutions, the only way I could guarantee that at the time was to just install another distro. The only reason I posted was curiosity really. I suspect there was an error in Sabayon's implementation of some update to GRUB or related package.
ReemZ wrote:I suspect your suspicion is incorrect.
I've not nuked winblows yet, and it still shows up in GRUB.
Next time you encounter a problem, collect more info and try to be a little more patient so it can get solved...
huwie wrote:ReemZ wrote:I suspect your suspicion is incorrect.
OK. Why?
I've not nuked winblows yet, and it still shows up in GRUB.
huwie wrote:Ah, the classic "well it works for me!" That does not mean anything.
huwie wrote:ReemZ wrote:Next time you encounter a problem, collect more info and try to be a little more patient so it can get solved...
Did you even read my post? Time was an issue. I had an urgent need to use Windows and did what I had to do. Besides, I've lost patience with Sabayon. This is the second time in as many years that it has rendered my system unusable. I no longer have the time nor the inclination to work through ridiculous problems like these that no end-user should ever have to encounter.
ReemZ wrote:What it does mean is that it's not the Sabayon team's fault.
No, I always respond to posts without reading them
This ridiculous problem could lie within Grub, or, as not everyone seems to have encountered it, might just be caused by something you did. Have you considered the possibility? Your rant suggests you haven't...
If you have such an urgent need to use that excuse for an OS and can't handle ONE hiccup per YEAR without going on one, then maybe Linux isn't for you.
Return to Sabayon Linux General Discussion
Users browsing this forum: No registered users and 2 guests