A regular BIOS update turned into a pain in the a**

Just found out that my 3-year-old Intel NUC8 has got a new BIOS release 0090 recently. I downloaded and upgraded it without think twice (which is going to waste some of my time later.)

I have two OS installed and dual boot configured on the hard drive. Windows 10 alongside with Ubuntu Desktop. By default, it will boot into GRUB menu by default, where I can choose whether or not to boot into Windows.

I have done BIOS update for this NUC several times before. But this time, after the new BIOS update, the machine boot directly into Windows without showing the GRUB menu. I tried to hit F10 on-boot to bring up the Boot selection menu to choose another EFI boot-loader — but something weird is: There is only one “Windows Boot Manager” up there, the “ubuntu” boot entry is missing.

Continue reading A regular BIOS update turned into a pain in the a**

Bing …

大约昨天(2021-Dec-16)下午开始注意到Bing (必应搜索) 出现访问困难。尝试了宽带和移动数据下的访问都是超时。一开始以为是DNS问题,换了后情况依旧。

今天还是和昨天一样无法访问。如果是DNS或者微软的服务器问题,不可能拖了那么久还没解决的。网上搜了下,发现原来不是个例。Bing自己也发布了一段简短的英文声明。

临时的方法

参考网上,目前暂时的解决方法,可以用备用的域名 www4.bing.com 进行访问。

或者可尝试修改hosts文件,把域名 www.bing.com cn.bing.com 对应的IP地址改为:204.79.197.200

结语

平时我自己是把Bing作为首选搜索引擎的。因为目前“普通的”上网姿势下,Bing比某度好用多了,广告少,并且外文关键字搜索能力也好得多。但愿这点事不会拖得太久,最终可以解决。要是Bing变成Google的待遇,那就实在太恶心人了。

附:

有关报道:https://www.ithome.com/0/592/920.htm

Bing自己也发布了一段简短的说明:

孜孜不倦的黑客 / Tireless Attacker

doge scream 日了个特大号的狗了! Holy super-sized shit! 刚才查看 fail2ban 日志的时候,被满满300多行日志吓尿 book。基本上从昨天中午开始就有个来自俄罗斯的 IP 一直在孜孜不倦地尝试进行 SSH 登录。通常被 ban 过几次之后攻击者就放弃了,哪会像这个家伙一样死心眼。而且我用的是非默认端口,这货应该是先扫描了端口boom。 I was scared by fail2ban log of my server — more than 300 lines of log showing a same Russia IP address trying to SSH into my server since yesterday noon. Usually attacker will give up after got banned by fail2ban several times, but this guy is tireless. And the port I’m using is not the default SSH port, clearly this piece of shit did a port scan before attack. Continue reading 孜孜不倦的黑客 / Tireless Attacker

CentOS 7 virt-manager “authentication failed”错误及解决方法

这两天在捣鼓CentOS 7,因为之前是在Debian用KVM,于是这次照着之前的做法来一步步安装KVM,然而最后打算用virt-manager来管理的时候,发现被拒之门外了。

virt-manager error

Unable to connect to libvirt.
authentication failed: no agent is available to authenticate.

呃,真够磨人的。看着像是权限问题。尝试了下,发现root级别的qemu:///system 是出错的,不过用户级别的qemu:///session 没有问题。因为默认是以非root用户执行virt-manager的,应该是这个原因导致权限的问题。

用户级别的权限受到很多限制,要全面发挥KVM的功能还是需要root级别。不过,现在却被挡在了门外。我先是检查了各种包有没有安装,结果是该装的都装了。 Continue reading CentOS 7 virt-manager “authentication failed”错误及解决方法