Discuss

discuss@lists.centos.org

2 participants
34758 discussions

CentOS6: ntfs-3g and writing utf-8 filenames
by wwp 19 Feb '15

19 Feb '15

Hello there, I know this has been widely discussed over the net, but I still can't find a way to write a file whose name contains accented characters in ntfs-3g partitions that are automatically mounted on my CentOS6 system. Whatever my locale is POSIX, en_US or en_US.utf8, I always get a: Invalid or incomplete multibyte or wide character error when I attempt to create a directory or a file when the name contains an accented char. I tried remounting manually the ntfs-3g partition using -o utf8 (and older variants: iocharset= and nls=), but it doesn't work better. My ntfs-3g disks are automatically mounted in GNOME (as fuseblk). Using ntfs-3g-2014.2.15-8.el6.x86_64 in an up-to-date CentOS6 system. Any hint? Regards, -- wwp

1 0

Re: [CentOS] CentOS 7: software RAID 5 array with 4 disks and no spares?
by James B. Byrne 19 Feb '15

19 Feb '15

On Thu, February 19, 2015 02:25, Niki Kovacs wrote: > Le 19/02/2015 05:43, Chris Murphy a écrit : >> My personal view on installers is extremely biased toward the user >> staying out of trouble, they shouldn't have to read documentation >> for >> a GUI installer. > > A *user* never has to even see - or use - an installer. A USER has to > USE a computer, by which I mean the applications he or she needs to > get some work done. Outside of the corporate world, and very often at the low-end of that itself, the user is the ADMIN. One can purchase computer systems with the OS and applications pre-installed of course. But, at some point, in every sufficiently complex and long-lived environment somebody has to do maintenance. Which on occasion does include installing operating systems. And even ADMINs can use some help from time-to-time. Let us be frank, the Linux/GNU hoge-poge of syntax makes the English language look positively simple in comparison. And that is not a good thing. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

CentOS Participation in GSOC-2015
by Saket Sinha 19 Feb '15

19 Feb '15

Hi Johnny, This is to enquire as to whether CentOS will be participating in GSOC this year? The Mentoring Organization applications are now being accepted for Google Summer of Code 2015. http://google-opensource.blogspot.in/2015/02/mentoring-organization-applica… Regards, Saket Sinha

2 1

sw raid issue with C5.10-xen
by Dave Stevens 18 Feb '15

18 Feb '15

My raid array won't boot, gives a kernel panic - attempt to kill init message and goes into endless reboots. MB is a supermicro 2P with opteron 2376 4-core cpus, centos sw raid, installed C5.3, updated as possible, currently c5.10. 5 seagate 750GB drives as raid-10 and hot spare. we set this up about 5 years ago and IIRC we set aside the first 10GB on drive 0 as a boot partition. Grub runs and the system tries to boot 2.6.18-308.20.1.el5xen, sees a dirty raid array and md: md0: raid array is not clean - starting background reconstruction which looks hopeful but then md10: not enough operational mirrors for raid 10 and then the panic and reboot. ideas? stuff to read? diagnostics? TIA, Dave -- "As long as politics is the shadow cast on society by big business, the attenuation of the shadow will not change the substance." -- John Dewey

1 0

Skip creating anaconda-ks.cfg in EL7?
by Nux! 18 Feb '15

18 Feb '15

Hello, In EL6 I could well remove /root/anaconda-ks.cfg in %post, but not any more it seems and I like my installs clean. Anyone has any idea how to skip creating this file or deleting during install? I don't want to resort to running scripts upon first boot. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro

1 0

Setting up new spacewalk server
by Eckert, Doug 18 Feb '15

18 Feb '15

We have a DHCP/PXE server in a build environment, which is separate from our Spacewalk v1.5 server. We direct builds to Satellite or Spacewalk based as needed. It contains initrd & vmlinuz files for each version/arch we currently deploy for both RHEL & CEL. I'd like to keep the storage footprint to a minimum, if possible. Keeping a big directory of ISOs to loop-mount for kickstart profile distributions seems excessive, especially when DVD#1 exceeds 4GB now. Is there any way around this requirement for kickstarting?

3 5

Help with routing question.
by James B. Byrne 18 Feb '15

18 Feb '15

CentOS-6.6 We have a host that has multiple IPv4 addresses aliased to eth0. The primary address is 216.185.71.x and the alias is 192.168.6.x. This host connects to devices on both netblocks without problems. Only default routing is used and it looks like this: #ip route 192.168.6.0/24 dev eth0 proto kernel scope link src 192.168.6.x 216.185.71.0/24 dev eth0 proto kernel scope link src 216.185.71.x 169.254.0.0/16 dev eth0 scope link metric 1002 default via 192.168.6.1 dev eth0 src 192.168.6.x default via 216.185.71.1 dev eth0 When the system connects to internal systems via ssh it uses the src 216.185.71.x for devices on that netblock and 192.168.6.x for devices on the other. The problem is that when we try to establish an ssh connection off-site to another netblock altogether the host uses 192.168.6.x as the source and the destination gets the public side IP address of our gateway router as the point of origin due to masquerading. I have solved this by explicitly binding ssh to the public ipv4 when connecting using the --bind=216.185.71.x parameter. But I have two questions I would like to find answers for 1. Why is ssh using the private IP in preference to the public IP when connecting to off-site addresses? 2. How does one configure the routing table on network startup to specifically detail the route particular addresses are supposed to take? For diagnosis here are the ifcfg scripts used for both interfaces: DEVICE="eth0" BOOTPROTO="static" BROADCAST="216.185.71.255" DNS1="216.185.71.33" GATEWAY="216.185.71.1" HWADDR="38:60:77:D5:AC:D8" IPADDR="216.185.71.x" IPV6INIT="yes" IPV6_AUTOCONF="yes" NETMASK="255.255.255.0" NM_CONTROLLED="no" ONBOOT="yes" TYPE="Ethernet" UUID="0202e615-ce93-4fe1-833a-c11259afb850" DEVICE="eth0:192" BOOTPROTO="static" BROADCAST="192.168.6.255" GATEWAY="192.168.6.1" IPADDR="192.168.6.x" NETMASK="255.255.255.0" NM_CONTROLLED="no" ONPARENT="yes" TYPE="Ethernet" -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

4 3

debuginfo versioning tools?
by Les Mikesell 18 Feb '15

18 Feb '15

Are there any tools to help assemble libraries and debuginfo to examine core dumps that happened on another host where the versions don't match? Something like mock but build-version specific and with the debuginfo packages pulled in? -- Les Mikesell lesmikesell(a)gmail.com

2 2

Re: [CentOS] debuginfo versioning tools?
by James B. Byrne 18 Feb '15

18 Feb '15

On Tue, February 17, 2015 15:20, Les Mikesell wrote: > Are there any tools to help assemble libraries and debuginfo to > examine core dumps that happened on another host where the versions > don't match? Something like mock but build-version specific and with > the debuginfo packages pulled in? > I am not sure that I understand your question so if this answer is totally irrelevant then please forgive me. But, in case this might help, you can configure mock to use locally provided repos and different architectures via the --configdir parameter. You provide an architecture specific config file like epel-6-x86_64.cfg in the specified directory and alter it to require packages to suit a specific build requirement. One of mine looks like this: config_opts['root'] = 'epel-6-x86_64' config_opts['target_arch'] = 'x86_64' config_opts['legal_host_arches'] = ('x86_64',) config_opts['chroot_setup_cmd'] = 'groupinstall buildsys-build' config_opts['dist'] = 'el6' # only useful for --resultdir variable subst config_opts['yum.conf'] = """ [main] cachedir=/var/cache/yum debuglevel=1 reposdir=/dev/null logfile=/var/log/yum.log retries=20 obsoletes=1 gpgcheck=0 assumeyes=1 syslog_ident=mock syslog_device= # repos [base] name=BaseOS enabled=1 mirrorlist=http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=os failovermethod=priority exclude=http* [updates] name=updates enabled=1 mirrorlist=http://mirrorlist.centos.org/?release=6&arch=x86_64&repo=updates failovermethod=priority exclude=http* [epel] name=epel mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6&arch=x86… failovermethod=priority exclude=http* [testing] name=epel-testing enabled=0 mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=testing-epel6&a… failovermethod=priority [local] name=local baseurl=file:///home/byrnejb/mock/repos/x86_64/ cost=0 enabled=1 [koji] name=koji baseurl=http://kojipkgs.fedoraproject.org/repos/dist-6E-epel-build/latest/x… cost=2000 enabled=0 [epel-debug] name=epel-debug mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=epel-debug-6&ar… failovermethod=priority enabled=0 """ and one calls it like this: mock --rebuild --root=epel-6-x86_64 --configdir=/home/byrnejb/mock /home/byrnejb/rpmbuild/SRPMS/httpd-2.4.9-1.el6.src.rpm -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

Re: [CentOS] How to write RPM spec
by James B. Byrne 18 Feb '15

18 Feb '15

> On Wed, 18 Feb 2015 05:36:48 +1300 > Jegadeesh Kumar wrote: > >> I setup the RPM build server and read some doc to write the spec >> files. but i did get it clearly. So can you guys please help me >> to write a new RPM spec. If you have set up an RPM build server then you should have installed the rpmbuild and rpmdevtools packages. If you have installed the latter then you can use vi (vim/gvim) to automatically create an empty spec template file simply by opening any new file name ending in '.spec'. It will look like this: Name: Version: Release: 1%{?dist} Summary: Group: License: URL: Source0: BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XXXXXX) BuildRequires: Requires: %description %prep %setup -q %build %configure make %{?_smp_mflags} %install rm -rf %{buildroot} make install DESTDIR=%{buildroot} %clean rm -rf %{buildroot} %files %defattr(-,root,root,-) %doc %changelog * Fri Apr 05 2013 James B. Byrne <byrnejb(a)harte-lyne.ca> - Rebuild for CentOS-6.4 - This description is an example and is not automatically - generated for you. Note that the formats for the date and identity in changelog entries are very specific and include the leading '*'. You cannot use any other format (to my knowledge) than that given above as an example. Each descriptive line thereafter must be prefaced by'- '. See: https://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Pa… -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss