similar to: HP NetServer LC2000r and LH6000r install woes

Hi All, I have some old HP Netserver LPr?s that have old HP RAID controllers (NetRAID 3si?s). The RAID controllers don?t work too well with CentOS. I?ve not been able to get the installer to see the controllers. I?ve read a lot of notes that don?t seem to point to me having any success. So 2 questions. Has anyone successfully used NetRAID 3si controllers with CentOS? Can anyone recommend an

Hi, I tried to install Centos4 on server with scsi NetRaid 1si. This card isnt't support from kernel version 2.6 (old megaraid driver, like LSI controller). What are steps to doing new install with this scsi card? And it will be stable? Thanks, Francesco

Hello my name is Piercarlo and I've discovered a bug in smbd_audit when I trace a Samba 2.2.7 or 2.2.7a on red hat 7.3 -the error exist on the redhat 2.4.18-17kernel ,on the original rh73 2.4.18-3 kernel and on the standard linus kernel (I tried on 2.4.20)-->these kernels are all the kernels that I tried. This error appear when samba is configured as pdc with the roaming of the users

Release notes say no support for the RAID card in a box I just picked up...is there no hope for this box running 2.6 kernel? http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/release- notes/as-x86/ The kernel shipped with Red Hat Enterprise Linux 4 includes the new megaraid_mbox driver from LSI Logic, which replaces the megaraid driver. The megaraid_mbox driver has an improved design,

Hi, what to do, if the kernel hangs on boot time with: megaraid: ABORTING-1 cmd=12 <c=0 t=0 l=0> megaraid: ABORTING-1[d7] fw owner Konrad Naumann _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I'm reading man nut.conf, and trying to understand the MODE directive. Does the specification mode=netserver mean that only upsd and the driver(s) will be started, and that upsmon will not be started? The man page says "Distribution?s init script should source this file in order to determine which components have to be started." But looking at the code which starts upsd in the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:08.realpath Security Advisory The FreeBSD Project Topic: Single byte buffer overflow in realpath(3) Category: core Module: libc Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:08.realpath Security Advisory The FreeBSD Project Topic: Single byte buffer overflow in realpath(3) Category: core Module: libc Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:08.realpath Security Advisory The FreeBSD Project Topic: Single byte buffer overflow in realpath(3) Category: core Module: libc Announced:

Hello there. I tried make update using the following stable-supfile: *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_4 *default delete use-rel-suffix and my two nearest Russian CVS mirrors showed no changes in realpath. Heck, I downloaded the patch and said in /usr/src: # patch < realpath.patch so it was rejected. Then I looked into realpath.c's revision and

Bug report, rather than R-help; This is at least since 1.0.0; didn't try even older versions .. Jim> Anon wrote: Anon> ...However, if I use Fred <- c(1,"33")... Is this a Anon> bug, or am I missing something? this made use it essentially something like par(lty = "1") Jim> This is an interesting problem. It boils down to the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:08.realpath Security Advisory The FreeBSD Project Topic: Single byte buffer overflow in realpath(3) Category: core Module: libc Announced:

How do i unsubscribe??

if((group_c = *lp_force_group(snum))) { BOOL is_guest = False; some lines deleted token = create_nt_token(uid, gid, current_user.ngroups,current_user.groups, is_guest); must_free_token = True; } set_sec_ctx(uid, gid, current_user.ngroups, current_user.groups,token); /* * Free the new token (as set_sec_ctx

Hi, I've encountered the following problem at a client. The problem results in one or more of the smbd processing continuously grabbing more and more memory until the system runs out of memory or just becomes unusable due to a low memory condition. This error is extremely serious as the entire server is eventually brought down by one error. After debugging this error at the

depends on "autoconf: regenerate configure scripts with 4.4 version" This series removes some of the really old deadwood from the tools build and makes some other things which are on their way out configurable at build time with a default depending on how far down the slope I judge them to be. * nuke in tree copy of libaio * nuke obsolete tools: xsview, miniterm, lomount & sv *