Re: [CentOS] Kickstarting CentOS 7 VM on CentOS 6 not possible?

[Gordon Messmer]

On 11/23/2015 12:59 AM, Jos Vos wrote:

I use virt-install with a local copy of the
"images/pxeboot" tree.


Does your tree also include the LiveOS structure (the stage2 installer)?


Installing CentOS 7 "manually" using virt-install and the netboot ISO
works fine, but I want to use kickstart files.


Using a local install tree isn't required for kickstart.  You can 
specify the location of the KS file as a boot arg and also use the ISO 
installer.

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

Re: [CentOS] Kickstarting CentOS 7 VM on CentOS 6 not possible?

[Jos Vos]

On Mon, Nov 23, 2015 at 11:16:50AM -0800, Gordon Messmer wrote:

> Does your tree also include the LiveOS structure (the stage2 installer)?

Yep.  In fact, I tried it with and without that LiveOS/squashfs.img
(I was not sure if that was required or just a speed-up).

> Using a local install tree isn't required for kickstart.  You can 
> specify the location of the KS file as a boot arg and also use the ISO 
> installer.

But how can the VM then access the kickstart file on the host disk?
Now it is injected in the initrd with that special flag, or can that
be done in combination with the ISO too?

-- 
--Jos Vos 
--X/OS Experts in Open Systems BV   |   Phone: +31 20 6938364
--Amsterdam, The Netherlands| Fax: +31 20 6948204
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Kickstarting CentOS 7 VM on CentOS 6 not possible?

[Jos Vos]

Hi,

On CentOS 6.7 (all updates) kickstarting a CentOS 7 VM (in the way it
always has worked for other versions, incl. Fedora 22 VM's), does not
work for me.  I use virt-install with a local copy of the
"images/pxeboot" tree.  It all stops with:

...
[  OK  ] Reached target Paths.
[  OK  ] Reached target Basic System.
dracut-initqueue[551]: Warning: Could not boot.
dracut-initqueue[551]: Warning: /dev/root does not exist
 Starting Dracut Emergency Shell...
Warning: /dev/root does not exist
...

I found zillion references to similar problems, including PXE-related
(I do not use PXE, but "-l" with virt-install) and cobbler-related
(no Cobbler involved), and I tried some of the suggestions, but none
of them worked.

Installing CentOS 7 "manually" using virt-install and the netboot ISO
works fine, but I want to use kickstart files.

Thanks for any suggestion.

-- 
--Jos Vos 
--X/OS Experts in Open Systems BV   |   Phone: +31 20 6938364
--Amsterdam, The Netherlands| Fax: +31 20 6948204
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Selling DVD image which include CentOS and our application

[Takuya Yamamoto]

Dear ALL

Our company make and sell some measurement system controlled by Server.
There is no technical issue but we don't have enough information about license.

We will do the following,

1) We make the DVD image which include CentOS and our application.
2) Sell DVD to our customer.
3) Customer installs this image (CentOS and our applications) on the Server.

Question 1
Is there no problem from the view point of CentOS license?

Question 2
We'd like to know what we should do to CentOS community?
e.g. contract, donate

I read following past ML
https://lists.centos.org/pipermail/centos/2010-June/096074.html
But, I want to know latest your comment.


br
---
Yamamoto Takuya
NEC Platforms, Ltd.

NEC Platforms, Ltd. Confidential


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

Re: [CentOS] Selling DVD image which include CentOS and our application

[Fabian Arrotin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 24/11/15 07:17, Takuya Yamamoto wrote:
> Dear ALL
> 
> Our company make and sell some measurement system controlled by
> Server. There is no technical issue but we don't have enough
> information about license.
> 
> We will do the following,
> 
> 1) We make the DVD image which include CentOS and our application. 
> 2) Sell DVD to our customer. 3) Customer installs this image
> (CentOS and our applications) on the Server.
> 
> Question 1 Is there no problem from the view point of CentOS
> license?
> 
> Question 2 We'd like to know what we should do to CentOS
> community? e.g. contract, donate
> 
> I read following past ML 
> https://lists.centos.org/pipermail/centos/2010-June/096074.html 
> But, I want to know latest your comment.
> 
> 
> br --- Yamamoto Takuya NEC Platforms, Ltd.
> 
> NEC Platforms, Ltd. Confidential
> 

Main website and wiki can have some informations around this  :
- - https://www.centos.org/legal/trademarks/
- - https://wiki.centos.org/Donate

- -- 
Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlZUBscACgkQnVkHo1a+xU45IQCglQpb2lBwvO8Mk4idL+tH+zvB
09wAoJZJ4biflNoqSUIPAimDs/vxHf10
=Lg0O
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Kernel route table is empty

[Siva Prasad Nath]

I can add using ifconfig and route.
Then I can see kernel route entry table.
I reboot system. Then route table is empty.

How to make kernel route entry table permanent.


-- 

Shiva Prasad Nath
92981134
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Kernel route table is empty

[Frank Cox]

On Tue, 24 Nov 2015 15:13:33 +0800
Siva Prasad Nath wrote:

> I can add using ifconfig and route.
> Then I can see kernel route entry table.
> I reboot system. Then route table is empty.
> 
> How to make kernel route entry table permanent.

Create a file in /etc/sysconfig/network-scripts named route-(ifname)

See section 2.4.4 of the RHEL 7 networking guide here for complete details:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Using_the_Command_Line_Interface.html#sec-Static-Routes_and_the_Default_Gateway

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Virtual Server in Windows 7

[Siva Prasad Nath]

Brand new one i7.

On Tuesday, November 24, 2015, Arun Khan  wrote:

> On Mon, Nov 23, 2015 at 9:17 PM, Siva Prasad Nath
> > wrote:
> > Hi,
> > I am creating a virtual machine. My laptop is i686 system.
>
> How old is your hardware?  I have a 6 year old Toshiba that came with
> a core i5  64 bit CPU.
>
> > Please advice me which Centos verson can be downloaded?
>
> If your hardware is indeed 32 bit then download the CentOS 6.7 iso for
> i386.
>
> -- Arun Khan
> ___
> CentOS mailing list
> CentOS@centos.org 
> https://lists.centos.org/mailman/listinfo/centos
>


-- 

Shiva Prasad Nath
92981134
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Virtual Server in Windows 7

[Arun Khan]

On Mon, Nov 23, 2015 at 9:17 PM, Siva Prasad Nath
 wrote:
> Hi,
> I am creating a virtual machine. My laptop is i686 system.

How old is your hardware?  I have a 6 year old Toshiba that came with
a core i5  64 bit CPU.

> Please advice me which Centos verson can be downloaded?

If your hardware is indeed 32 bit then download the CentOS 6.7 iso for i386.

-- Arun Khan
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Building for older versions

[Michael Eager]

Hi --

I'm trying to build an application on CentOS 7 which
can run on older versions of CentOS.  I'm running into
problems with versioning of memcpy in Glibc.  Executables
built on CentOS 7 require memcpy from glibc-2.14, which
causes the program not to load on systems with older
versions of glibc.

My online search suggests to add an asm() with a .symver
option to select memcpy from glibc-2.2.5 in each of the
source files which reference memcpy().  This isn't practical
with a program with tens of thousands of source files.

Does anyone have a reasonable solution?

--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Building for older versions

[Nicolas Thierry-Mieg]

On 11/23/2015 04:33 PM, Michael Eager wrote:

Hi --

I'm trying to build an application on CentOS 7 which
can run on older versions of CentOS.  I'm running into
problems with versioning of memcpy in Glibc.  Executables
built on CentOS 7 require memcpy from glibc-2.14, which
causes the program not to load on systems with older
versions of glibc.

My online search suggests to add an asm() with a .symver
option to select memcpy from glibc-2.2.5 in each of the
source files which reference memcpy().  This isn't practical
with a program with tens of thousands of source files.

Does anyone have a reasonable solution?


IMO you should really be building your app on an older Centos version (5 
or 6). Then your binary should run everywhere, though it may sometimes 
require installing a -compat package.


An alternative is to link everything statically. Not as good a solution, 
as it introduces security concerns.

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

Re: [CentOS] Building for older versions

[Chris Adams]

Once upon a time, Michael Eager  said:
> I'm trying to build an application on CentOS 7 which
> can run on older versions of CentOS.  I'm running into
> problems with versioning of memcpy in Glibc.  Executables
> built on CentOS 7 require memcpy from glibc-2.14, which
> causes the program not to load on systems with older
> versions of glibc.

Most shared libraries are "upwards compatible" but not "backwards
compatible" - builds against an old version will run with the new
version, but not the other way around.  You've found this with glibc,
but you could also run into it with other libraries.

> My online search suggests to add an asm() with a .symver
> option to select memcpy from glibc-2.2.5 in each of the
> source files which reference memcpy().  This isn't practical
> with a program with tens of thousands of source files.
> 
> Does anyone have a reasonable solution?

Would it be practical to use mock and build on the oldest version you
want to support?  This is how EPEL packages are built for example.  It
is targeted at building RPMs, but you can manually use copy-in and
copy-out to do other things.

-- 
Chris Adams 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Building for older versions

[Gordon Messmer]

On 11/23/2015 07:33 AM, Michael Eager wrote:
Does anyone have a reasonable solution? 


I'd start here:
https://wiki.linuxfoundation.org/en/Using_lsbdev
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Building for older versions

[Michael Eager]

On 11/23/2015 08:06 AM, Nicolas Thierry-Mieg wrote:

On 11/23/2015 04:33 PM, Michael Eager wrote:

Hi --

I'm trying to build an application on CentOS 7 which
can run on older versions of CentOS.  I'm running into
problems with versioning of memcpy in Glibc.  Executables
built on CentOS 7 require memcpy from glibc-2.14, which
causes the program not to load on systems with older
versions of glibc.

My online search suggests to add an asm() with a .symver
option to select memcpy from glibc-2.2.5 in each of the
source files which reference memcpy().  This isn't practical
with a program with tens of thousands of source files.

Does anyone have a reasonable solution?


IMO you should really be building your app on an older Centos version (5 or 6). 
Then your binary
should run everywhere, though it may sometimes require installing a -compat 
package.


That causes a number of other problems, when the only issue is
accessing a working version of memcpy from the installed glibc.


--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Building for older versions

[Chris Adams]

Once upon a time, Michael Eager  said:
> Building on an older version of CentOS means using older compilers and
> libraries.  Some applications require building with more current tools.

Maybe try an older base OS but with tools from a software collection
add-on?  That's trickier to do with mock (I figured it out once but
don't remember now).

-- 
Chris Adams 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Building for older versions

[Michael Eager]

On 11/23/2015 07:43 AM, Chris Adams wrote:

Once upon a time, Michael Eager  said:

I'm trying to build an application on CentOS 7 which
can run on older versions of CentOS.  I'm running into
problems with versioning of memcpy in Glibc.  Executables
built on CentOS 7 require memcpy from glibc-2.14, which
causes the program not to load on systems with older
versions of glibc.


Most shared libraries are "upwards compatible" but not "backwards
compatible" - builds against an old version will run with the new
version, but not the other way around.  You've found this with glibc,
but you could also run into it with other libraries.


The situation with memcpy is a bit different.  This isn't really a
forward/backward interface compatibility issue.

There was a patch applied to memcpy to improve performance on
some architectures, but it also changed the order in which data was
moved.  Some programs were dependent on this and they broke with the
new implementation.  These programs did not conform to the non-overlapping
data requirements in memcpy's specification.  Programs which did conform
worked with both the new and old implementation.

To prevent non-conforming programs from using the new version of
memcpy, they tagged it with glibc-2.14.  Unfortunately, this also
makes conforming programs, which work with either the old or new
implementation from running on systems which have older versions of
glibc.




My online search suggests to add an asm() with a .symver
option to select memcpy from glibc-2.2.5 in each of the
source files which reference memcpy().  This isn't practical
with a program with tens of thousands of source files.

Does anyone have a reasonable solution?


Would it be practical to use mock and build on the oldest version you
want to support?  This is how EPEL packages are built for example.  It
is targeted at building RPMs, but you can manually use copy-in and
copy-out to do other things.


I'll look into mock.


--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Building for older versions

[Nicolas Thierry-Mieg]

On 11/23/2015 06:00 PM, Michael Eager wrote:

On 11/23/2015 08:06 AM, Nicolas Thierry-Mieg wrote:

On 11/23/2015 04:33 PM, Michael Eager wrote:

Hi --

I'm trying to build an application on CentOS 7 which
can run on older versions of CentOS.  I'm running into
problems with versioning of memcpy in Glibc.  Executables
built on CentOS 7 require memcpy from glibc-2.14, which
causes the program not to load on systems with older
versions of glibc.

My online search suggests to add an asm() with a .symver
option to select memcpy from glibc-2.2.5 in each of the
source files which reference memcpy().  This isn't practical
with a program with tens of thousands of source files.

Does anyone have a reasonable solution?


IMO you should really be building your app on an older Centos version
(5 or 6). Then your binary
should run everywhere, though it may sometimes require installing a
-compat package.


That causes a number of other problems,


can you please provide some details? I'm genuinely curious as I've been 
faced with this occasionally and the only problem I've encountered is 
having to install a few *-compat packages.

thanks.


when the only issue is
accessing a working version of memcpy from the installed glibc.


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

Re: [CentOS] Building for older versions

[Michael Eager]

On 11/23/2015 09:10 AM, Nicolas Thierry-Mieg wrote:

On 11/23/2015 06:00 PM, Michael Eager wrote:

On 11/23/2015 08:06 AM, Nicolas Thierry-Mieg wrote:

On 11/23/2015 04:33 PM, Michael Eager wrote:

Hi --

I'm trying to build an application on CentOS 7 which
can run on older versions of CentOS.  I'm running into
problems with versioning of memcpy in Glibc.  Executables
built on CentOS 7 require memcpy from glibc-2.14, which
causes the program not to load on systems with older
versions of glibc.

My online search suggests to add an asm() with a .symver
option to select memcpy from glibc-2.2.5 in each of the
source files which reference memcpy().  This isn't practical
with a program with tens of thousands of source files.

Does anyone have a reasonable solution?


IMO you should really be building your app on an older Centos version
(5 or 6). Then your binary
should run everywhere, though it may sometimes require installing a
-compat package.


That causes a number of other problems,


can you please provide some details? I'm genuinely curious as I've been faced 
with this occasionally
and the only problem I've encountered is having to install a few *-compat 
packages.
thanks.


Building on an older version of CentOS means using older compilers and
libraries.  Some applications require building with more current tools.

So you end up between a rock and a hard place.  You can try to build
on the older system for library compatibility, but then you have to
use development tools from newer versions.  Or you can build with the
newer tools, and you have compatibility issues running on the older system.



--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Building for older versions

[Michael Eager]

On 11/23/2015 07:57 AM, Gordon Messmer wrote:

On 11/23/2015 07:33 AM, Michael Eager wrote:

Does anyone have a reasonable solution?


I'd start here:
https://wiki.linuxfoundation.org/en/Using_lsbdev


Yeah.  I know about LSB and I've worked with the
LSB committee.  Maybe it's time I tried using it.  :-)


It does seem to be a sledge hammer to address what
seems to be a minor issue.



--
Michael Eagerea...@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Virtual Server in Windows 7

[Siva Prasad Nath]

Hi,
I am creating a virtual machine. My laptop is i686 system.
Please advice me which Centos verson can be downloaded?


With regards,
Shiva
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Kickstarting CentOS 7 VM on CentOS 6 not possible?

[Fabian Arrotin]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 23/11/15 09:59, Jos Vos wrote:
> Hi,
> 
> On CentOS 6.7 (all updates) kickstarting a CentOS 7 VM (in the way
> it always has worked for other versions, incl. Fedora 22 VM's),
> does not work for me.  I use virt-install with a local copy of the 
> "images/pxeboot" tree.  It all stops with:
> 
> ... [  OK  ] Reached target Paths. [  OK  ] Reached target Basic
> System. dracut-initqueue[551]: Warning: Could not boot. 
> dracut-initqueue[551]: Warning: /dev/root does not exist Starting
> Dracut Emergency Shell... Warning: /dev/root does not exist ...
> 
> I found zillion references to similar problems, including
> PXE-related (I do not use PXE, but "-l" with virt-install) and
> cobbler-related (no Cobbler involved), and I tried some of the
> suggestions, but none of them worked.
> 
> Installing CentOS 7 "manually" using virt-install and the netboot
> ISO works fine, but I want to use kickstart files.
> 
> Thanks for any suggestion.
> 

I can say that it works for sure, so can you share your virt-install
command / kickstart / extra-args ?

I'm injecting the kickstart directly into the initrd.img
(transparently through --initrd-inject= )

- -- 
Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlZTh+YACgkQnVkHo1a+xU6a/ACghQ/uXg9j+H14qYN2IlPyz7F9
HakAn3nxaY6EQovmSPd/Pfne7iJGm7yp
=SPNO
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos