Re: sockets and scientific linux security
On Mon, 8 Apr 2013, Charles Campbell wrote: Hello! I'm pretty sure that I'm running into a security blockade. I have several small example sockets programs which have compiled and worked in the past on other platforms. However, they are not working under SL 6.3, even when I change ports multiple times. I have: * disabled SELINUX (I first tried setenforce 0 as root to make it simply permissive, but no luck, so I disabled it instead) * turned iptables off: /etc/init.d/iptables stop Still, after having done both of these, I can't get a simple socket and client example to work. The /var/log/messages file simply shows my shutting off of iptables. Is there another thing that I can do to get some simple sockets examples to work? I figure once I have located the problems, I can begin to attack the rules needed to get it to work. Regards, and thank you, Chip Campbell What does not work about them? What port numbers are you using? Running as what user? -Connie Sieh
failure of anaconda upgrade to SL 6.4 X86-64
My workstation has the following disk partition setup: /dev/sda10 swapswapdefaults0 0 /dev/sda5/ ext2defaults1 1 /dev/sda1 /boot ext2defaults1 2 /dev/sda3 /oldhome ext2defaults 1 2 /dev/sda8 /optext2defaults1 2 /dev/sda2 /usrext2defaults1 2 /dev/sda7/usr/local ext2defaults1 2 /dev/sda11/usr1 ext2defaults1 2 /dev/sda9 /varext2defaults1 2 /dev/sda6 /vmware ext2defaults1 2 /dev/sda12 /usr2 ext2defaults1 2 /dev/sdc5 /oldrootext2 defaults 1 2 /dev/sdc1 /oldboot ext2 defaults 1 2 /dev/sdc2 /oldusr ext2 defaults 1 2 /dev/sdc3 /home ext2 defaults 1 2 /dev/sdc6 /oldvmware ext2 defaults 1 2 /dev/sdc7 /oldusr/local ext2 defaults 1 2 /dev/sdc8 /oldopt ext2 defaults 1 2 /dev/sdc9 /oldvar ext2 defaults 1 2 /dev/sdc11 /oldusr1 ext2 defaults 1 2 /dev/sdb1 /mnt-ntfs1 ntfs-3gdefaults 1 2 /dev/sdb2 /mnt-ntfs2 ntfs-3gdefaults 1 2 When I attempt to use the current SL 6.4 X86-64 standalone installation DVD to upgrade, anaconda fails with a diagnostic message that I cannot seem to be able to save (the log file is not created on a physical hard drive). Basically, anaconda does not like the ntfs format disk nor the second linux disk. Is there a way to tell anaconda to use a particular drive (say /dev/sda) and fully ignore others (say /dev/sdb and /dev/sdc) when running anaconda? Can anaconda be run from the DVD from a running linux system that mounts the DVD containing the upgrade image(s)? If not, is there another methodology (say an appropriate invocation of yum but using the DVD as the files from which the upgrade is generated)? If there is URL or other documentation that (easily) explains the above steps, that will be sufficient. Current environment is a previous SL 6 X86-64. Yasha Karant
