Hi everybody, I'm new in that great help place. my question is, how can I jail apache in a chroot directory with fedora? I know how do that action in Centos, modifying the /etc/rc.d/init.d/syslog file but in fedora it doesn't exists..I don't find anything in the internet Thanks anyway > From: fedora-list-request@xxxxxxxxxx > Subject: fedora-list Digest, Vol 70, Issue 59 > To: fedora-list@xxxxxxxxxx > Date: Wed, 9 Dec 2009 08:05:36 -0500 > > Send fedora-list mailing list submissions to > fedora-list@xxxxxxxxxx > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/fedora-list > or, via email, send a message with subject or body 'help' to > fedora-list-request@xxxxxxxxxx > > You can reach the person managing the list at > fedora-list-owner@xxxxxxxxxx > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of fedora-list digest..." > > > Today's Topics: > > 1. Re: Selinux problems (James Allsopp) > 2. Re: Fedora on Macbook Air? (Colin Paul Adams) > 3. Fedora 12 on Sun Blade x6250 (Marcelo M. Garcia) > 4. Re: How do I disable coredumps on F12? (Andre Costa) > 5. Re: Latest Kernel causes reboot hell (Chris) > 6. Re: Latest Kernel causes reboot hell (Ian Malone) > 7. Problem with thunderbird message filters (Joachim Backes) > 8. Re: Latest Kernel causes reboot hell (Sam Varshavchik) > 9. LDAP authentication error (Luc MAIGNAN) > 10. Re: Latest Kernel causes reboot hell (Tom Horsley) > 11. SB driver in F12 ? (Luc MAIGNAN) > 12. confirm (Austin Christain) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 9 Dec 2009 09:34:01 +0000 > From: James Allsopp <jamesaallsopp@xxxxxxxxxxxxxx> > Subject: Re: Selinux problems > To: "Community assistance, encouragement, and advice for using > Fedora." <fedora-list@xxxxxxxxxx> > Message-ID: > <d7feae030912090134o641a4bb6lef4075f9a94c086d@xxxxxxxxxxxxxx> > Content-Type: text/plain; charset="iso-8859-1" > > Yes, it seems to have worked, thank you! > James > > 2009/12/9 Wolfgang S. Rupprecht <wolfgang.rupprecht@xxxxxxxxx> > > > > > James Allsopp <jamesaallsopp@xxxxxxxxxxxxxx> writes: > > >I keep getting this SELinux issue, This is a new install of Fedora 12, and > > >I just copied all of my home directory back to this machine from an > > >external after install. I've tried running "restorecon /home" but no > > >change. > > ... > > > You can execute the following command as root to relabel your computer > > > system: > > > "touch /.autorelabel; reboot" > > > > Did you read the above? Did you do it? > > > > -wolfgang > > -- > > Wolfgang S. Rupprecht > > If the airwaves belong to the public why does the public only get 3 > > non-overlapping WIFI channels? > > > > -- > > fedora-list mailing list > > fedora-list@xxxxxxxxxx > > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > > Guidelines: > > http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: https://www.redhat.com/archives/fedora-list/attachments/20091209/442c7875/attachment.html > > ------------------------------ > > Message: 2 > Date: Wed, 09 Dec 2009 09:46:28 +0000 > From: Colin Paul Adams <colin@xxxxxxxxxxxxxxxxxx> > Subject: Re: Fedora on Macbook Air? > To: "Community assistance\, encouragement\, and advice for using > Fedora." <fedora-list@xxxxxxxxxx> > Message-ID: <m3vdgg5vkb.fsf@xxxxxxxxxxxxxxxxxx> > Content-Type: text/plain; charset=us-ascii > > >>>>> "Tom" == Tom H <tomh0665@xxxxxxxxx> writes: > > >> But how to get the Air to try to boot from the USB port? > Tom> Try booting with "c" pressed (it is supposed to be for > Tom> CDs/DVDs but it might work with a bootable external drive > > I actually meant with a DVD drive, but probably forgot to say that in > my original message. > This works up to a point. That is, I can begin the installation > process, but when loading the kernel from the DVD, it soon comes to a > halt (this is with F11, 64-bit, purely investigatory, as I shall try with F12 > once I have downloaded the ISO for that). > > >> "Chad" == Chad Kellerman <sunckell@xxxxxxxxx> writes: > > Chad>When it comes to booting from a disk drive, I believe the Air only boot OS's > Chad> from a Super Drive. ( I read that somewhere once..) > > Chad>I think you want to look at http://refit.sourceforge.net/ that has all the > Chad> documentation you need > > Hm. It doesn't actually answer my question outright, but I think the > answer is I can't do it - I will need to retain a minimal Mac OSX > partition. :-( > > (I can't spare the disk space for two OSes, as I use > the Air as a repository for digital photographs when on holiday. I > filled the disk last year with one day to go of a fortnight in > thailand - fortunately the 8GB memory card on the camera didn't fill > on the last day). > -- > Colin Adams > Preston Lancashire > > > > ------------------------------ > > Message: 3 > Date: Wed, 09 Dec 2009 11:06:51 +0000 > From: "Marcelo M. Garcia" <marcelo.maia.garcia@xxxxxxxxxxxxxx> > Subject: Fedora 12 on Sun Blade x6250 > To: fedora-list@xxxxxxxxxx > Message-ID: <4B1F84CB.6070806@xxxxxxxxxxxxxx> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi > > I'm trying to install Fedora 12 x86_64 in a Sun Blade x6250 with PXE > boot but the installation hangs when loading Anaconda, both in graphical > and text mode. I'm using the Sun management tool (Sun eLOM) to do the > network install, maybe Fedora requirements are to high to this tool, but > does anyone knows a work around? > > To test the text mode, I just added the word "text" to the end of line > "APPEND" in pxelinux.0 file, like: > LABEL Fedora 12 x86_64 > MENU LABEL Fedora 12 x86_64 > KERNEL images/Fedora/12/x86_64/vmlinuz > APPEND initrd=images/Fedora/12/x86_64/initrd.img > ramdisk_size=100000 text > > Thanks > > Marcelo > > > > > ------------------------------ > > Message: 4 > Date: Wed, 9 Dec 2009 09:30:09 -0200 > From: Andre Costa <blueser@xxxxxxxxx> > Subject: Re: How do I disable coredumps on F12? > To: "Community assistance, encouragement, and advice for using > Fedora." <fedora-list@xxxxxxxxxx> > Message-ID: > <6d5924370912090330t6e53fbc5m15fe5320ad868152@xxxxxxxxxxxxxx> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Ed, > > On Wed, Dec 9, 2009 at 01:57, Ed Greshko <Ed.Greshko@xxxxxxxxxxx> wrote: > > > Andre Costa wrote: > > > Hi Rick, thks for the reply. Comments below: > > > > > > On Tue, Dec 8, 2009 at 23:12, Rick Stevens <ricks@xxxxxxxx > > > <mailto:ricks@xxxxxxxx>> wrote: > > > > > > On 12/08/2009 03:44 PM, Andre Costa wrote: > > > > > > Hi, > > > > > > apps crashes are generating coredumps on /var/cache/abrt/* ; > > > since I > > > won't debug them myself and won't send them anywhere because > > > they're too > > > big, I would like to turn them off. I tried uncommenting > > > > > > #* soft core 0 > > > > > > on /etc/security/limits.conf but it did not work, coredumps > > > were still > > > being generated. > > > > > > > > > I believe you need to reboot for that to take effect. > > > > > > > > > I did that, to no avail :-( > > > > > > > > > Then I tried to set > > > > > > MaxCrashReportsSize = 0 > > > > > > directly on /etc/abrt/abrt.conf, restarted abrtd but it didn't > > > work > > > either (oddly enough abrt-gui doesn't allow changing this > > > setting, "ok" > > > button is disabled -- not even if I run it as root). > > > > > > So, as a last resource I created a script on /etc/cron.daily > > > to get rid > > > of the coredumps, but I'd rather not create them in the first > > > place. > > > > > > Anyone could give a hand? > > > > > > > > > Well, you should also, as root: > > > > > > echo 'fs.suid_dumpable = 0' >> /etc/sysctl.conf > > > sysctl -p > > > > > > That prevents suid programs from creating core files. You should > > > also make sure that there is a line to the effect: > > > > > > ulimit -S -c 0 >/dev/null 2>&1 > > > > > > is in /etc/profile so that all users have a core file dump limit size > > > of 0 bytes. > > > > > > > > > Cool, nice tips, will implement them and see if they finally free me > > > from these damned coredumps =/ (IMHO there should be an easier way of > > > doing that, considering this is a "new" feature shipped with F12) > > > > > Have you tried simply turning off the abrtd service? > > > That's definitely an option, and it already crossed my mind, but the thing > is that I'd really like to contribute with bug reports. My problem is not > abrt per se, I actually like the idea, but I just can't understand why it is > not easy to turn off coredumps generation since they're useless -- the > smallest one I've got was 15M, which AFAIK would never be accepted as a > bugzilla attachment (and it can get worse: Firefox keeps generating 350-450M > coredumps when it crashes...). > > So, ideally I would keep abrt around, and just turn off coredumps > generation. But, if worse comes to worst, I will end up disabling it > completely -- which I think will be a step back, but... > > Regards, > > Andre > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: https://www.redhat.com/archives/fedora-list/attachments/20091209/deaf4189/attachment.html > > ------------------------------ > > Message: 5 > Date: Wed, 09 Dec 2009 05:35:47 -0600 > From: Chris <racerx@xxxxxxxxxxxxx> > Subject: Re: Latest Kernel causes reboot hell > To: fedora-list@xxxxxxxxxx > Message-ID: <20091209053547.443101a4@xxxxxxxxxxxxx> > Content-Type: text/plain; charset=UTF-8 > > On Mon, 07 Dec 2009 18:30:02 -0500 > Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> wrote: > > > Chris writes: > > > > > On Mon, 07 Dec 2009 18:06:12 -0500 > > > Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> wrote: > > > > > >> Some time ago, in F9-F10 era, there was a consecutive series of > > >> about four kernels that were released that could not boot on one > > >> of my machines. Somehow, I managed to survive this traumatic > > >> experience without installing a completely different distribution. > > >> I waved a magic wand, and continued to boot the last working > > >> kernel, until a new one came out that worked on my hardware once > > >> more. > > > > > > I agree - quoting from Louis Lagendijk; > > > > > > "The best way to avoid the problem might be to get grub to display > > > the list of installed (assuming that the original F12 kernel worked > > > for you) and select that kernel to boot from. Change the default > > > line in /etc/grub.conf to automate that....." > > > > It just occured to me that there may be a large number of people who > > are completely unaware of the fact that they can easily boot a > > previous kernel. > > > > Some time ago, someone decided to set up grub by default to hide its > > boot menu, so that it boots without delay. As such, some people may > > not even know about this option. > > > > This is a perfect example of why hiding some complexity from the end > > user is not always a good idea. > > > > Thanks for the suggestions to all that helped me out. I am now past the > kernel/reboot issue. > > -- > Best regards, > > Chris > > “It is always better to have no ideas than false ones; to believe > nothing, than to believe what is wrong.â€� > > -- Thomas Jefferson > > > > ------------------------------ > > Message: 6 > Date: Wed, 9 Dec 2009 11:56:32 +0000 > From: Ian Malone <ibmalone@xxxxxxxxx> > Subject: Re: Latest Kernel causes reboot hell > To: "Community assistance, encouragement, and advice for using > Fedora." <fedora-list@xxxxxxxxxx> > Message-ID: > <124299980912090356j7d0b4905jfd4acbfcedd67291@xxxxxxxxxxxxxx> > Content-Type: text/plain; charset=UTF-8 > > 2009/12/7 Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx>: > > >> > >> "The best way to avoid the problem might be to get grub to display the > >> list of installed (assuming that the original F12 kernel worked for you) > >> and select that kernel to boot from. Change the default line > >> in /etc/grub.conf to automate that....." > > Precisely, though there's no 'might' about it. Updated kernel fails to > boot = boot to previous kernel instead. This is one of the easier > update problems to work around, except that: > > > > > It just occured to me that there may be a large number of people who are > > completely unaware of the fact that they can easily boot a previous kernel. > > > > Some time ago, someone decided to set up grub by default to hide its boot > > menu, so that it boots without delay. As such, some people may not even know > > about this option. > > > > This is a perfect example of why hiding some complexity from the end user is > > not always a good idea. > > > > Yes, it does look more polished the way it is now, but what used to be > really obvious (especially to someone who has always run dual boot > set-ups), that you can boot an earlier kernel, is now an obscure piece > of knowledge. Suggestions: > 1. The grub boot screen should have an explicit message to this effect. > 2. (More difficult to implement), autodetect failures to boot and > explicitly offer the user the alternatives. (A la Windows, not > everything they do is bad.) > > -- > imalone > > > > ------------------------------ > > Message: 7 > Date: Wed, 09 Dec 2009 13:05:56 +0100 > From: Joachim Backes <joachim.backes@xxxxxxxxxxxxxx> > Subject: Problem with thunderbird message filters > To: Fedora <fedora-list@xxxxxxxxxx> > Message-ID: <4B1F92A4.9010603@xxxxxxxxxxxxxx> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > I'm running the actual thunderbird (thunderbird-3.0b4) on F12. > > Having two accounts (1 IMAP, I POP), and I want to move all incoming > emails for account-#2 (POP) to the IMAP-Inbox. So I made a filter with > one entry: "Match all messages" as search criteria, and "move to > IMAP-Inbox" as action. > > But this filter seems not to run, and when opening the error console > window, I find a lot of messages: > > --------------------------------------------------------------------- > Error: [Exception... "'_javascript_ component does not have a method > named: "handleEvent"' when calling method: > [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 > (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" > data: no] > ---------------------------------------------------------------------- > > Can anybody explain this behaviour? All comments are welcome. > > Regards > > Joachim Backes > > -- > Joachim Backes <joachim.backes@xxxxxxxxxxxxxx> > > http://www.rhrk.uni-kl.de/~backes > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: smime.p7s > Type: application/pkcs7-signature > Size: 6101 bytes > Desc: S/MIME Cryptographic Signature > Url : https://www.redhat.com/archives/fedora-list/attachments/20091209/3a7bc25a/smime.bin > > ------------------------------ > > Message: 8 > Date: Wed, 09 Dec 2009 07:13:30 -0500 > From: Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> > Subject: Re: Latest Kernel causes reboot hell > To: Community assistance, encouragement, and advice for using Fedora. > <fedora-list@xxxxxxxxxx> > Message-ID: > <cone.1260360810.157957.30383.500@xxxxxxxxxxxxxxxxxxxxxxxx> > Content-Type: text/plain; charset="us-ascii" > > Ian Malone writes: > > > Yes, it does look more polished the way it is now, but what used to be > > really obvious (especially to someone who has always run dual boot > > set-ups), that you can boot an earlier kernel, is now an obscure piece > > of knowledge. Suggestions: > > 1. The grub boot screen should have an explicit message to this effect. > > 2. (More difficult to implement), autodetect failures to boot and > > explicitly offer the user the alternatives. (A la Windows, not > > everything they do is bad.) > > I think there's a way to install a one-time only grub configuration file, > for the next boot. I'm not sure how it's done now, but I think suspend to > disk worked this way before, to have grub boot some loader that restores the > suspended image into ram. If restore failed, the next boot loaded the usual > kernel. > > The kernel update can do that, and a start up script that runs at the end of > the boot cycle then commit the permanent configuration file, at the tail end > of the next boot. > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 198 bytes > Desc: not available > Url : https://www.redhat.com/archives/fedora-list/attachments/20091209/15e26049/attachment.bin > > ------------------------------ > > Message: 9 > Date: Wed, 09 Dec 2009 13:13:26 +0100 > From: Luc MAIGNAN <luc.maignan@xxxxxxxxxxxx> > Subject: LDAP authentication error > To: "Community assistance, encouragement, and advice for using > Fedora." <fedora-list@xxxxxxxxxx> > Message-ID: <4B1F9466.3060209@xxxxxxxxxxxx> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi, > > I use an OpenLDAP server to permit users to log in their computers. All > seem to be ok but for a while. > After several days, users are required to change their passwords (I've > never configured it) and they cannot do that (they are said they don't > have enough rights to do this). > > Has anyone an idea to prevent the unsollicited change of password ? > > BR > > > > ------------------------------ > > Message: 10 > Date: Wed, 9 Dec 2009 07:34:41 -0500 > From: Tom Horsley <tom.horsley@xxxxxxx> > Subject: Re: Latest Kernel causes reboot hell > To: fedora-list@xxxxxxxxxx > Message-ID: <20091209073441.013df972@tomh> > Content-Type: text/plain; charset=US-ASCII > > On Wed, 09 Dec 2009 07:13:30 -0500 > Sam Varshavchik wrote: > > > I think there's a way to install a one-time only grub configuration file, > > for the next boot. > > There are two ways: The one documented in the grub info file, and the > one that actually works :-). Both involve "savedefault", but the > grub "help savedefault" info is correct and the info file description > of savedefault is completely bogus. > > > > ------------------------------ > > Message: 11 > Date: Wed, 09 Dec 2009 13:51:23 +0100 > From: Luc MAIGNAN <luc.maignan@xxxxxxxxxxxx> > Subject: SB driver in F12 ? > To: "Community assistance, encouragement, and advice for using > Fedora." <fedora-list@xxxxxxxxxx> > Message-ID: <4B1F9D4B.2000004@xxxxxxxxxxxx> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi, > > is there any driver available under F12 for Creative Labs SB X-Fi ? > > BR > > > > ------------------------------ > > Message: 12 > Date: Wed, 9 Dec 2009 14:05:12 +0100 > From: Austin Christain <austintik12@xxxxxxxxx> > Subject: confirm > To: fedora-list@xxxxxxxxxx > Message-ID: > <6df391ae0912090505j4687130em200917fa4d92bd80@xxxxxxxxxxxxxx> > Content-Type: text/plain; charset="iso-8859-1" > > thanks guys for what you are doing out there..i need you to send me > info/material to help me with my LPI1 exam am already prepareing for > > thanks > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: https://www.redhat.com/archives/fedora-list/attachments/20091209/2674e2c9/attachment.html > > ------------------------------ > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/fedora-list > > End of fedora-list Digest, Vol 70, Issue 59 > ******************************************* 49 habitantes, 49 expertos en Windows 7. Así es Sietes, ¡Visítalo! |
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines