Re: [CentOS] Centos7 kickstart & pxe
- Original Message - From: "John Hodrien" To: "CentOS mailing list" Sent: Thursday, August 18, 2016 4:47:09 PM Subject: Re: [CentOS] Centos7 kickstart & pxe On Thu, 18 Aug 2016, johan.vermeul...@telenet.be wrote: > Hello All, > > I'm trying to get kickstart to work through pxe. > So far I've set up dhcp server, tftp and so on. > But it seems at some point I always get stuck because the iso file is > write-protected. > > I've tried remounting it rw, and I 've dd the iso first, I then get EM not a > block device. I'd always tend to just expose the install image via HTTP. jh Hello John, thanks for the reply. I found a useful tutorial on kickstart/http here: http://www.tomsitpro.com/articles/kickstart-linux-automation,2-798.html but if I understand it right, via http is not an unattended install. You have to have a boot medium. If I'm correct people do unattended installs all the time, so I don't understand why all the tutorials I try fail on the same point. I must be doing something wrong. What I did on my last try was: Download Centos dvd to /tmp mount -o loop /path/to/centos-dvd.iso /mnt rsync -azvp /mnt/* /var/ftp/pub/ But subsequently I can't change anything in /var/ftp/pub because of read-only file system. Greetings, J. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS-announce Digest, Vol 138, Issue 6
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org
You can reach the person managing the list at
centos-announce-ow...@centos.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."
Today's Topics:
1. CESA-2016:1626 Moderate CentOS 7 python Security Update
(Johnny Hughes)
2. CESA-2016:1626 Moderate CentOS 6 python Security Update
(Johnny Hughes)
--
Message: 1
Date: Thu, 18 Aug 2016 17:23:01 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2016:1626 Moderate CentOS 7 python
SecurityUpdate
Message-ID: <20160818172301.ga16...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2016:1626 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1626.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
4580fa3bd63f62fcb02e491b1ab0952f5c11d56dac42295d3f7917818790c28d
python-2.7.5-38.el7_2.x86_64.rpm
d65cd5414f4167267a8305c43b9828a19d6c0f02c4b9b046bcbc4ebfb9d898b9
python-debug-2.7.5-38.el7_2.x86_64.rpm
1d846ef07419a41e66c2423f07063dfc498f595bc8077bac36af8d3204a3e3fa
python-devel-2.7.5-38.el7_2.x86_64.rpm
4225681bbc8bdc0a24dba05f6edd0b7536448a7d062a9ef0f921501c8bf3757e
python-libs-2.7.5-38.el7_2.i686.rpm
de6d8600d0d9a36c1cb22b6968224612ad7a06354d9cbd33da4bec17554837fe
python-libs-2.7.5-38.el7_2.x86_64.rpm
01c3fecdcab99e8f853adcde3fb2080468c2eff91c5e29906a143541d494f4df
python-test-2.7.5-38.el7_2.x86_64.rpm
ca3d26aa3f2a10f399ab2f26577054fc0c443b099e2bbfba1b6d4785a4fce3f9
python-tools-2.7.5-38.el7_2.x86_64.rpm
95c26c4e3a57926bc59e80e8f2707011c5000a6a0d47875e823a4126cf15ea6b
tkinter-2.7.5-38.el7_2.x86_64.rpm
Source:
4470b36c08ba660c4317b4211b6aa2207288d4a9f438a998b92be3d62a958def
python-2.7.5-38.el7_2.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
--
Message: 2
Date: Thu, 18 Aug 2016 17:23:23 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2016:1626 Moderate CentOS 6 python
SecurityUpdate
Message-ID: <20160818172323.ga16...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2016:1626 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1626.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
d434ddba7ca4db22fb0a430f43961ecda1394f8e0c0c799855acf448a056b2f4
python-2.6.6-66.el6_8.i686.rpm
73a0c8b071682ee7cf2f44d1779ffc3302ad639fffe6ef3e528c887af609058b
python-devel-2.6.6-66.el6_8.i686.rpm
48e1c9e73faeeed24011487a75915cdd67cdbdd0fb3aadfa6ea2a690220e6e0f
python-libs-2.6.6-66.el6_8.i686.rpm
fdfc3b56a5caa9bcf8b58737caa7337daf49532fca8a1e62e7c5f1edfcab0c91
python-test-2.6.6-66.el6_8.i686.rpm
069495e99bfd46b657c8622274cb0aca1921b374df5e43ec8ef7f88052b504c0
python-tools-2.6.6-66.el6_8.i686.rpm
6d267b6e09719e7cd17e7b05e736a4272f14d62dc3162616c65840a80bd90847
tkinter-2.6.6-66.el6_8.i686.rpm
x86_64:
53c75a1756e5b4f6564c5229a37948c9b4561e0bf58076bd7dab7aff85a417f2
python-2.6.6-66.el6_8.x86_64.rpm
73a0c8b071682ee7cf2f44d1779ffc3302ad639fffe6ef3e528c887af609058b
python-devel-2.6.6-66.el6_8.i686.rpm
5c9d6761d8d896b93ed92caa1ec61045aa1847c32d6cf860c2b4959b49d9de80
python-devel-2.6.6-66.el6_8.x86_64.rpm
48e1c9e73faeeed24011487a75915cdd67cdbdd0fb3aadfa6ea2a690220e6e0f
python-libs-2.6.6-66.el6_8.i686.rpm
ae6a523f79928c4fdb8c7d62f07279883b20b8b89d8703cb91030201c54e25e9
python-libs-2.6.6-66.el6_8.x86_64.rpm
61116f6ad9f288b23d0fd63fa2252ffd2fdc53e978a358aebda1654453145d4c
python-test-2.6.6-66.el6_8.x86_64.rpm
a88d7d03b236ac4938be140c230d2d8d645a82a39bcf647c7d5d55bc27106192
python-tools-2.6.6-66.el6_8.x86_64.rpm
7eb7c048610b47fd5c7918e5f12038c3869fe90f4a24d604fbc70a6220d460c2
tkinter-2.6.6-66.el6_8.x86_64.rpm
Source:
b56fb033143cf700283ef68914a9cec31a1f8a045e6849c3c1afd2e08d7a2b56
python-2.6.6-66.el6_8.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
--
___
CentOS-announce mailing list
centos-annou...@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
End of CentOS-announce Digest, Vol 138, Issue 6
***
___
[CentOS] explain strange behavior
In my bin directory, most of the binaries are linked to it. It is in my path. I have googled this and cannot find anything close. I am running bash on centos6.8 When I run "which command" most of the files in this custom bin directory show up. When I run "which file.jar" it cannot see it, but I can *ls* the file (soft link) as which only works on executables (according to man page), I created a dan.jar empty file and did a which on dan.tar and found it. can anyone explain what is happening and how I can soft link the jar files to my bin directory so which can see them? Dan ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] explain strange behavior
On 8/19/2016 11:12 AM, Dan Hyatt wrote: In my bin directory, most of the binaries are linked to it. It is in my path. I have googled this and cannot find anything close. I am running bash on centos6.8 When I run "which command" most of the files in this custom bin directory show up. When I run "which file.jar" it cannot see it, but I can *ls* the file (soft link) as which only works on executables (according to man page), I created a dan.jar empty file and did a which on dan.tar and found it. can anyone explain what is happening and how I can soft link the jar files to my bin directory so which can see them? `which` will only show files that have chmod +x set and are in the path. jar files aren't directly executable by the shell, you have to run java -jar name.jar to execute them, so there's no point in having them in the path or +x. -- john r pierce, recycling bits in santa cruz ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] explain strange behavior
On Fri, August 19, 2016 1:12 pm, Dan Hyatt wrote: > In my bin directory, most of the binaries are linked to it. It is in my > path. I have googled this and cannot find anything close. > > I am running bash on centos6.8 > > When I run "which command" most of the files in this custom bin > directory show up. > > When I run "which file.jar" it cannot see it, but I can *ls* the file > (soft link) Do these files that are not shown by which command have "execute" bit on for everyboty (in other words, can regular user executing the command "which" execute that file, and read that file: what is set in UNIX permissions for that file. Showing us what ls -l /usr/local/bin/file.jar (if it is symlink, show us permission of actual file symlink points to) Valeri > > as which only works on executables (according to man page), I created a > dan.jar empty file and did a which on dan.tar and found it. > > > can anyone explain what is happening and how I can soft link the jar > files to my bin directory so which can see them? > > Dan > > > > ___ > CentOS mailing list > CentOS@centos.org > https://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 https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] explain strange behavior
On Fri, Aug 19, 2016 at 01:12:57PM -0500, Dan Hyatt wrote:
> In my bin directory, most of the binaries are linked to it. It is in my
> path. I have googled this and cannot find anything close.
>
> I am running bash on centos6.8
>
> When I run "which command" most of the files in this custom bin directory
> show up.
>
> When I run "which file.jar" it cannot see it, but I can *ls* the file (soft
> link)
>
> as which only works on executables (according to man page), I created a
> dan.jar empty file and did a which on dan.tar and found it.
>
>
> can anyone explain what is happening and how I can soft link the jar files
> to my bin directory so which can see them?
>
I don't use java, so this may be way off base.
I'm assuming you have several *.jar files, but will work with two,
foo.jar and bar.jar.
Place all your jar files in a single directory, not bin. Under lib
is the common place. I'll use /home/dan/lib/jarfiles.
In your bin directory place a shell script named "foo" containing
something like this:
#!/usr/bin/bash
ProgName=${0##*/} # (basename) strips dirs from path
JarDir=/home/dan/lib/jarfiles
JarFile=${JarDir}/${ProgName}.jar
## possibly test for existance of jar file
java -jar ${JarFile} "${@}"# I assume there may be args to pass.
That would let you run foo.jar as "foo" and do a "which foo" as it is
an executable shell script.
For bar.jar you merely need to put it in the JarDir and make a link
in the bin directory:
ln /home/dan/bin/foo /home/dan/bin/bar
Do the same for each *.jar, move to JarDir, make a link.
If particular jar files need special treatment you can put a switch
statement in the script based on $ProgName.
Jon
--
Jon H. LaBadie j...@jgcomp.com
11226 South Shore Rd. (703) 787-0688 (H)
Reston, VA 20190 (703) 935-6720 (C)
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] GRUB 2 dumps to grub prompt when installed on >4TB disk
- Original Message - | On Thu, Aug 18, 2016 at 11:57 AM, James A. Peltier wrote: | > Hi All, | > | > I have a Dell R710 that has 6x1TB in a RAID-5 configuration. | | | This is hardware RAID 5? Because it's pretty screwy how this ends up | working when using software RAID and might take additional | troubleshooting. Yes, it's a Dell R710XD | > When installing CentOS 7 using the full disk capacity and booting in UEFI | > mode the machine dumps me into a GRUB rescue mode prompt. | > error: disk `,gpt2' not found | > Entering rescue mode... | > grub rescue> | | | This is confusing to me because there should be no such thing as grub | rescue on UEFI. On BIOS systems, there is boot.img (formerly stage 1) | and core.img in the MBR gap or on BIOS Boot if GPT disk (formerly | stage 1.5 and stage 2). The core.img is where grub rescue comes from | when it can't find grub modules, in particular normal.mod. | | But on UEFI, core.img, normal.mod, and a pile of other modules are all | baked into the grubx64.efi file founds on the EFI system partition. | | I suspect two things that can cause normal.mod to not be found: | a. The system is not in fact booting in UEFI mode and there's been | some mistake in the installation of grub. | b. The system is in UEFI mode, but either the installer, or | post-install, grub2-install was run which obliterates the grub2-efi | package installed grubx64.efi, i.e. it's not really proper to run | grub2-install on UEFI systems. I suspect this is the case. when attempting to run grub-install the system claims that the grub2-efi-modules packages aren't installed, so this may be an installer bug. | Boot off install media with boot parameter inst.rescue and choose all | the default options; this ought to assemble the file system per fstab, | and you can | | chroot /mnt/sysimage | yum reinstall grub2-efi | efibootmgr -v | grep efibootmgr /var/log/anaconda/program.log ## I think that's | right it might be anaconda.program.log though | | | It's really just reinstalling grub2-efi that should fix the problem, | the following two options are just information gathering in case the | reboot still doesn't work. We'll try this and get back to you soon. -- James A. Peltier IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 604-365-6432 Fax : 778-782-3045 E-Mail : jpelt...@sfu.ca Website : http://www.sfu.ca/itservices Twitter : @sfu_rcg Powering Engagement Through Technology ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos7 kickstart & pxe
- Original Message - | | | - Original Message - | From: "John Hodrien" | To: "CentOS mailing list" | Sent: Thursday, August 18, 2016 4:47:09 PM | Subject: Re: [CentOS] Centos7 kickstart & pxe | | On Thu, 18 Aug 2016, johan.vermeul...@telenet.be wrote: | | > Hello All, | > | > I'm trying to get kickstart to work through pxe. | > So far I've set up dhcp server, tftp and so on. | > But it seems at some point I always get stuck because the iso file is | > write-protected. | > | > I've tried remounting it rw, and I 've dd the iso first, I then get EM not | > a block device. | | I'd always tend to just expose the install image via HTTP. | | jh | | Hello John, | | thanks for the reply. | I found a useful tutorial on kickstart/http here: | http://www.tomsitpro.com/articles/kickstart-linux-automation,2-798.html | but if I understand it right, via http is not an unattended install. You have | to have a boot medium. | | If I'm correct people do unattended installs all the time, so I don't | understand why all the tutorials I try fail on the same point. | I must be doing something wrong. | | What I did on my last try was: | | Download Centos dvd to /tmp | mount -o loop /path/to/centos-dvd.iso /mnt | rsync -azvp /mnt/* /var/ftp/pub/ | | But subsequently I can't change anything in /var/ftp/pub because of read-only | file system. | | Greetings, J. Basically in order to boot from the network you need the contents of os/$arch/images/pxeboot/ for your system architecture. You can then use kickstart to point to a media you want to use for the actual installation. This can be that of cdrom, url, nfs, etc. You pass the kickstart parameter to your client using the 'ks=' parameter. the installation media can be from a local rsync of the CentOS repository (to save money) or to a mirror of your choice that may be local to you. Feel free to ask any questions. -- James A. Peltier IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 604-365-6432 Fax : 778-782-3045 E-Mail : jpelt...@sfu.ca Website : http://www.sfu.ca/itservices Twitter : @sfu_rcg Powering Engagement Through Technology ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Kickstart issue with UEFi
Hi, I have a test system that booted fine using "Legacy Bios” mode and using the following Kickstart snippet configured the disks correctly:- # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel # Disk partitioning information part raid.01 --fstype="raid" --ondisk=sda --size=500 part raid.02 --fstype="raid" --grow --ondisk=sda --size=1 part raid.03 --fstype="raid" --ondisk=sdb --size=500 part raid.04 --fstype="raid" --grow --ondisk=sdb --size=1 raid /boot --device=0 --fstype="xfs" --level=RAID1 raid.01 raid.03 raid pv.01 --device=1 --level=RAID1 raid.02 raid.04 For UEFi I changed it to the following:- # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel # Disk partitioning information part raid.01 --fstype="raid" --ondisk=sda --size=500 part raid.02 --fstype="raid" --grow --ondisk=sda --size=1 part raid.03 --fstype="raid" --ondisk=sdb --size=500 part raid.04 --fstype="raid" --grow --ondisk=sdb --size=1 raid /boot --device=0 --fstype="xfs" --level=RAID1 raid.01 raid.03 part /boot/efi —fstype=“efi” --grow --maxsize=200 --size=20 raid pv.01 --device=1 --level=RAID1 raid.02 raid.04 The install fails under UEFi due to the fact the partitions are not cleared, and it doesn’t have any space to continue. Is there an extra step I need to do to remove the original partitions before the new layout will work ? Thanks ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
