Tag Info

Hot answers tagged

13

You're not going to be able to use GParted because the filesystem is on LVM and GParted does not support that. First, TAKE A BACKUP OF THE VM. Then perform the following as "root" from a command line. It looks like you've already rebooted but just in case, ensure the kernel recognizes the larger disk echo 1 > /sys/class/scsi_disk/0:0:0:0/device/rescan ...


7

The shred command can zero out a file. To do what you want, I think something like this should work find /var/cache/pacman/pkg -type f -exec shred -n 0 -z {} \; \ && rm -rf /var/cache/pacman/pkg/*


7

You can install the correct kernel header files like so: $ sudo yum install "kernel-devel-uname-r == $(uname -r)" Example This command will always install the right version. $ sudo yum install "kernel-devel-uname-r == $(uname -r)" Loaded plugins: auto-update-debuginfo, changelog, langpacks, refresh-packagekit No package kernel-devel-uname-r == ...


5

Using dmidecode or lshw and greping seems to be to be the best way to find out.


5

I think all you need to do is run reset. If that doesn't help, look to see if you changed any files in /etc recently (e.g. find /etc -mtime -1) and read the unicode_start or consolechars man pages.


5

In order to compile kernel modules for your running kernel, you need install the kernel headers. The following command should work: apt-get install linux-headers-$(uname -r) build-essential


5

Don't login as root over ssh; rather, create an user for logging in and then become root. But editing /etc/ssh/sshd_config and adding the line PermitRootLogin yes (or changing if it's already set to No) should do it.


5

You can use who command to find out all the logged in users. There is w command also available to find out the same.


5

You can do it with shred command: shred -z -u <filename> -z option makes file become zero, then -u option will delete file.


5

That's typically not a problem. The WiFi on the host is not actually directly accessible to the VMware guests, or any VM guests using other technologies such as KVM, VirtualBox, etc. The hardware that's present in the physical host is interacted through virtual hardware that's presented to the guest VMs through the software BIOS that the various ...


4

The right way to do this would be to find the config file that is changed, and edit it to the correct resolution. But I'm not an XFCE user so you'll have to look for this yourself :) Another, desktop-agnostic way is to change the resolution using xrandr. Assuming you can still boot up your computer and use Ctrl+Alt+F1 to access a command prompt, you can ...


4

I did not download it and not sure if this is everything but you should be able to get started with it. The most important part is that you are able to use the provided disk image. VirtualBox supports vmdk (Vmwares image format) out of the box. So you should be able to directly use the provided disk image with VirtualBox. If this does not work have a look ...


4

Install an NTP service on the virtual machine: sudo apt-get install ntp That way the virtual machine (assuming it has internet access) will set its time from a remote NTP server. If this is already installed, check that the service is running: sudo service ntp status If it is not, start it: sudo service ntp start Finally, you can force it to get ...


4

You often cannot run virtualization products inside other virtualization products. In this case you're attempting to run KVM (one virtualization product) inside another one (VMware), and this might be technically feasible, the performance of having to run a nested hypervisor inside another hypervisor on your Dell Inspiron laptop will likely be completely ...


4

If you only changed the partition size, you're not ready to resize the logical volume yet. Once the partition is the new size, you need to do a pvresize on the PV so the volume group sees the new space. After that you can use lvextend to expand the logical volume into the volume group's new space. You can pass -r to the lvextend command so that it ...


3

You need to install the VMWare Tools package in the guest OS, then copy and paste should work seamlessly between host and guest.


3

You've defined a gateway on both interfaces. So there is a default route through both interfaces. I'm not sure what exactly happens in this case, but I doubt this is what you intended. I suspect that only a smaller network should be accessible through eth0. You can do this by changing the corresponding stanza like this: iface eth0 inet static address ...


3

Disk alignment used to be rather trivial to figure out. All the tracks had the same number of sectors of the same size. Modern high density drives use variable numbers of sectors per track maintaining roughly the same bit density on the platter. They still report the old sizing information of cylinders, tracks, and sectors. Actual sector geometry varies ...


3

The best idea would probably to look at the hardware. At least with VirtualBox you can easily determine that you are on a virtual machine, due to the names of some of the hardware devices (for example /sys/block/sda/device/model will say "VBOX HARDDISK"). Since all your machines are VMware, just pick one of those things and check that.


3

You could try Joanna Rutkowska's Red Pill This little program examines the IDTR (interrupt descriptor table register) using the SIDT instruction (x86 only), which apparently will be set differently by different VMMs.


3

If all you need is a way to tell whether the OS/host is a virtualized host or not, just you have a perl module Sys::Detect::Virtualization and the script with it virtdetect. It does all the possible heuristics/guess detections and reports the detected OS environment. Give it a try. http://search.cpan.org/dist/Sys-Detect-Virtualization/script/virtdetect


3

VMware will translate your wireless cards on the host to wired cards that are available to the guests. The only type of network card that you will be able to add to the guest is a hardwired card. What you most likely want to do it setup the Fedora guest to use "Bridged" networking mode, and then config fedora to use DHCP. Assuming (bad I know), that you ...


3

In addition to the grub password, you also need to configure the BIOS to not allow booting from media other than the device that contains your primary OS. You will want to set a BIOS password so this configuration can not be changed. Unless your drives are encrypted, physical access to the machine is access to your data. Even with a BIOS password the CMOS ...


3

The easiest way is probably just not to have a default route. If you've set up a static IP address, edit /etc/network/interfaces and comment out the "gateway" line. If you're using DHCP, you may be able to not ask for a gateway (edit /etc/dhcp3/dhclient.conf and change the "request" to not ask for "routers", but I haven't tested this. Alternatively, you ...


3

I have some experience in usage of python library for configuring vmware, pysphere. Possible tasks, (taken from official web site) Connect to VMWare's ESX, ESXi, Virtual Center, Virtual Server hosts Query hosts, datacenters, resource pools, virtual machines VM: Power on, power off, reset, revert to snapshot, get properties, update vmware tools, clone, ...


3

Your new partition (/dev/sda4) is just after /dev/sda3, which should make things straightforward. Booting from a gparted live-CD (which, from your /dev/sr0, seems that you already have) and then resizing /dev/sda3 should work, but back up your /home first (you might have hard drive corruption if you lose power, your virtual machine or host OS ...


3

If you have a VM guest that's Linux then you could build t he Kernel inside of that VM and boot it inside that way. That's what I do all the time to save from mucking up my primary system.


3

You can also use the tool zerofree to zero out all the blocks on disk that are unused. This can save you a significant amount of space. This method will require that you boot into an alternative OS such as Finnix. You could also use Parted Magic which comes with zerofree installed. Example Using Finnix: $ sudo apt-get update && sudo apt-get ...


3

The specific attribute in this issue is i, the immutable attribute. The file was marked immutable. This means it is unchangeable at all by any user including root. Root can still change the attributes and remove the immutable attribute, but must to so first before making changes to the file, unlike standard no-write permissions to a file which root can ...


3

If you actually want to run linux-0.01 (the one circa 1991), VMware may not be the best option (but see below). The VMware, being a high performance "same platform" VM, exposes much less details on the underlying execution context and less opportunities to tweaking it, compared to a full fledged platform simulator, such as QEMU or Bosch. However, to answer ...



Only top voted, non community-wiki answers of a minimum length are eligible