This is a security hole in my opinion and should be plugged by editing the lock screen ui layout:
#find these objects and set the visible property to false
object class="GtkLabel" id="note-tab-label"
object class="GtkLabel" id="auth-username-label>
object class="GtkLabel" id="auth-realname-label"........
Install Errors on Version 12:
This error happened on QEMU emulator version 2.11.1 pve-qemu-kvm_2.11.1-5
on Proxmox/Debian but installing on QEMU.12 on Centos 6 did not produce the error.
*Update it is not related to the OS or QEMU version. This happened in Centos 6 too after a second install.
What really causes this even though you successfully install........
The strange thing is that usually the first install or two will work on any new machine but then it suddenly won't. I had this experience on QEMU 2.13 on a different machine. There is something finicky or buggy about the CUCM installer even when choosing the same virtual hardware specs.
QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2-2.506.el6_10.1), Copyright (c) 2003-2008 Fabrice Bellard
systemd is like the service manager for your Centos and other modern Linux distributions (including Debian/Mint/Ubuntu) allows you to enable services, stop them, restart them, check their status and even reboot your system.
The key commands or arguments you will use with systemctl are the following:
list-units [PATTERN...] List loaded units
It has been a big pain for a long-time to install Windows from a Linux environment. I used to run a windows install server and it never worked right for some reason (the install would fail on most servers).
Before getting start be sure to setup your samba share so once you boot into WinPE you can mount the install for whatever Windows you want
path = /tftpboot/images/winstall
guest ok = yes........
In Centos 7 the days of editing the "kernel"line and adding "single"are gone. On top of that sometimes after a new install passwords do not work, maybe you forgot your password or for some other reason you need to break in or fix your system? It could also be because you can't mount your root / or some other /etc/fstab error and many other errors.
1. Edit your grub settings and find the linux16 /vmlinu........
yum -y install samba
mkdir syslinux;cd syslinux;unzip syslinux-6.03.zip
mkdir -p /tftpboot/libs/
cp bios/com32/modules/linux.c32 /tftpboot/libs/
cp bios/com32/libutil/libutil.c32 /tftpboot/libs/
cp bios/com32/lib/libcom32.c32 /tftpboot/libs/
#add lib path
echo "PATH libs" >> /tftpboot/pxeli........
Done on Centos 7.3 very important as clearly based on older guides it was a lot easier and more simpler! Hint do not use grub2-install!
One huge caveat if you are an oldschool user or sysadmin who has avoided UEFIbooting
The normal way will not work here if your Centos was using UEFI. Newer systems use it by default.
The easiest way to check is to do an fdisk -l if your sy........
*Update so this doesn't work it must be something to do with the path of nfs or something else but the installer fails with "Installer crashed" at the end whereas with the CD/USB it works.
This assumes you've already installed and configured a separate PXE/DHCP server somewhere else and your /tftpboot directory is setup.
This is for Linux Mint 18.1 but generally applies to most versions although you may have tro change things like "casper"........
You may get this after a long time of not rebooting but especially if you have rsync'd a / partition or deployed an image to another VPS or computer, you will often have this issue.
The good thing it usually just takes a reboot.
Here is more info from Centos........
grub> root (hd0,0)
Filesystem type is ext2fs, partition type 0xfd
grub> setup (hd0)
But if you do:
it does work, I think hd0/sda had a GPT partition that was not removed properly (what I did was just dd bs=512 count=1 the partition table from another drive since the partition table should be identical).
Checking if "/boot/grub/........
I am getting this error:
kernel:[14277.697049] EDAC MC0: UE row 4, channel-a= 0 channel-b= 1 labels "-": (Branch=0 DRAM-Bank=0 RDWR=Read RAS=7048 CAS=0 FATAL Err=0x4 (>Tmid Thermal event with intelligent throttling disabled))
But many people believe this is a bug/false message and the server is running stably.........
Here is the scenario you or a client have a remote machine that was installed as a standard/default minimal Centos 6.x machine on a single disk with LVM for whatever reason. Often many people do not know how to install it to a RAID array so it is common to have this problem and why reinstall if you don't need to? In some cases on a remote system you can't easily reinstall without physical or KVM access.
So in this case you add a second physical or disk or already ha........
If you remove the white label on the chip (near the CMOS battery) you will find the following details about it:
SST 49LF080A 33-4C-NHE
It is the PLCC32 type and can be pried and removed safely (but be very careful) with an eye glass flat head screw driver.
If you just have a bad flash you may be able to reprogram your original or just buy another one with the part# above and reprogram it.
This is great news for people who have bricked th........
I'm not sure why I'm getting these but all memory modules are the exact same and all passed memtest successfully although they are ECC. I've heard that ECC RAM can't be tested as well and the kernel seems to indicate they are non-fatl recoverable errors. I wonder if the BIOS has aggressive RAM timing or maybe the controller or motherboard is bad.
[ 12.716515] EDAC MC: Ver: 2.1.0
[ 12.717771] EDAC MC0: Giving out device to........
The above site has the patch that does this essentialy turning a Desktop Windows into a full fledged RDP server.........
At first it was configured as a RAID 0, then I deleted the Virtual Disk Group.
I thought both drives would be shown and detected in Linux as sda and sdb but it actually shows nothing.
To make them work you have to hit Ctrl+R before the system boots (when prompted) and create a Virtual Disk Group. In my case I created each one as RAID 0 (with a single drive only) as I just wanted JBOD but there is no such option or default in these Dell Pe........
kernel: EDAC MC0: CE page 0x0, offset 0x0, grain 1073741824, syndrome 0x1a, row 2, channel 0, label "": i3200 CE
I believe this is a hardware issue, it's usually bad RAM, incompatible RAM or bad timing or even a motherboard/RAM controller.........
I find it very annoying that this mouse has buttons on the side where you grip it and the left one goes back in the browser and the right one goes forward. Imagine if you're filling out a form and hit it, most forms/websites have no protection against it.
Here's how I fixed it with xinput, it's too bad there's no good standard GUI to........
This is something I often setup for clients because it's very helpful for people in datacenters, this allows custom OS installs on demand, you can customize it more by using kickstart etc.. but here's a base I use before customizing more:
This little script below will install everything you need to get booting by PXE Linux.
It also assumes you set a local IP (be sure not to overwrite your existing IP) on eth0:0 (note the :0) as 192.168.1.10 and it........
I installed 5.5 with a 300GB RAID 1 partition (boot is also on this partition). It booted up fine the first few times until after I used a Live CD and accessed the array, and it became named /dev/md127 for some reason.
Now whenI boot into CentOS I get a kernel panic and different errors, once I got "invalid superblock", even though the array is fine (it didn't happen again, probably because I was sure to dismount and stop the mdadm array properly).
Before we start I take no responsibility for this, you should have a backup and if you make a mistake during this process you could wipe out all of your data. So backup somewhere else before starting this as a precaution, or make sure it's data you could afford to lose.
The RAID 1 Setup (Hardware Wise)
I've already setup my 2 x 1TB (Seagate) drives with identical partitions, make sure your new hard drive (the empty one) is setup like your curr........