> From: Harald Hoyer <harald.hoyer@xxxxxxxxx> > You might want to edit /etc/grub.conf in rescue and remove "quiet" and > "rhgb" and add "rdinit rd_NO_PLYMOUTH" to the Kernel command line. I will gladly do it but it seam to be a non editable file, if there is away please let me know. > > On Wednesday, July 21, 2010, Vincent Onelli <vonelli@xxxxxxxxxxxxx> wrote: > >> From: "Darr" <darr@xxxxxxxx> > > > >> >> Hmmmm... if grub's boot menu never appears, how do you know > >> >> there's only 1 kernel listed in it? > >> >> > >> >> If grub's boot menu never appears, how do you choose to run > >> >> windows or fedora? > >> >> > >> > By looking in the directory /lib/modules, while I am in the command > >> > >> Just because there is only one subdirectory in /lib/modules doesn't > >> mean there is (or was, now) only one kernel listed in the boot menu. > >> > >> > >> > line in rescue mode. After reinstall again I now have in this > >> > directory only 2.6.33.3-85.fc13.i.686.PAE if run dracut it > >> > doesn't find because the PAE extension. > >> > >> So you reinstalled, but it still won't boot from the initial > >> kernel that anaconda gives you. What messages do > >> you see when you remove the rhgb and quiet from > >> the kernel arguments at boot time? > >> i.e. we don't know that the initramfs file is bad... > >> that was something someone said *could* be wrong. > >> > >> Still, if you've convinced yourself that's the problem and want to > >> remake that file system, just don't use the $(uname -r) variable. > >> Run e.g. > >> # mv /boot/initramfs-2.6.33.3-85.fc13.i.686.PAE.img > >> /boot/initramfs-2.6.33.3-85.fc13.i.686.PAE.img.old > >> > >> # dracut /boot/initramfs-2.6.33.3-85.fc13.i.686.PAE.img > >> 2.6.33.3-85.fc13.i.686.PAE > > dracut ran OK > > rebooted, still no change > >> > >> instead (both of those commands should be single lines that > >> begin with the root-access prompt '#'... the email programs wrap > >> them at arbitrary lengths... typically between 65 and 72 characters in > >> length). > >> > >> The first command 'moves' the original file to having the > >> extension "old" so you can compare it to the new one > >> after it's created by the second command. > >> > >> What size is the current /boot/initramfs-2.6.33.3-85.fc13.i.686.PAE.img > >> file, by the way? > >> > > The new 11883506 > > The old 11883371 > > > > -- > > users mailing list > > users@xxxxxxxxxxxxxxxxxxxxxxx > > To unsubscribe or change subscription options: > > https://admin.fedoraproject.org/mailman/listinfo/users > > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > > > > ------------------------------ > > Message: 13 > Date: Tue, 20 Jul 2010 23:09:21 -0700 > From: Gordon Messmer <yinyang@xxxxxxxxx> > Subject: Re: Verizon and Comcast email challenges > To: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx> > Message-ID: <4C468F11.7060304@xxxxxxxxx> > Content-Type: text/plain; charset=UTF-8; format=flowed > > On 07/20/2010 02:39 PM, Max Pyziur wrote: > > > > Recently (over the last six months?), Verizon has blocked smtp requests on > > port 25 to our mail server hosted on our machine (brama.com). It seems > > that this isn't just our box, but a policy that Verizon has implemented > > widely, forcing Verizon patrons to use someuser@xxxxxxxxxxx to send > > outbound email, or use a different port (587?). > > That's fairly common for residential service. More ISPs are doing so, > and it's good practice for limiting spam. If you run an SMTP server, > ask your ISP for a business-class account. You'll pay more, but you > won't have filtered access. I don't think there's any other way for you > to run an MX for your domain on one of their lines. > > If you want to allow users to send email through your server, you should > definitely run an SMTP server on port 587. It should require SMTP AUTH > for relay privileges. You will probably need to configure your server > to use Verizon's SMTP servers as "smart hosts" to relay your mail. > > > More recently, recipients with @verizon.net cannot receive emails from our > > hosted domain names. As yet, I only have bare knowledge with the > > indication that the Verizon problem rests with finding an answer at the > > following website: > > Sender Policy Framework > > http://www.openspf.org/ > > That's possible. You did publish an SPF+ record for brama.com. What > leads you to believe that this is the source of the problem? > > > ------------------------------ > > Message: 14 > Date: Tue, 20 Jul 2010 23:13:27 -0700 > From: Gordon Messmer <yinyang@xxxxxxxxx> > Subject: Re: PostgreSql question > To: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx> > Message-ID: <4C469007.5000700@xxxxxxxxx> > Content-Type: text/plain; charset=UTF-8; format=flowed > > On 07/20/2010 05:23 PM, Nermin Celik wrote: > > I've downloaded PostgreSql from http://yum.pgsqlrpms.org/8.3/, however > > when I try access it from the termnial line it doesn't work and gives > > the following warning. > > Is there a reason you did that, when Fedora provides PostgreSQL packages? > > # yum install postgresql postgresql-server > # chkconfig postgresql on > # service postgresql initdb > # service postgresql start > > Running Fedora's packages means that you'll get updates via 'yum update' > when there are bugfixes or security fixes available, and makes it easier > to get help here on the list since you'll be using the same packages > everyone else does. > > > ------------------------------ > -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
