Hi Guys,
It is surprised that VMware-tools gives 4 options only for resolutin after
I install VMware-tools for CentOS release 5.10 (Final), a guest OS running
with VMware player 6.0.1 build-1379776. The kernal is 2.6.18-371.4.1.el5
x86_64 x86_64. The host system is win7 64bit OS. The hardware is Thinkpad
T440S with a FHD display, 1920 X 1080. The following is what I get when I
run vmware-config-tools.pl. The VMware-tools is
VMwareTools-9.6.1-1378637.tar.gz. I think that is the latest version.
CODE: SELECT ALL
<https://www.centos.org/forums/viewtopic.php?f=19&t=44910#>Please
choose one of the following display sizes that X will start with:
[1] 640x480
[2] 800x600
[3] 1024x768
[4]< 1280x800
Please enter a number between 1 and 4:
[4] 4
Obviously it does not contain the resolution I need. The information I get
with getinfo.sh has one line "VGA compatible controller [0300]: VMware SVGA
II Adapter [15ad:0405]"
VMware-tools worked well when I installed CentOS 5.5 for my virtual
machine. What's wrong? Would you please help me? Thank you.
Best Regards,
Yawei
I can easily get a copy of my pending cron jobs so I can keep a backup. "crontab -l > mycron.txt" is part of my backup script, and that does the job nicely.
Is there a way that I can get a copy of pending at jobs for this purpose? I can get a list of pending jobs with atq, and I can show each job with at -c jobname, but I don't see a way to get something that is suitable for use as a file that I can keep as a backup of the pending jobs.
--
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
Hey,
http://zfsonlinux.org/epel.html
If you have a little time and resource please install and report back
any problems you see.
A filesystem or Volume sits within a zpool
a zpool is made up of vdevs
vdevs are made up of block devices.
zpool is similar to LVM volume
vdev is similar to raid set
devices can be files.
Thanks,
Andrew
Hi,
over time the requirements and possibilities regarding filesystems
changed for our users.
currently I'm faced with the question:
What might be a good way to provide one big filesystem for a few users
which could also be enlarged; backuping the data is not the question.
Big in that context is up to couple of 100 TB may be.
O.K. I could install one hardware raid with e.g. N big drives format
with xfs. And export one big share. Done.
On the other hand, e.g. using 60 4 TB Disks in one storage would be a
lot of space, but a nightmare in rebuilding on a disk crash.
Now if the share fills up, my users "complain", that they usually get a
new share (what is a new raidbox).
From my POV I could e.g. use hardware raidboxes, and use LVM and
filesystem growth options to extend the final share, but what if one of
the boxes crash totally? The whole Filesystem would be gone.
hm.
So how do you handle big filesystems/storages/shares?
Regards . Götz
--
Götz Reinicke
IT-Koordinator
Tel. +49 7141 969 82 420
E-Mail goetz.reinicke(a)filmakademie.de
Filmakademie Baden-Württemberg GmbH
Akademiehof 10
71638 Ludwigsburg
www.filmakademie.de
Eintragung Amtsgericht Stuttgart HRB 205016
Vorsitzender des Aufsichtsrats: Jürgen Walter MdL
Staatssekretär im Ministerium für Wissenschaft,
Forschung und Kunst Baden-Württemberg
Geschäftsführer: Prof. Thomas Schadt