PLEASE STOP EMAILING ME IM IN HIGH SCHOOL YOU HAVE THE WRONG LAUREN MCMILLAN!!!!!!!!!!!!!!!!!!!!!!! ----- Original Message Follows ----- From: redhat-list-request@xxxxxxxxxx To: redhat-list@xxxxxxxxxx Subject: redhat-list Digest, Vol 63, Issue 15 Date: Tue, 12 May 2009 12:00:33 -0400 (EDT) >Send redhat-list mailing list submissions to > redhat-list@xxxxxxxxxx > >To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/redhat-list >or, via email, send a message with subject or body 'help' >to > redhat-list-request@xxxxxxxxxx > >You can reach the person managing the list at > redhat-list-owner@xxxxxxxxxx > >When replying, please edit your Subject line so it is more >specific than "Re: Contents of redhat-list digest..." > > >Today's Topics: > > 1. iSCSI/iSAS (M. Hamzah Khan) > 2. lvm (Joy Methew) > 3. RE: Problem with selinux? (Geofrey Rainey) > 4. Re: lvm (Edson Marquezani Filho) > 5. Re: lvm (mark) > 6. Re: lvm (navneet sharma) > 7. Re: lvm (mark) > 8. horde (Joy Methew) > 9. Re: horde (Harry Hoffman) > 10. Re: horde (Barry Brimer) > 11. RE: Prefix question (Smith Jack (Ext. - UGIS - >UniCredit Group)) > > >----------------------------------------------------------- >----------- > >Message: 1 >Date: Mon, 11 May 2009 17:01:25 +0100 >From: "M. Hamzah Khan" >Subject: iSCSI/iSAS >To: redhat-list@xxxxxxxxxx >Message-ID: <4A084BD5.2080107@xxxxxxxxxxxxxx> >Content-Type: text/plain; charset> >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Hello everyone, > >I'm trying to setup an iSCSI target (stgt) with an iSAS >server (Open-iSAS). > >I read README.redhat.setup, and now I am a little confused. > >The README file provided by RedHat states that to setup >stgt with Open-iSAS, I must edit isasadm.conf, and >set SourceName to the target name for the iSCSI tgt target. > >The problem is that I have multiple targets defined in >/etc/tgt/targets.conf. > >Which target must I set the SourceName to? > >I understand that the actual registration is done using >isnsadm - --register, so I can run the command multiple >times, each time with a different target. > >Does this mean I do not need to edit isasadm.conf? > >Regards > >Hamzah > >- -- >M. Hamzah Khan >RedHat Certified Engineer Number: 804005539516829 >Email: hamzah[at]hamzahkhan.com >URL: http://www.hamzahkhan.com >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v2.0.11 (GNU/Linux) >Comment: Using GnuPG with Mozilla - >http://enigmail.mozdev.org > >iEYEARECAAYFAkoIS9UACgkQdfTMIiHVzMmlggCgoTJh5Tj+ILDhgdGdsNC >mrNs0 HOAAoIjKoKN0VjgNsNf3lsqmBnNjz/ms >Ã >-----END PGP SIGNATURE----- > > > >------------------------------ > >Message: 2 >Date: Mon, 11 May 2009 14:08:54 -0400 >From: Joy Methew >Subject: lvm >To: General Red Hat Linux discussion list > Message-ID: > ><64fd0700905111108m6c947ae2k3cc8181e38b0651b@xxxxxxxxxxxxxx >> Content-Type: text/plain; charset> >hello all, > when we wanna create LVM we create a lvm >type drive with 8e code. >but here we can can create lvm partation with simple linux >partation with code 83. >so here is no need to create 8e code partation.... >any perticular reaseon behind this? > > >------------------------------ > >Message: 3 >Date: Tue, 12 May 2009 10:10:22 +1200 >From: "Geofrey Rainey" >Subject: RE: Problem with selinux? >To: "General Red Hat Linux discussion list" > Message-ID: > >, >and le -lZ , and reply with the output. > >-----Original Message----- >From: redhat-list-bounces@xxxxxxxxxx >[mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of >Esteban Torres Rodriguez Sent: Monday, 11 May 2009 11:18 >p.m. To: General Red Hat Linux discussion list >Subject: Problem with selinux? > >Hello Everybody!!! > >I have thats problem with machine on Redhat 4, with >samba-3.0.25b-1.el4_6.5 and winbind. > >*May 11 10:24:16 smb04 kernel: audit(1242030246.549:8): >avc: denied { write } for pidb32 comm>name>scontext>tcontext> >May 11 10:24:16 smb04 kernel: audit(1242030246.899:9): avc: > denied { getattr } for pidb51 comm>name>scontext>tcontext> >May 11 10:24:16 smb04 kernel: audit(1242030246.899:10): >avc: denied { read write } for pidb51 comm>name>scontext>tcontext> >May 11 10:24:16 smb04 kernel: audit(1242030246.899:11): >avc: denied { lock } for pidb51 comm>name>scontext>tcontext> >May 11 10:24:16 smb04 kernel: audit(1242030255.492:12): >avc: denied { lock } for pidb51 comm>name>scontext>tcontext> >I disabled selinux.Anyone help me? > >-- >################################################## ># Esteban Torres Rodríguez # ># Área de Soporte Técnico # ># Subdirección de Sistemas Informáticos # ># Empresa Pública Desarrollo Agrario y Pesquero # ># email: etorres@xxxxxx # >################################################## > > >-- >redhat-list mailing list >unsubscribe >mailto:redhat-list-request@xxxxxxxxxx?subject>https://www.redhat.com/mailman/listinfo/redhat-list >>r more information on the Television New Zealand Group, >visit us online at tvnz.co.nz >>UTION: This e-mail and any attachment(s) contain >information that is intended to be read only by the named >recipient(s). This information is not to be used or stored >by any other person and/or organisation. > > > > >------------------------------ > >Message: 4 >Date: Mon, 11 May 2009 22:20:24 -0300 >From: Edson Marquezani Filho >Subject: Re: lvm >To: General Red Hat Linux discussion list > Message-ID: > ><2fc5f090905111820t66156f0ctfd476e02ae3b295@xxxxxxxxxxxxxx> >Content-Type: text/plain; charset> >On Mon, May 11, 2009 at 3:08 PM, Joy Methew >> wrote: hello all, >> when we wanna create LVM we create a >> lvm type drive with 8e code. >> but here we can can create lvm partation with simple >> linux partation with code 83. >> so here is no need to create 8e code partation.... >> any perticular reaseon behind this? > >It confuses me too. > >What does that partition type exactly mean? I mean, when we >set it, what does it change in the partition table level, >if it does change? And, if not, what does the partition >type actually affect? > > > >------------------------------ > >Message: 5 >Date: Mon, 11 May 2009 20:37:36 -0500 >From: mark >Subject: Re: lvm >To: General Red Hat Linux discussion list > Message-ID: ><4A08D2E0.70308@xxxxxxx> Content-Type: text/plain; >charset> >Edson Marquezani Filho wrote: >> On Mon, May 11, 2009 at 3:08 PM, Joy Methew >>> wrote: hello all, >>> when we wanna create LVM we create a >>> lvm type drive with 8e code. >>> but here we can can create lvm partation with simple >>> linux partation with code 83. >>> so here is no need to create 8e code partation.... >>> any perticular reaseon behind this? >> >> It confuses me too. >> >> What does that partition type exactly mean? I mean, when >> we set it, what does it change in the partition table >> level, if it does change? And, if not, what does the >partition type actually affect? > >What it all matters to is the BIOS. There is *very* little >code in the BIOS - we're talking words, we do *not* have >even kilobytes. The BIOS has to identify what the >partitions are, so it knows how to handle them, or whether >to hand them off to something somewhere later in the >bootstrap process. > >And if you want to see the partition types, in fdisk, if >you go to create a partition, there is an option when it >asks for type that will give you a full list of known >partition types, with what they are. > > mark > > > > >------------------------------ > >Message: 6 >Date: Tue, 12 May 2009 09:06:06 +0530 >From: navneet sharma >Subject: Re: lvm >To: General Red Hat Linux discussion list > Message-ID: > ><7cbba7e60905112036n6bea076hdb92dd9bb8de40da@xxxxxxxxxxxxxx >> Content-Type: text/plain; charset> >hii, >we needed to change the partition type 8e for LVM >partitions in RHEL4 but in RHEL5 we are able to create >with/without changing the partition type to create LVM. >the reason is still non predictable. > >regards >navneet sharma > > >------------------------------ > >Message: 7 >Date: Mon, 11 May 2009 22:39:54 -0500 >From: mark >Subject: Re: lvm >To: General Red Hat Linux discussion list > Message-ID: ><4A08EF8A.5090505@xxxxxxx> Content-Type: text/plain; >charset> >navneet sharma wrote: >> hii, >> we needed to change the partition type 8e for LVM >> partitions in RHEL4 but in RHEL5 we are able to create >> with/without changing the partition type to create LVM. >> the reason is still non predictable. > >That's because having the right partition type provides >lower-level support. You can do it on a straight linux >partition, I *think*, but it's better if you don't. > > mark > > > >------------------------------ > >Message: 8 >Date: Tue, 12 May 2009 13:45:25 +0530 >From: Joy Methew >Subject: horde >To: General Red Hat Linux discussion list > Message-ID: > ><64fd0700905120115k12f077aeh13fecf92c562f846@xxxxxxxxxxxxxx >> Content-Type: text/plain; charset> >hello all, > i can see login page in horde ,now i wanna >take authtication of user by nis server where i write in >horde for nis authication? > >vim /var/www/html/horde/conf/config.php. > >i m confused where i write?? > > >------------------------------ > >Message: 9 >Date: Tue, 12 May 2009 08:58:46 -0400 >From: Harry Hoffman >Subject: Re: horde >To: General Red Hat Linux discussion list > Message-ID: ><4A097286.7060808@xxxxxxxxxxxxxxxx> Content-Type: >text/plain; charset> >Hi Joy, > >It might be better to join the Horde and Imp mailing lists, >as I'm sure you'll get answers more quickly. > >Cheers, >Harry > >Joy Methew wrote: >> hello all, >> i can see login page in horde ,now i wanna >> take authtication of user by nis server where i write in >> horde for nis authication? >> vim /var/www/html/horde/conf/config.php. >> >> i m confused where i write?? > > > >------------------------------ > >Message: 10 >Date: Tue, 12 May 2009 07:58:38 -0500 (CDT) >From: Barry Brimer >Subject: Re: horde >To: General Red Hat Linux discussion list > Message-ID: > >Content-Type: TEXT/PLAIN; charset> >On Tue, 12 May 2009, Joy Methew wrote: > >> hello all, >> i can see login page in horde ,now i wanna >> take authtication of user by nis server where i write in >>horde for nis authication? >> vim /var/www/html/horde/conf/config.php. >> >> i m confused where i write?? > >There are many ways to authenticate horde users. Are you >using the setup pages in the web interface? I don't >believe there is a direct NIS implementation. I use the >IMAP authentication, and others are available. > >Barry > > > >------------------------------ > >Message: 11 >Date: Tue, 12 May 2009 16:19:27 +0200 >From: "Smith Jack (Ext. - UGIS - UniCredit Group)" > >Subject: RE: Prefix question >To: "General Red Hat Linux discussion list" > Message-ID: > ><34F674675D1EF848A4B9A66D6141110D040ADCE4@xxxxxxxxxxxxxxxxx >root.net> Content-Type: text/plain; charset> >I guess I should have used a better title for this topic. > >It should read "rpmbuild prefix question" > >The question is related to the Prefix funcitonality of >rpmbuild spec file > >-----Original Message----- >From: redhat-list-bounces@xxxxxxxxxx >[mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Smith >Jack (Ext. - UGIS - UniCredit Group) >Sent: Monday, May 11, 2009 10:43 AM >To: redhat-list@xxxxxxxxxx >Subject: Prefix question > > >The documentation indicates that it's possible to specify >more than one 'prefix' in the spec file, but does not >provide an example, or explain how one could use this >feature. > >"Note: You can define more than one Prefix: directive to >list more than one top-level directory. " > >How does one specify the second (or further) prefix > >Is it simply a matter of something like this: > >Prefix: /usr/local >Prefix: /usr/share > >wouldn't the second definition over-write the first, or is >it cumulative ? > >or do do something weird (and undocumented) like appending >subsequent prefixes with digits as in: > >Prefix: /usr/local >Prefix1: /usr/share > >or what ? > > >Secondly, once I've defined more than one prefix, what rpm >commandline option allows me to relocate the respective >values: > >rpm -Uvh --prefix>my_beautiful_package-0.001-1.i386.rpm? > >Or do I only have the option of specifying one prefix value >on the commandline (which limits how flexible the >relocation is) ? > >I look forward to your reply ? > >-- >redhat-list mailing list >unsubscribe >mailto:redhat-list-request@xxxxxxxxxx?subject>https://www.redhat.com/mailman/listinfo/redhat-list > > > >------------------------------ > >__ >redhat-list mailing list >Unsubscribe >mailto:redhat-list-request@xxxxxxxxxx?subject>https://www.redhat.com/mailman/listinfo/redhat-list > >End of redhat-list Digest, Vol 63, Issue 15 >******************************************* -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subjecthttps://www.redhat.com/mailman/listinfo/redhat-list
