Re: [CentOS] Change default font size in terminal

[Robert G. (Doc) Savage]

-Original Message-
From: Yawei Guo 
Reply-to: CentOS mailing list 
To: CentOS mailing list 
Subject: [CentOS] Change default font size in terminal
Date: Tue, 21 Oct 2014 07:36:31 +0800


Hello,

I want to change default font size in terminal. The size is too small for a
1920x1080 screen. Thank you very much.

Yawei,

It's easy:

Edit --> Profile Preferences
Uncheck:  Use the system fixed width font
Change point size to a number larger than 12
Click on  OK  and  Close

--Doc Savage
  Fairview Heights, IL
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Change default font size in terminal

[Yawei Guo]

Hello,

I want to change default font size in terminal. The size is too small for a
1920x1080 screen. Thank you very much.


Yawei
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Continuous Release (CR) Repository updates are released for CentOS-6.6

[Johnny Hughes]

We have released the following updates into the 6.5/cr repository:

http://lists.centos.org/pipermail/centos-cr-announce/2014-October/thread.html

The updates include everything that will be on the 6.6 ISO Sets and also
everything to date that will be in 6.6 Updates.

We will continue to put updates into 6.5 CR until we actually release
CentOS-6.6.

For information on the CR repository, see this link:

http://wiki.centos.org/AdditionalResources/Repositories/CR

Thanks,
Johnny Hughes



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Amazon Marketplace AMI

[Patrick Flaherty]

On Fri, Oct 17, 2014 at 3:45 AM, Thorsten Höger  wrote:

> Hi,
>
> the updated Amazon Web Service AMI (ami-4ac6653d) has a serious bug.
> It is not possible to resize a disk after creating a new volume with a
> size greater than 8GB.
>
> resize2fs does nothing.
>
> The previous AMI worked perfectly but is no longer available. This bug is
> a show stopper
> for using CentOS on AWS.
>

 I rarely use the CentOS AWS market place AMIs, and frequently build my own
HVM images. It sounds more like the root FS isn't expanding based on the
volume thrown at it. I guess the image could have some sort of "delete last
partition, extend that partition to end of drive, extend root volume to end
of drive" magic in initrd, but that sounds sketch. Multiple volumes mounted
in multiple places are "better" than a single gigantic root partition in
traditional system engineering. You can snapshot your data volume, not your
os install volume, or your os install without your log directory, all using
native amazon tools.

For your specific problem, you can try this for an AWS specific solution:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/storage_expand_partition.html
(easy-ish, but time consuming)
* or you could do the traditional:
http://geekswing.com/geek/unix/extending-a-linux-disk-with-lvm-extending-root-partition/
* Or you could add another volume, and extend your VG onto that volume.
Actually, don't do that, you'd have to shut off the instance to snap shot
the drives to keep the blocks in sync. Which makes this dumb approach of
large root volumes even dumber.

If you want to make your own HVM instance. Here's the basic process I
follow. The post chunk from KS file has been edited a bit, but should work.
This was all stolen from various stack overflow and blog postings, if you
see your code in here, thank you for posting your work.

## Create VM locally in Virtual Box
## Convert VM disk image to RAW
Get qemu-img from http://wiki.qemu.org/Main_Page
qemu-img supports lots of file types, my file type was vmdk non-streaming.
 qemu-img convert -f vmdk -O raw c6ami.vmdk c6ami.raw
## Upload to Amazon
* Grab tools from: http://aws.amazon.com/developertools/351
* Set up your environment

export AWS_ACCESS_KEY=asdfasdfasdf
export AWS_SECRET_KEY=asdfasdfasdfasdfasdfsadfsdasdfasdf
export EC2_HOME=/where/you/downloaded/ec2_dev_tools
export JAVA_HOME=`/usr/libexec/java_home`

* Upload your file. Amazon only allows linux to be uploaded to the
following platforms:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/VMImportPrerequisites.html
ec2-import-instance c6ami.raw -f RAW -t m3.xlarge -a x86_64 -b
c6ami_bucket -o s3bucketkey -w s3bucketsecretkey -p Linux
* Wait

The kickstart file I use to build the image does this this on post to
enable sudo/centos user, and sriov if launched with enhanced networking
enabled.

yum clean all
chkconfig ntpd on
sed -i 's/^ssh_deletekeys:.*$/ssh_deletekeys:   1/'  /etc/cloud/cloud.cfg
sed -i 's/name: cloud-user/name: centos\
lock_passwd: True\
gecos: CentOS\
groups: \[adm, audio, cdrom, dialout, floppy, video, dip\]\
sudo: \[\"ALL=(ALL) NOPASSWD:ALL\"\]\
shell: \/bin\/bash/' /etc/cloud/cloud.cfg
echo '#!/bin/sh
/sbin/modprobe ixgbevf' > /etc/sysconfig/modules/sriov.modules
chmod 755 /etc/sysconfig/modules/sriov.modules
rm  /etc/udev/rules.d/70-persistent-net.rules
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] rsync question: building list taking forever

[Keith Keller]

On 2014-10-20, Les Mikesell  wrote:
> On Mon, Oct 20, 2014 at 1:12 PM, Keith Keller
>>
>> The OP said he was mounting the NFS over sshfs.
>
> OK, I don't see how that is possible because something would either be
> mounted as nfs or sshfs, not one over the other.

I'm just repeating what he wrote; perhaps the OP can elaborate.

> But if the
> intermediate host is allowed to ssh (as it must for sshfs to work) I'd
> throw a bunch of disk space at the problem and rsync a copy to the
> intermediate host, then rsync from there to the target at the other
> data center.

That was one of my suggestions earlier in the thread.

> Or work out a way to do port-fowarding over ssh
> connections from the intermediate host.

Or (as you and perhaps I suggested) some sort of OpenVPN link.

--keith

-- 
kkel...@wombat.san-francisco.ca.us


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] rsync question: building list taking forever

[Les Mikesell]

On Mon, Oct 20, 2014 at 1:12 PM, Keith Keller
 wrote:
> On 2014-10-20, Les Mikesell  wrote:
>>
>> So, you probably want the 'source' side of the transfer to be local
>> for faster startup. But... in what universe is NFS mounting across
>> data centers considered more secure than ssh?  Or even a reasonable
>> thing to do?  How about a VPN between the two hosts?
>
> The OP said he was mounting the NFS over sshfs.

OK, I don't see how that is possible because something would either be
mounted as nfs or sshfs, not one over the other.   But if the
intermediate host is allowed to ssh (as it must for sshfs to work) I'd
throw a bunch of disk space at the problem and rsync a copy to the
intermediate host, then rsync from there to the target at the other
data center.  Or work out a way to do port-fowarding over ssh
connections from the intermediate host.

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] rsync question: building list taking forever

[Keith Keller]

On 2014-10-20, Les Mikesell  wrote:
>
> So, you probably want the 'source' side of the transfer to be local
> for faster startup. But... in what universe is NFS mounting across
> data centers considered more secure than ssh?  Or even a reasonable
> thing to do?  How about a VPN between the two hosts?

The OP said he was mounting the NFS over sshfs.

--keith

-- 
kkel...@wombat.san-francisco.ca.us


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] how to identify build options

[Leon Fauster]

Am 20.10.2014 um 17:41 schrieb John R Pierce :
> On 10/20/2014 8:38 AM, kqt4a...@gmail.com wrote:
>> 
>> What options were used to build this package? 
> 
> you'd need to look at the SRPM.



http://vault.centos.org/6.5/updates/Source/SPackages/

--
LF


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CPAN dependency on CentOS 7

[Luigi Rosa]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Reindl Harald wrote on 20/10/2014 17:52:

> that may be true but you need to report that *upstream* CentOS is a package
> for package and bug for bug clone
> 
> https://bugzilla.redhat.com/enter_bug.cgi

Been there, done that

https://bugzilla.redhat.com/show_bug.cgi?id=1154741




Ciao,
luigi

- -- 
/
+--[Luigi Rosa]--
\

There is a difference between knowing the path and walking the path.
--Morpheus, Matrix
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJURTeFAAoJEO5WT/qgw4yKNLcP/At99DT64R0ilYielXqECIua
tP6zZcnr4PygGOSsolHbb6Mkix1kxzC2fAFTDAz1WOFFwQa2kRfWdPaED1FCzfip
WyvDNBhax5yECH0fBADigLR7aU6Z/5+AepRNM28n7f12zIHz91rsRwJ+w0zPefRA
/rsGImw0KvR0VWUkv2FF5KghTvJAAziYKVT0kiHpSs2X8W03ivJYrEI1Or+odP+D
YgsfYUSqfhnRliO8Xs7s8dm+7QFcMwKcDgnjF8xO2R2roQnvRzJaCEqjsYNLvxgG
aeQmnfu18GtX5fSL99OeL6Qsy7pPtNWlv1MOAlY//PKyNLZBcjTs3ZdU+JtDAqNd
fe7EAgG1mYrdasIiWRR8TlqCiV6bYkNSuG6A7RSLEFktUOAlaLe/MYzTUiDk6MSh
1tKnZinlozAbiO31uilf7quOzJ0Ur5NZ3YC0lyhlTObFAblfpaKBgiw6epXgVxHL
GsWs1Ed2Nc9ndUGkoUJmuFWQ/ivEzOANYM8fKaGNPl4b0lh1BuvP/OO675PFxcFH
6BRwSwpgtCw0+lIwJgxSIRYdILKKklWosV4RMXHkak4Pi1c+2fDJ8lYZy1e75Swj
rgpNQTW7eJouCXmrzzk0mZbt6nYzq56U+rifBDz8tx2RFrk+yCv6n+OPMs56EpPh
T5FFnphYrzY7cjS1PZ1R
=4XbR
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] CPAN dependency on CentOS 7

[Luigi Rosa]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Una a CentOS 7 with minimal install if I install perl-CPAN the first time I
execute cpan to download a mduel, the automatic configuration of CPAN fails
for missing Time/HiRes

The package perl-Time-HiRes should be installed as a dependency of perl-CPAN

The exact error is:

Would you like me to automatically choose some CPAN mirror
sites for you? (This means connecting to the Internet) [yes]
Trying to fetch a mirror list from the Internet
Fetching with HTTP::Tiny:
http://www.perl.org/CPAN/MIRRORED.BY

Looking for CPAN mirrors near you (please be patient)
Can't locate Time/HiRes.pm in @INC (@INC contains: /usr/local/lib64/perl5
/usr/local/share/perl5 /usr/lib64/perl5/vendor_perl
/usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/sha
re/perl5 /root) at /usr/share/perl5/Net/Ping.pm line 313.




Ciao,
luigi

- -- 
/
+--[Luigi Rosa]--
\

Naeser's Law: You can make it foolproof, but you can't make it damnfoolproof.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJURS59AAoJEO5WT/qgw4yKFEMP/1nYHUr5SC0IUQ6kiSEsQVBB
MO6YWy7DQZ5zgHCgLed2A6IjPqSy1fXq6JWkM4UmnAHEJWVyx+H0x+2onUixTDnv
cy+KnRMHD5A+wytPcKgWXGUzxYhYg8lmD18eTeZEPPI2qiQqdOhOOP+9UZv1f3Ku
QJRBdoThbUM5SJ338DkIOz9waedqgjBk0uxn8vzxVp8+xHDffvxFYzvt2SmXjrWc
RuGeltDBDgPxiTLWZfTFhA2aIyyEilUQ2zHAICZJ71sGAASQF/8+DVE2AINfP43A
VW5PGBFKySJ0US1an+RQ0gVoYb2Un8/249odLJUJZ94zdess87QcPmsF0YMdEdaB
6PSJZMOcm3XZzlt3Pld/CA8TSuvhMs5gVnmgCp95mpSKbzrr0v9Gz6ErpGmWUWc9
6hNeC8Bc9myE3+JgiA4oQOFPV+TMSG+OqYuOVPj7IuKes+XnOPxCxlM8g3qH07nD
rg100obawcwMUHCqCDdw+uIRO+ai/1F27SNKbrlI+ma66lbTV7CqxDE1jTA9UP3S
wK1QE0W9TvptkzsrS5PTVNPOiH/wfWAhvCHpw4w9gQXideu2m9P5SWXuAxv814Ze
sEYohjginoO9AdxXnlSiwz1rZqHoODXmLAULnkG6Zx+mW05KHa0r9rZJd7/MkDI9
LvQiKCQTroQOko0sPTgV
=zL/I
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] how to identify build options

[John R Pierce]

On 10/20/2014 8:38 AM, kqt4a...@gmail.com wrote:


What options were used to build this package? 


you'd need to look at the SRPM.



--
john r pierce  37N 122W
somewhere on the middle of the left coast

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] how to identify build options

[kqt4at5v]

If using the standard CentOS packages is there a way to print the options 
that were specified when the package was built? For example


# rpm -qi at
Name: at   Relocations: (not relocatable)
Version : 3.1.10Vendor: CentOS
Release : 44.el6_5.2Build Date: Tue 07 Oct 2014 
03:35:22 AM CDT
Install Date: Fri 17 Oct 2014 02:38:44 PM CDT  Build Host: 
c6b9.bsys.dev.centos.org
Group   : System Environment/DaemonsSource RPM: 
at-3.1.10-44.el6_5.2.src.rpm
Size: 86228License: GPLv2+
Signature   : RSA/SHA1, Tue 07 Oct 2014 07:57:22 AM CDT, Key ID 0946fca2c105b9de
Packager: CentOS BuildSystem 
URL : http://ftp.debian.org/debian/pool/main/a/at
Summary : Job spooling tools
Description :
At and batch read commands from standard input or from a specified
file. At allows you to specify that a command will be run at a
particular time. Batch will execute commands when the system load
levels drop to a particular level. Both commands use user's shell.

You should install the at package if you need a utility for
time-oriented job control. Note: If it is a recurring job that will
need to be repeated at the same time every day/week, etc. you should
use crontab instead.


What options were used to build this package?

Richard


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] rsync question: building list taking forever

[Les Mikesell]

On Sun, Oct 19, 2014 at 9:05 PM, Tim Dunphy  wrote:
>>
>> > Don't forget that the time taken to build the file list is a function of
>> > the number of files present, and not their size. If you have many
>> millions
>> > of small files, it will indeed take a very long time. Over sshfs with
>> > a slowish link, it could be days.
>> >
>> > and it may end up failing silently or noisily anyway.
>
>
> Ahhh, but isn't that part of the beauty of adventure that being a linux
> admin is all about? *twitch*

There's not that much magic involved.  The time it takes rsync to read
a directory tree to get started should approximate something like
'find /path -links +0"   (i.e. something that has to read the
directory tree and the associated inodes).Pre-3.0 rsync versions
read and transfer the whole thing before starting the comparison and
might trigger swapping if you are low on RAM.

So, you probably want the 'source' side of the transfer to be local
for faster startup. But... in what universe is NFS mounting across
data centers considered more secure than ssh?  Or even a reasonable
thing to do?  How about a VPN between the two hosts?

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] creating a floppy image from a linux file

[Les Mikesell]

On Mon, Oct 20, 2014 at 7:58 AM, Dan Hyatt  wrote:
> This is relatively unique. Cannot load a barebones OS because VMWares mouse
> does not map to the screen. So where the mouse pointer is pointing and the
> buttons are not mapped correctly making impossible.

Can't you resize the (virtual) console screen to match the geometry
the installer is detecting? Or, if you can bring the network up on the
guest, use the vnc install approach to control it from a remote
screen:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-vnc-installations-anaconda-modes.html

> As this is a production environment where we don't have any http servers
> under my control, it gets interesting.
> Normal blades are installed via PXE from the other groups pxe server, the
> other group is not being helpful at this time.

Do you have any other equipment available, like a desktop PC?   You
could create a VMware image under any version (like the free vmware
player) on any system that works.  Then use the vmware converter tool
to copy that image over to the system(s) where you want it to run.

If you really want a floppy image you should be able to use the mtools
package like:
mformat -C -f 1440 -v MYLABEL -i myfloppy.img
to create it, then
mcopy -i myfloppy.img  myfile  ::
to put your file on it.
See 'man mtools' for the details of using image files and ::

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] rsync question: building list taking forever

[Denniston, Todd A CIV NAVSURFWARCENDIV Crane]

> -Original Message-
> From: John Doe [mailto:jd...@yahoo.com]
> Sent: Monday, October 20, 2014 5:30 AM
> To: CentOS mailing list; Tim Dunphy
> Subject: Re: [CentOS] rsync question: building list taking forever
> 
> Are you "allowed" to temporarily run an ssh tunnel (or stunnel) on your 
> jumpbox?
> So connecting from host1 to jumpbox on port XXX would be tunneled to ssh port 
> on host2...
> 
> Or with netcat (if you can mkfifo)?
>   mkfifo backpipe
>   nc -l 12345 0backpipeBut you will have to trick 
> ssh into accepting your jumpbox "fingerprint"...
> 
> JD
> 

Or perhaps easier (depending on how paranoid sshd configs are) with 
ProxyCommand in ssh/config, i.e., setup config so one ssh command can get you 
logged onto the final target and then use rsync across ssh as per normal:

http://sshmenu.sourceforge.net/articles/transparent-mulithop.html

Then rsync will be running on both ends, where the data (filesystem 
information) is LOCAL, i.e., fast.

I would use, if possible/allowed,  key[s] with ssh(-agent) to make the whole 
connect to multiple hosts thing easier (i.e., fewer passphrase requests).

[OP: `they don't allow ssh between the datacenters` ...but... they nfs between 
them...??? ME: much head scratching.]

Even when this disclaimer is not here:
I am not a contracting officer. I do not have authority to make or modify the 
terms of any contract.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 5.11 / Firefox 31 -- totally borked...

[Stephen Harris]

On Mon, Oct 20, 2014 at 12:49:38PM +0100, Lars Hecking wrote:
> > http://people.centos.org/tru/firefox-31.2.0-3.el5.centos.bz1150082-32/

>  Sweet. Thanks Tru and Johnny!

Yay, also fixed my read RH5 32bit desktop at work :-)

Thanks!

-- 

rgds
Stephen
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] creating a floppy image from a linux file

[Dan Hyatt]

So back to the question...

If I unpack my iso image, and add a kickstart file, then I have to do 
this every change I make to the kickstart file.


But if I convert the kickstart file into a floppy image, then I don't 
need an iso image for every build..I just have tiny kickstart images.


So back to the question, do we know how to convert a kickstart file into 
a floppy image. This will solve the "unsupported" datastore problem.

On 10/17/2014 5:10 PM, SilverTip257 wrote:

On Fri, Oct 17, 2014 at 4:55 PM, Dan Hyatt  wrote:


Hi,

I am still trying to get kick-start centos in my vmware5 because pxe
cannot find the pxe server. I do not control the dhcp or pxe server.


Bummer.



I have both my kickstart file and my iso image for centos6.5 on my vmware
datastore, but am trying to run my kickstart file from VMware guest.


Include your ks file as part of your ISO image.



Can I tell the command line to run from the datastore in VMWare? Or must I
convert my kickstart file to a floppy image to run from VMware console?


The vmware datastore is not a supported medium for retrieving a kickstart
file (http and others are).

Include your ks as part of your ISO .. which means unpacking, add files,
and repacking the ISO.



I have the centos image on the DVD mounted from my datastore.  Now I need
to convert the kickstart file to a floppy image to mount on the server from
my datastore


This is what google and VMWare keeps telling me but it does not make sense
unless I am copying off a floppy
What I am trying to do is turn the kickstart file into a floppy image so I
can kickstart off the floppy in vmware.

Create a disk image from the physical drive:
cat /dev/fd0 > imagefile.img

Copy image to the physical drive:
cat imagefile.img > /dev/fd0

Help figuring out that silly little piece that is keeping me from building
a VM guest from my kickstart file is much appreciated.



* And John Pierce's suggestion to create your own PXE virtual network is a
flexible and more ideal scenario in my opinion.



___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] creating a floppy image from a linux file

[Dan Hyatt]

My chicken and egg.

I was hoping to
1. create a baseline image that I can clone
2. get a centos image on a VM guest, have my own management servers 
(including pxe boot) that I own and control.



Once I have one or two, I can expand my private cloud as large as I 
want...and building new guest servers will take minutes.


On 10/17/2014 5:06 PM, John R Pierce wrote:

On 10/17/2014 1:55 PM, Dan Hyatt wrote:
I am still trying to get kick-start centos in my vmware5 because pxe 
cannot find the pxe server. I do not control the dhcp or pxe server. 


this is on ESXI?   you /could/ create a virtual network thats not 
routed or bridged to your actual networks, then create your own 
PXE/DHCP server on this virtual network, and then connect your new VM 
to that private virtual net for installation, switching it over to the 
regular networks when its done installingI've done crazier 
things on ESXI :)






___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] creating a floppy image from a linux file

[Dan Hyatt]

This is relatively unique. Cannot load a barebones OS because VMWares 
mouse does not map to the screen. So where the mouse pointer is pointing 
and the buttons are not mapped correctly making impossible. Since it is 
not a physical server, I don't have the USB. But VMWare will allow me to 
"mount" a virtual floppy. So if I can create a floppy image of my 
kickstart file, I can kickstart my virtual iso image.


A datastore is a filesystem on a virtual server exported to the virtual 
guests.
Because this is a blade, there is no usb or DVD physically connected.  I 
can virtually mount a floppy and dvd from a floppy image and a dvd image.


As this is a production environment where we don't have any http servers 
under my control, it gets interesting.
Normal blades are installed via PXE from the other groups pxe server, 
the other group is not being helpful at this time.



On 10/17/2014 4:20 PM, Valeri Galtsev wrote:

On Fri, October 17, 2014 3:55 pm, Dan Hyatt wrote:

Hi,

I am still trying to get kick-start centos in my vmware5 because pxe
cannot find the pxe server. I do not control the dhcp or pxe server.
I have both my kickstart file and my iso image for centos6.5 on my
vmware datastore, but am trying to run my kickstart file from VMware
guest.

Can I tell the command line to run from the datastore in VMWare? Or must
I convert my kickstart file to a floppy image to run from VMware console?

I hope I didn't miss something (as I have no idea what "datastore in
VMWare" means). When I install system on real machine or on virtual box
virtual machine, I use kickstart that I place on some webserver, then if I
don't have access to dhcp configuration, then I boot the box off any
installation media, and before it load kernel (when it gives you choice
run system off CD or install system) I press "escape". At this moment you
have access to which kernel and with which options you want to boot. So I
just point it to my kickstart file as follows:

linux ks=http://my.server.com/path/to/kickstart.cfg

(replace the URL with URL of your kickstart file).
Also, in kicstart I just give the URL of our public mirror I support for
our University. E.g. as URL of installation media for 64 CentOS 7 I have
the following line in kickstart file:

url --url=http://bay.uchicago.edu/centos/7/os/x86_64

I hope, this helps.

Valeri


I have the centos image on the DVD mounted from my datastore.  Now I
need to convert the kickstart file to a floppy image to mount on the
server from my datastore


This is what google and VMWare keeps telling me but it does not make
sense unless I am copying off a floppy
What I am trying to do is turn the kickstart file into a floppy image so
I can kickstart off the floppy in vmware.

Create a disk image from the physical drive:
cat /dev/fd0 > imagefile.img

Copy image to the physical drive:
cat imagefile.img > /dev/fd0

Help figuring out that silly little piece that is keeping me from
building a VM guest from my kickstart file is much appreciated.

Dan


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos




Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] djbdns under CentOS7: startup and socket issues

[James Hogarth]

On 20 Oct 2014 12:41, "Boris Epstein"  wrote:
>
> sshd is not a telnetd-type servide yet it uses a .socket file. So I
thought
> djbdns should as well.
>

It can be run that way as an option:

http://0pointer.de/blog/projects/inetd.html

> As for why DJBDNS - we have used it for a long time due to the security
> advantages. And yes, BIND is now much better than it used to be and we may
> switch to it at some point but for now we are still trying to get DJBDNS
to
> work.
>

If you are using the 1.05 tar from the djb site this is a very bad idea -
see previous links for reasons.

> I am close - when I start it manually and when I use it locally. So all I
> need to do is figure out how to start it automatically as well as how to
> open the necessary ports in the firewall.
>

The correct answer here to ease your maintenance burden if you insist in
djbdns is to use the ndjbdns package in epel that has already been
mentioned.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] CESA-2014:1652 Important CentOS 6 openssl Security Update

[David Hrbáč]

Dne 20.10.2014 v 12:55 Johnny Hughes napsal(a):
> Well, this one is a 'one off' as it really has no upstream
> counterpart. It also has notes that the other announcements do not,
> etc. As a 'one off', the format was taken from the Xen4CentOS type
> announcements. The normal distro announcements will continue as they
> were before. Thanks, Johnny Hughes

Thanks,
DH
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 5.11 / Firefox 31 -- totally borked...

[Lars Hecking]

> try these in the interim:
> 
> http://people.centos.org/tru/firefox-31.2.0-3.el5.centos.bz1150082-32/
> 
> http://people.centos.org/tru/firefox-31.2.0-3.el5.centos.bz1150082-64/
> 
> Thanks Tru !

 Sweet. Thanks Tru and Johnny!

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] djbdns under CentOS7: startup and socket issues

[Boris Epstein]

On Fri, Oct 17, 2014 at 6:49 PM, James Hogarth 
wrote:

> On 17 Oct 2014 23:32, "Boris Epstein"  wrote:
> >
> > Hello all,
> >
> > I am trying to get djbdns ( http://en.wikipedia.org/wiki/Djbdns )
> running
> > on CentOS 7. So far I have wirtten the djbdns.service and djbdns.socket
> > files. The sockets (TCP and UDP 53) for some reason would not start and I
> > don't know how to debug that;
>
> I was under the impression it used daemontools and listened directly on the
> ports rather than an inetd style behaviour of being triggered and having
> the connection handed to it like socket based behaviour would require... It
> seems unlikely you'd need a socket unit.
>
> > the service does start but only when I start
> > it manually by running
> >
> > systemctl start djbdns
> >
>
> This strongly indicates you don't need the socket as socket based services
> are not stated by calling start on their service file.
>
> You will need to add a wantedby multi-user.target to the [install] part of
> that service file and then call systemctl enable djbdns
>
> > So, I am a real noob when it comes to systemd, hence any advice on how to
> > proceed will be much appreciated.
> >
>
> I'd ask why you want to use djbdns rather than the DNS server provided by
> the CentOS distribution. If security is your concern then SELinux confined
> bind (in a chroot as well if you like) is supported directly by the
> distribution packages so you can be sure of updates and this list plus the
> IRC channel can support that - unlike your custom compiled djbdns.
>
> If you wanted to be extremely paranoid you could configure the systemd unit
> for BIND to hide all but a select number of directories too... Which is
> technically more powerful than the chroot as it makes use of kernel
> namespaces.
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>


James,

Good points.

sshd is not a telnetd-type servide yet it uses a .socket file. So I thought
djbdns should as well.

As for why DJBDNS - we have used it for a long time due to the security
advantages. And yes, BIND is now much better than it used to be and we may
switch to it at some point but for now we are still trying to get DJBDNS to
work.

I am close - when I start it manually and when I use it locally. So all I
need to do is figure out how to start it automatically as well as how to
open the necessary ports in the firewall.

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] CESA-2014:1652 Important CentOS 6 openssl Security Update

[Johnny Hughes]

On 10/20/2014 04:20 AM, David Hrbáč wrote:
> Hi,
> 
> This announcement has different body scheme than the rest of
> announcement messages. Is it a new scheme? It breaks the importing
> scripts...
> 
> Thanks,
> DH
>

Well, this one is a 'one off' as it really has no upstream counterpart.
 It also has notes that the other announcements do not, etc.  As a 'one
off', the format was taken from the Xen4CentOS type announcements.

The normal distro announcements will continue as they were before.

Thanks,
Johnny Hughes


> Dne 16.10.2014 v 22:48 Johnny Hughes napsal(a):
>> CentOS Errata and Security Advisory 2014:1652 
>>
>> The following updated files have been uploaded and are currently
>> syncing to the mirrors: ( sha256sum Filename )
>>
>> -
>> i386
>> -
>>
>> 5898ac3179dfdd904c352badd79b6f5ec702315f4bc7b8989de8f114304fbd78 
>> openssl-1.0.1e-30.el6_5.2.i686.rpm
>> dcc5d47340d69f53af592a92282df89ef3bd4705ce34f4a57a93d211e93cfd7d 
>> openssl-devel-1.0.1e-30.el6_5.2.i686.rpm
>> dc42eb136b3cfef78d590d4ab29d36e5e5951bc9433d20d5ca633033d960a00d 
>> openssl-perl-1.0.1e-30.el6_5.2.i686.rpm
>> 95e67f00f7d58348e5f0df6ac74d7baecb9d5fc214d58ad257a14bec353219a3 
>> openssl-static-1.0.1e-30.el6_5.2.i686.rpm
>>
>> -
>> X86_64
>> -
>>
>> 5898ac3179dfdd904c352badd79b6f5ec702315f4bc7b8989de8f114304fbd78 
>> openssl-1.0.1e-30.el6_5.2.i686.rpm
>> 17bfdb52afcb2ebaa16875819b9d8d2f3dc84eb061ee3e194da14e286bc76029 
>> openssl-1.0.1e-30.el6_5.2.x86_64.rpm
>> dcc5d47340d69f53af592a92282df89ef3bd4705ce34f4a57a93d211e93cfd7d 
>> openssl-devel-1.0.1e-30.el6_5.2.i686.rpm
>> 7c390aab888c07887fc783686f42216711665738e58c2b23029748292dd0f96d 
>> openssl-devel-1.0.1e-30.el6_5.2.x86_64.rpm
>> dfdcf88163743d5f4fda06a69cba00b822b73ba66aa5841faf8c0e9841b91bcb 
>> openssl-perl-1.0.1e-30.el6_5.2.x86_64.rpm
>> 0f8cc0615d96d4d7e74b5ffc109143873510406dbb6be679d4ab94bd4f731cdb 
>> openssl-static-1.0.1e-30.el6_5.2.x86_64.rpm
>>
>> -
>> Source:
>> -
>>
>> 1a1c3ed0d8eb5775d89b726e7f19ff2d8b52b7ef27f6e36260e83ffc40328460 
>> openssl-1.0.1e-30.el6_5.2.src.rpm
>>
>> =
>>
>> The following upstream security issues are addressed in this update:
>>
>> https://rhn.redhat.com/errata/RHSA-2014-1652.html
>>
>> =
>>
>> NOTE: This update is released into the CentOS-6.5 tree and has a .el6_5 dist
>> tag, *NOT* the .el6_6 dist tag that Red Hat used for RHEL in the link above.
>>
>> This update was built against 'CentOS-6.5 + updates' and that is where it is
>> intended to be used.
>>
>> The CentOS team will build and release a openssl-1.0.1e-30.el6_6.2.src.rpm as
>> a zero day update to CentOS-6.6 when that is released as we are currently
>> building CentOS-6.6 from the released Red Hat Enterprise Linux sources.
>>
>> Please also note that even after installing this update, further action is
>> required to mitigate the POODLE issue on CentOS-6. Please see this link for
>> steps to take and ways to test for both the POODLE and TLS_FALLBACK_SCSV 
>> issues.
>>
>> http://wiki.centos.org/Security/POODLE
>>
>> --
>> Johnny Hughes
>> CentOS Project { http://www.centos.org/ }
>> irc: hughesjr, #centos at irc.freenode.net





signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] rsync question: building list taking forever

[John Doe]

Are you "allowed" to temporarily run an ssh tunnel (or stunnel) on your jumpbox?
So connecting from host1 to jumpbox on port XXX would be tunneled to ssh port 
on host2...

Or with netcat (if you can mkfifo)?
  mkfifo backpipe
  nc -l 12345 0backpipeBut you will have to trick ssh 
into accepting your jumpbox "fingerprint"...

JD

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] CESA-2014:1652 Important CentOS 6 openssl Security Update

[David Hrbáč]

Hi,

This announcement has different body scheme than the rest of
announcement messages. Is it a new scheme? It breaks the importing
scripts...

Thanks,
DH

Dne 16.10.2014 v 22:48 Johnny Hughes napsal(a):
> CentOS Errata and Security Advisory 2014:1652 
>
> The following updated files have been uploaded and are currently
> syncing to the mirrors: ( sha256sum Filename )
>
> -
> i386
> -
>
> 5898ac3179dfdd904c352badd79b6f5ec702315f4bc7b8989de8f114304fbd78 
> openssl-1.0.1e-30.el6_5.2.i686.rpm
> dcc5d47340d69f53af592a92282df89ef3bd4705ce34f4a57a93d211e93cfd7d 
> openssl-devel-1.0.1e-30.el6_5.2.i686.rpm
> dc42eb136b3cfef78d590d4ab29d36e5e5951bc9433d20d5ca633033d960a00d 
> openssl-perl-1.0.1e-30.el6_5.2.i686.rpm
> 95e67f00f7d58348e5f0df6ac74d7baecb9d5fc214d58ad257a14bec353219a3 
> openssl-static-1.0.1e-30.el6_5.2.i686.rpm
>
> -
> X86_64
> -
>
> 5898ac3179dfdd904c352badd79b6f5ec702315f4bc7b8989de8f114304fbd78 
> openssl-1.0.1e-30.el6_5.2.i686.rpm
> 17bfdb52afcb2ebaa16875819b9d8d2f3dc84eb061ee3e194da14e286bc76029 
> openssl-1.0.1e-30.el6_5.2.x86_64.rpm
> dcc5d47340d69f53af592a92282df89ef3bd4705ce34f4a57a93d211e93cfd7d 
> openssl-devel-1.0.1e-30.el6_5.2.i686.rpm
> 7c390aab888c07887fc783686f42216711665738e58c2b23029748292dd0f96d 
> openssl-devel-1.0.1e-30.el6_5.2.x86_64.rpm
> dfdcf88163743d5f4fda06a69cba00b822b73ba66aa5841faf8c0e9841b91bcb 
> openssl-perl-1.0.1e-30.el6_5.2.x86_64.rpm
> 0f8cc0615d96d4d7e74b5ffc109143873510406dbb6be679d4ab94bd4f731cdb 
> openssl-static-1.0.1e-30.el6_5.2.x86_64.rpm
>
> -
> Source:
> -
>
> 1a1c3ed0d8eb5775d89b726e7f19ff2d8b52b7ef27f6e36260e83ffc40328460 
> openssl-1.0.1e-30.el6_5.2.src.rpm
>
> =
>
> The following upstream security issues are addressed in this update:
>
> https://rhn.redhat.com/errata/RHSA-2014-1652.html
>
> =
>
> NOTE: This update is released into the CentOS-6.5 tree and has a .el6_5 dist
> tag, *NOT* the .el6_6 dist tag that Red Hat used for RHEL in the link above.
>
> This update was built against 'CentOS-6.5 + updates' and that is where it is
> intended to be used.
>
> The CentOS team will build and release a openssl-1.0.1e-30.el6_6.2.src.rpm as
> a zero day update to CentOS-6.6 when that is released as we are currently
> building CentOS-6.6 from the released Red Hat Enterprise Linux sources.
>
> Please also note that even after installing this update, further action is
> required to mitigate the POODLE issue on CentOS-6. Please see this link for
> steps to take and ways to test for both the POODLE and TLS_FALLBACK_SCSV 
> issues.
>
> http://wiki.centos.org/Security/POODLE
>
> --
> Johnny Hughes
> CentOS Project { http://www.centos.org/ }
> irc: hughesjr, #centos at irc.freenode.net
>
> ___
> CentOS-announce mailing list
> centos-annou...@centos.org
> http://lists.centos.org/mailman/listinfo/centos-announce

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos