Discuss

discuss@lists.centos.org

5 participants
34752 discussions

mozilla bug?
by Robert 17 Dec '05

17 Dec '05

I had an embarrassing experience today, attempting to demonstrate that with gmail one can use the web interface when he must or use the pop/smtp interface or use both at the same time. The web interface would not work with mozilla-1.7.12-1.4.1.centos4. A quick check showed that firefox-1.0.7-1.4.1.centos4 has the same symptom -- that is, displays a page containing nothing but "Loading..." after user and password are entered. Konqueror works fine, as does mozilla-1.7.8-2 on an FC4 box I have. I can find nothing on this list regarding this and will admit that since the common denominator appears to be the "1.4.1.centos4", I haven't checked mozilla bugzilla. Can someone confirm that my imagination hasn't run wild?

5 5

CentOS-announce Digest, Vol 10, Issue 7
by centos-announce-request＠centos.org 17 Dec '05

17 Dec '05

1 0

Belking USB KVM switch & the unresponsive mouse - it works now
by Ron Jones 17 Dec '05

17 Dec '05

>>Tried switching ports on KVM? I didn't think of that, so on your suggestion, I did try it, but still didn't get any love from the mouse >>when booting, let the boot process finish before you switch >>ports. Other than that, my two belkin 6 porters work like a champ! >>Hope that helps.... You know... I can't explain it, but it works. I was really hoping to be able to offer back a set of clearly defined steps to follow in order to resolve this question (I really like it when I see them, so I try to do that whole 'golden rule thing). I let the computer boot completely, leaving the kvm set on my linux box for the entire cycle. Upon logging in and entering 'startx' I thought for a moment that it didn't work, and the mouse was still sitting there, unresponsive in the center of the screen. However, after a few seconds, I noticed that it moved. I had occasion to add a new UPS to the server last night, and when I restarted, I did NOT set the KVM to view the CentOS screen. Instead, I was busy with some work on my Windows desktop. When I switched over to take a look, I noticed that after starting up the X server, my mouse worked just fine. It figures! Unfortunately, it kind of "just works" now, I don't know whether it's in the completion of the boot cycle before switching over, or whether there are other factors involved. >>They had a firmware patch for the kvm on the site, >>but it wasn't exactly a painless progress to update the firmware. Thanks, I didn't know that, I hope that I don't need it. Ron Jones Alpharetta, GA

1 0

SELinux threads, cynicism, one-upmanship, etc.
by Lamar Owen 16 Dec '05

16 Dec '05

After reading through the various SELinux threads, I really became quite perturbed. I mean, really quite perturbed. As an IT Director (and the entire IT department, currently), if I were hiring a sysadmin I know for a fact that someone whose first response to a question on why something doesn't work is 'turn it off' would not get a job here. Neither would a sysadmin with as much cynicism as has been displayed, or an automatic 'it broke things' when something new (and in fact improved) comes along get a job here. Do realize that this list is archived, and that many people who are hiring might use Google to find your name (or mine, for that matter). No, I would hire someone who would read enough of the friendly manual to know where to look and who to ask to find the fix for the real problem. The real fix is there; thanks to the KMail developers for including a 'mark as important' feature so I can find that message amongst the drivel in that thread easily (well, actually I'll probably just delete everything but the real solution). It is the lazy sysadmin who just turns things off without an understanding as to why they are turned off; don't give me the 'overworked' line; you had enough time to post here on the brokenness of SELinux, so you had enough time to find the problem's real source. I am not interested in hiring lazy sysadmins, once I get to hiring. Bryan Smith, for all the verbosity he is known for, doesn't seem to be lazy and could likely hold the job; Craig White likewise, among many others here. I won't name all the names to protect the guilty. :-) The main reason I think sysadmins in general seem to hate SELinux is the 'Mandatory' part of 'Mandatory Access Control' : that is, superuser power is too addictive to get rid of, and SELinux can do away with 'superuser' powers entirely. AND THAT IS A GOOD THING. Yes, it really is. The buffer overflow exploit for those root-running daemons doesn't stand a chance even if it gains root, as long as the selinux policies are set properly. And, yes, it is possible to set the policies properly; any daemon whose developers feel that it needs to be exempt from such might have a problem running on my servers. In a nutshell, SELinux is on and enabled everywhere here; I can't seem to find any measureable speed difference between SELinux targeted, permissive or off; it is unobtrusive in my experience, and it does indeed help protect internet-facing systems from unknown buffer overflows. This is a good thing, and I am convinced that the minor inconvenience of learning a new security tool's configuration is a great tradeoff; especially when the alternative is a compromised system. As there is no such thing as a 100% secure system, anything that improves security but, when properly configured, doesn't impact usability is a BIG WIN in a my book, and probably in many other IT Directors' books too. I have been running Red Hat Linux on internet-facing servers for quite a while, now, and in my opinion and experience, SELinux is the best thing to happen to Linux since 0.13 was released. It's about time the antiquated default Unix permissions system was overhauled. Yes, it requires study, thought, and care. I would expect nothing less of any sysadmins who would work under me. Also, as one poster wrote, SELinux is NOT a *service* but is indeed the Bully Boss of the system. This is also a good thing for internet-facing servers to have; how is the machine supposed to know that the Real Root has logged in, and that that process with euid 0 really was started by the Real Root? The Real Root should take the time to configure in to the policies those things the Real Root would normally do (you know, things like backups and the like, along with other normal activities), but then block those actions that the Real Root would not do (like install a rootkit; yes, a properly configured SELinux can prevent installation of a rootkit on your machine even if it gets 'rooted'). The power of the properly configured Mandatory Access Control system (The Bully Boss) is completely in the control of the Real Root, but untouchable by those Fake Roots who wish to do your system harm. This is again a good thing, and one I would think Diligent Sysadmins would be falling over themselves trying to learn and deploy. -- Lamar Owen Director of Information Technology Pisgah Astronomical Research Institute 1 PARI Drive Rosman, NC 28772 (828)862-5554 www.pari.edu

15 49

Block file system browing with Nautilus
by Kanwar Ranbir Sandhu 16 Dec '05

16 Dec '05

Hello All, It's possible to lock down the Gnome desktop so that a user can't open a terminal. One of the steps includes not letting Nautilus manage the desktop, but that's okay. However, it's still possible to browse the file system with Nautilus by clicking on "Computer" in the tool bar, and then on "Filesystem". I want to block this. Can the "Filesystem" icon be removed? I haven't seen an gconf keys that can be set, but I may have missed them. Is there some other method available to remove that option in Nautilus? Oh, I'm trying to do this on a CentOS 4 system. Thanks for any tips. Regards, Ranbir -- Kanwar Ranbir Sandhu Systems Aligned Inc. www.systemsaligned.com

1 0

Kernel 2.4 and Centos4
by Maciej Żenczykowski 16 Dec '05

16 Dec '05

Hi, Has anyone used a 2.4 series kernel on RHEL4/Centos4? There's a patch (openmosix) which I would really like to make use of [seeing as I just got 10 diskless computers...] which is not ready (yet) for the 2.6 kernel series... Can I just drop in a 2.4.26 series kernel and continue to have a working system? Or is RHEL now totally dependent on 2.6 kernel features? Cheers, MaZe.

3 3

CentOS-announce Digest, Vol 10, Issue 6
by centos-announce-request＠centos.org 16 Dec '05

16 Dec '05

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)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. CEBA:2005-1214-2 CentOS 4 i386 nx - bugfix update (Extras Only) (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 14 Dec 2005 20:26:35 -0600 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA:2005-1214-2 CentOS 4 i386 nx - bugfix update (Extras Only) To: CentOS-Announce <centos-announce(a)centos.org> Message-ID: <1134613595.3551.42.camel(a)myth.home.local> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Bugfix Advisory 2005:1214-2 CentOS 4 i386 NX - Bugfix Update (Extras Only) This CEBA rolls in updates to NX server up to and including the "Third Maintenance Release of the NX 1.5.0 Server Packages" from www.nomachine.com. You should use the latest nomachine client from this link to connect to CentOS after this NX upgrade: http://www.nomachine.com/download.php --------------------------------------------------------- The following items are among the bugs that have been resolved since the previous CentOS release of NX: * Sessions may be left in status 'suspending'. * The NX server fails to go in timeout when the NX Client Available GUI remains open. * Sometimes NX server doesn't forcibly kill a failed X11 session and leaves it hanging. * The space character is not supported in the NX user's passwords. * The NX server doesn't allow empty password for VNC sessions. * Some applications like Java NetBeans and IntelliJ, MS PowerPoint run through CrossOver Office and SlickEdit don't work properly in a X11 session. * Resuming OpenGL-based 3D applications running in an X11 session may show windows with no content. * The keyboard doesn't work properly when an X11 session is migrated from a x86 platform to Mac OS X and vice versa. * Removed the dialog shown when a session is resumed over a slow link. * The X11 agent may crash when the proxy on the client side disconnects. * Floating X11 sessions may shut down unexpectedly when minimized applications are still running. * An X11 session fails to start if the -kb option is specified in the AGENT_EXTRA_OPTIONS_X key. * Sudden disconnection of a rootless X11 session when saving an unreachable link with Konqueror. * Double redraw of the NoMachine splash screen at RDP session startup. * Buggy display of scroll-bar patterns in the OpenOffice application run inside a RDP full-color session. * Improvements on the way nxsetup creates links to the run-level directories for starting and stopping the NX server services. * Added the shutdown command to stop the NX server and terminate all the sessions. * Solved problems related to the minimizing and the refresh of windows and cursor shapes when reconnecting a seamless session. * Solved the unreliable behaviour when running IntelliJ, BeanShell, Wine, PerlTK and XView applications in seamless sessions. * Fixed the bugs arising when resizing the RDP agent's window. * Solved the incorrect handling of some X11 agent options, like the 'norender', 'slow' and 'fast' options that may be specified in the NX server configuration. * Fixed problems with the CUPS backend on AMD64 architectures. * Improved detection of session status in the case of abnormal session terminations. * Improved management of user accounts with options for setting UID, GID and home directory of the NX accounts to be created. * Added a new configuration key to forcibly disable the initialization of the keyboard layout on the remote X server. This may be useful for test purposes. * Improvements in NX server's methods to verify the validity of the configuration parameters. * Fixed printing jobs hangs when printing from remote server. * Improvements to handling of expose events. * Disabled some logs left in the X11 agent. --------------------------------------------------------- The following versions of NX sources are used in this release of NX for CentOS 4: nxproxy-1.5.0-9.tar.gz (same as last release) nxcomp-1.5.0-80.tar.gz (upgraded) nxcompext-1.5.0-20.tar.gz (upgraded) nx-X11-1.5.0-21.tar.gz (upgraded) nxagent-1.5.0-112.tar.gz (upgraded) nxviewer-1.5.0-15.tar.gz (upgraded) nxdesktop-1.5.0-78.tar.gz (upgraded) nxscripts-1.5.0-11.tar.gz (same as last release) --------------------------------------------------------- Excellent instructions for how to install NX / freenx are available from Rick Stout's article here: http://fedoranews.org/contributors/rick_stout/freenx/ (except use the command: yum install freenx nx then follow Rick's instructions for the keys and client install) --------------------------------------------------------- The following files are uploaded and syncing to the mirrors: i386: nx-1.5.0-1.centos4.i386.rpm src: nx-1.5.0-1.centos4.src.rpm

4 6

Ghost 8.0 Clone Filesystem with ext3 (remove resize_inode and ext_attr features)
by Cesar Lagarrigue 16 Dec '05

16 Dec '05

I've Found a page with interesing discussion about images backup http://forums.fedoraforum.org/archive/index.php/t-28255.html This give a "dirty" solucion for remove special thing of ext3 (Selinux remove resize_inode and ext_attr features) witch cause the error in ghost. I hope somebody help with the problem of norton ghost and clone centos 4. :) ----------- sfabkk 2005-07-11, 04:53 AM PDT Solution to using Ghost 8 with Core 3 and 4 Good news : It can be done Bad News : You have to turn off SELinux Forever and remove resize_inode and ext_attr features from filesystem. Also if you mess this up it could kill your system, so I would use G4U (Ghost 4 Unix) to image it first before you try. Here's the procedure to remove resize_inode and ext_attr features from filesystems on an FC3 or FC4 installation. Everything must be done from the root account. Step 1 If you installed FC3 or FC4 with SELinux enabled, which is the default, it you must disabled. Log on the system and edit /etc/selinux/config. Replace SELINUX=enforced by SELINUX=disabled. If you don't disable SELinux, the ext_attr will be set again on the root filesystem the next time you boot and every file created or modified will have its extended ACL entries set. Step 2 Download e2fsprogs-1.36-rc5 from SourceForge. Click on the following link: http://sourceforge.net/projects/e2fsprogs Step 3 Untar, compile and install the new utilities: tar -zxf e2fsprogs-1.36-rc5.tar.gz cd e2fsprogs-1.36-rc5 ./configure make make install Step 4 Reboot the system in single-user mode: type reboot at the GRUB splash screen, press enter then press the 'a' and add the word single at the end of the command line (there's a space between quiet and single) Step 5 Unmount all filesystems, including /, and remove both resize_inode and ext_attr features. Run the following commands on all filesystems: debugfs -w /dev/XXXX -R "features ^resize_inode ^ext_attr" e2fsck -y -f /dev/XXXX Example: /dev/sda1 is mounted on /boot /dev/sda2 is mounted on / /dev/sda5 is mounted on /home umount /boot umount / umount /home debugfs -w /dev/sda1 -R "features ^resize_inode ^ext_attr" debugfs -w /dev/sda2 -R "features ^resize_inode ^ext_attr" debugfs -w /dev/sda5 -R "features ^resize_inode ^ext_attr" e2fsck -y -f /dev/sda1 e2fsck -y -f /dev/sda2 e2fsck -y -f /dev/sda5 Running e2fsck on the root filesystem takes a while. Step 6 Reboot the system. During shutdown, you will get error messages telling you that the root filesystem cannot be written. That's normal because the root filesystem is still mounted read-only. It must remain mounted read- only during shutdown. During boot, you will get a message telling you that the system was not properly shutdown and ask you if you want to verify the filesystem integrity. You can skip this step. It didn't find anything wrong on my system. Your system is now ready to be Ghosted. link to the bugzilla report https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145307 -- Cesar Lagarrigue V.

2 1

usb error when using Belkin 2-port KVM switch F1DL102U
by Ron Jones 16 Dec '05

16 Dec '05

I've chased all over google and haven't come to any satisfactory resolution on this... today, I installed a Belkin 2-port KVM switch (with audio support & built in cabling) for my CentOS 4.2 server AND my Windows XP desktop. Now, the mouse (a USB mouse) does not work on the Linux box. However, it WILL work if I plug it directly into the CentOS box. if I switch over to the CentOS 4 interface, before I startx, I see a display on the screen that consists of the following output: "drivers/usb/input/mid-core.c: input irq status -84 received" (minus the quotes) This message is repeated every few moments. Has anyone seen/heard of something like this before? Thanks, Ron Jones Alpharetta, GA

4 4

RE: [CentOS] csgfs repo problem
by Bowie Bailey 16 Dec '05

16 Dec '05

From: Karanbir Singh [mailto:mail-lists@karan.org] > > Bowie Bailey wrote: > > I just took a brand new CentOS 4.2 x86_64 install, updated all of > > the base packages with yum, and then added the csgfs repo and > > attempted to install those packages. > > > > When I do the installation, I have a problem with one package: > > > > Package perl-Net-Telnet-3.03-3.noarch.rpm is not signed > > > > I know I can set gpgcheck=0 in the repo definition, but shouldn't > > this be fixed in the repo? Is there another way to specifically > > allow this one package to install without turning off gpg checks > > for the entire repo? > > > > Couple of packages had this issue - all fixed now, try again. > Depending on what mirror you are using - it might take a few hours > for the updates to propagate through the mirror network. Thanks. I have already bypassed the problem on this install, but hopefully this will make things go smoother on the next one. Bowie

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss