search for: peterwood

I have two identical Supermicro boxes with 32GB ram. Hardware details at the end of the message. They were running OI 151.a.5 for months. The zpool configuration was one storage zpool with 3 vdevs of 8 disks in RAIDZ2. The OI installation is absolutely clean. Just next-next-next until done. All I do is configure the network after install. I don''t install or enable any other services.

Awesome. Thank you. Embarrassing but I can't find the Q&A page with this question. Can you please post a link to it. Thanks, -- Peter On Fri, Mar 9, 2018 at 11:16 AM, Akemi Yagi <amyagi at gmail.com> wrote: > On Fri, Mar 9, 2018 at 10:46 AM, Peter Wood <peterwood.sd at gmail.com> > wrote: > > > Anyway, I'm stuck with a few 32bit systems exposed to customers and I > have > > to come up with an answer to their question about meltdown/spectre. At > this > > point all I can say is that Red Hat hasn't patched 32bit system...

Hi Johnny, Thank you for your reply. It seems to me that my message may have came around as offensive but that was not my intend. I have basic understanding how things work and when I said CentOS I actually meant Red Hat and all its derivatives. I asked CentOS community because that's the community I'm member of. Not to say that CentOS is not secure or anything like that. Anyway,

On Fri, Mar 9, 2018 at 10:46 AM, Peter Wood <peterwood.sd at gmail.com> wrote: > Anyway, I'm stuck with a few 32bit systems exposed to customers and I have > to come up with an answer to their question about meltdown/spectre. At this > point all I can say is that Red Hat hasn't patched 32bit systems but that > is hard to believe...

HTTPD on some of my CentOS5 systems is configured to run as user "nobody". Also, it needs access to some exported file systems. CentOS5 uses NFS3 so I changed the ownership of the files on the storage server to "nobody" to give httpd full permissions. Now I want to rebuild these systems with CentOS6 and httpd running as user "apache". The problem is how to give

On CentOS5 I was used to create a simple spec file where at the end I'll declare files and directories I wan't to package: --< Snip >-- %files %dir /opt/myapp %dir /opt/myapp/bin %dir /opt/myapp/etc /opt/myapp/bin/exec01 /opt/myapp/etc/myapp.conf ---- I'll copy the file in /usr/src/redhat/SPECS and run "rpmbuild -bb myapp.spec". On CentOS6 rpm-build package no longer

mkfs.ext4 fails to create 38TB file system on CentOS 6.4 64bit with this error: mkfs.ext4: Size of device /dev/vg02/vtapes too big to be expressed in 32 bits using a blocksize of 4096. More details follow: # uname -a Linux tzbackup 2.6.32-358.18.1.el6.x86_64 #1 SMP Wed Aug 28 17:19:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux # fdisk -l /dev/sdc Disk /dev/sdc: 41996.7 GB, 41996727091200

[root at build6 ~]# cat /etc/redhat-release CentOS release 6.5 (Final) [root at build6 ~]# [root at build6 ~]# uname -a Linux build6 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31 17:20:51 UTC 2014 x86_64 x86_64x86_64 GNU/Linux [root at build6 ~]# yum clean all Loaded plugins: fastestmirror, security Cleaning repos: base extras updates Cleaning up Everything Cleaning up list of fastest mirrors

I have a clean install, fully updated CentOS 6 32-bit. When I run the Red Hat detection script: https://access.redhat.com/sites/default/files/spectre-meltdown--a79614b.sh it finds that the system is vulnerable. Is this false positive or there is no patches for CentOS 6 32-bit systems? Thank you, -- Peter

Where can we learn more about the workflow and software used to build CentOS RPMs and iso images? This will be extremely helpful to everyone facing the same challenges of building a custom distro. Thank you all for the hard work on CentOS. On Fri, Jul 12, 2019 at 7:44 AM Johnny Hughes <johnny at centos.org> wrote: > On 7/10/19 1:18 AM, Turritopsis Dohrnii Teo En Ming wrote: > >

I'm using CentOS5.9 and mounting a remote directory via NFSv4. The nfs server is OpenIndiana 151.a.7 (i.e. Solaris). Users bin and daemon have each others ID on the oposite system. On OpenIndiana: User: bin; ID=2 User: daemon; ID=1 On CentOS: User: bin; ID=1 User: daemon; ID=2 That means if I create a file as daemon on the client (CentOS), it gets saved on the server as owner bin