grubby: unable to open /boot/boot.b: No such file or directory
by Thomas Rabaix
Hello,
I just update my Fedora 8 with yum, and I don't want to reboot it as I
get an error during the update. I cannot easily rescue it in
case of problem as the host is located at a remote location (datacenter).
so the /boot/boot.b is missing, the bootloader is lilo.
How can I regenerate this file ?
I have include more information about my configuration.
Thanks for your help.
Thomas
INFORMATION
============
I have a Fedora 8 :
# cat /etc/fedora-release
Fedora release 8 (Werewolf)
I had updated the system from a FC4 to Fedora 8 a month ago, I just
follow the instruction from the wiki. Everything went fine.
Now today I run the command sudo yum update , I resume the
dependencies to kernel packages :
Installing:
kernel i686 2.6.25.6-27.fc8 updates 18 M
kernel-devel i686 2.6.25.6-27.fc8 updates 5.2 M
Updating:
kernel-headers i386 2.6.25.6-27.fc8 updates 734 k
Removing:
kernel i686 2.6.23.17-88.fc7 installed 44 M
kernel-devel i686 2.6.23.17-88.fc7 installed 15 M
during the installation I get
Installing: kernel ##################### [ 20/144]
grubby: unable to open /boot/boot.b: No such file or directory
The bootloader is Lilo :
# dd if=/dev/sda obs=512 count=1 2>/dev/null|grep LILO
Binary File ... matches
my lilo.conf
#cat lilo.conf
prompt
timeout=50
default=2.6.25.6-27.fc8
boot=/dev/sda
map=/boot/map
install=/boot/boot.b
lba32
append=""
#serial=0,9600n8
image=/boot/vmlinuz-2.6.25.6-27.fc8
label=2.6.25.6-27.fc8
read-only
root=/dev/sda1
initrd=/boot/initrd-2.6.25.6-27.fc8.img
image=/boot/vmlinuz-2.6.24.7-92.fc8
label=2.6.24.7-92.fc8
read-only
root=/dev/sda1
initrd=/boot/initrd-2.6.24.7-92.fc8.img
image=/boot/bzImage-2.6.24.5-xxxx-grs-ipv4-32
label=linux
read-only
root=/dev/sda1
The default kernel is present
# ls -lsa /boot/vmlinuz-2.6.25.6-27.fc8
2052 -rw-r--r-- 1 root root 2095904 jun 13 22:47 /boot/vmlinuz-2.6.25.6-27.fc8
--
Thomas Rabaix
15 years, 10 months
FC9 boot hangs with encrypted filesystems
by Bill Davidsen
I put an encrypted f/s on an FC9 install, and the boot hung waiting for
the password. Not good, so I marked it "noauto" in fstab, but it still
hung. So I put it in automount and not in fstab and it still hangs, and
I finally took it out of everywhere and the boot process can still see it.
I want the system to boot without the filesystem, and mount it only on
demand, but by simply existing it seems to be found and validated at
boot time. Can someone tell me where the boot process is finding the
f/s? It's not used for normal operations, only for special operations by
people with the password.
Is there a way to keep the boot from asking about it until used?
--
Bill Davidsen <davidsen(a)tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
15 years, 10 months
Upgrade from Fedora 7 to 9, no GUI
by JUSTIN TAYLOR
I tested Fedora 9 on my desktop using a Live disk and it worked fine. I downloaded the full set of CD's and performed the upgrade, but now I do not have my GUI desktop. It boots in text mode.
Any ideas where to start looking?
15 years, 10 months
scrambled image with xine
by François Patte
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bonjour,
I installed xine on my laptop and if I want to whatch a dvd the image is
completely unreadable: scrambled as if the dvd was crypted.
No problem with vlc, no problem with totem-xine.
totem, installed by default, doesn't work, whatever the install I made
up to now.
Anybody has any ideas?
Thanks
- --
François Patte
UFR de mathématiques et informatique
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 44 55 35 61
http://www.math-info.univ-paris5.fr/~patte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFIY67QdE6C2dhV2JURAgeCAJ9LcwUpPppXmHtfVVZetqlwJXDmPACfeLBV
XjxAfGTcXWLIhBdrLHK0y2o=
=UwUf
-----END PGP SIGNATURE-----
15 years, 10 months
Fedora 9 + wifi + ssh stale connections
by Christof Haerens
LBS,
Since F9 I have occasional ssh connections that are no longer
responding. For now it only occurs whem I'm using my wireless connection
(intel 3945ABG). When I use my UTP connection I have no problems. There
is no problem with the wireless connection, because non ssh connections
keep working. Connections that use underlying ssl (like
vmware-server-console), are also experiencing the same problem.
Any ideas?
Kind regards.
Christof
15 years, 10 months
DC7700 + intel = no gigabit speeds
by Dr. Michael J. Chudobiak
Hi all,
I have a multiple HP DC7700s with integrated Intel ethernet adapters.
They work when the network cable is plugged into a 10/100 port on a
switch. They do not work when plugged into a 10/100/1000 port. I also
have DC7700s with integrated Broadcom chips (tg3 driver) and they work fine.
They all worked fine before the upgrade to F9.
From dmesg:
e1000e: Intel(R) PRO/1000 Network Driver - 0.2.0
e1000e: Copyright (c) 1999-2007 Intel Corporation.
...
eth0: (PCI Express:2.5GB/s:Width x1) 00:0f:fe:4a:68:37
eth0: Intel(R) PRO/1000 Network Connection
eth0: MAC: 4, PHY: 6, PBA No: 1002ff-0ff
Forcing 100 Mb operation with:
ethtool -s eth0 autoneg off speed 100 duplex full
makes everything work OK.
Forcing 1 Gb operation results in flaky or dead connections.
The auto-negotiated 1 Gb state is flaky/dead.
Now... I can force 100 Mb operation as a workaround, but does anyone
know what's causing this bug?
http://bugzilla.redhat.com/show_bug.cgi?id=453023
http://bugzilla.kernel.org/show_bug.cgi?id=10990
- Mike
15 years, 10 months
different mounts leads to different permissions/acl?
by fedora
Hoi every
we use a cvs environment, where the repository is mounted from the main
cvs-server into each participants work-space.
before fedora 9, we used cifs mounts exclusively.
with fedora 9, we started using sshfs.
this afternoon, i had the repository mounted using sshfs.
i had a failure when committing a cvs module.
cvs said:
...
Checking in module/779930879.htm;
/home/cvs/r/repository/module/779930879.htm,v <-- 779930879.htm
new revision: 1.2; previous revision: 1.1
cvs [commit aborted]: cannot rename file
/home/cvs/r/repository/module/,779930879.htm, to
/home/cvs/r/repository/module/779930879.htm,v: Operation not permitted
[cvs@myws ~/work]$
i unmounted the repository and remounted it using cifs, whereupon the
commit worked fine.
i then wanted to see, what the difference is in file permissions between
the two mount versions, and to my surprise, found none: user:group were
the same with both mounts, also the file permissions were the same.
then i tried to do manually the move cvs had complained about and got
the following:
repository cifs mounted:
[cvs@myws ~/work]$ mv /home/cvs/r/repository/module/,779930879.htm
/home/cvs/r/repository/module/779930879.htm,v
mv: try to overwrite `/home/cvs/r/repository/module/779930879.htm,v',
overriding mode 0544 (r-xr--r--)? y
[cvs@myws ~/work]$
repository sshfs mounted:
[cvs@myws ~]$ mv /home/cvs/r/repository/module/,779930879.htm
/home/cvs/r/repository/module/779930879.htm,v
mv: cannot move `/home/cvs/r/repository/module/,779930879.htm' to
`/home/cvs/r/repository/module/779930879.htm,v': Operation not permitted
[cvs@myws ~]$
i made sure, that the file i wanted to move had exactly the same
permissions as when the repository was cifs mounted: it had the same
permissions (r-xr--r--).
for the cifs mount we use the standard fedora 9 samba installation for
[home] shares:
[homes]
comment = Home Directories
browseable = no
writable = yes
; valid users = %S
; valid users = MYDOMAIN\%S
as far as i can see, the difference is minimal, but it makes cvs commit
fail, when the repository is sshfs mounted.
can somebody explain, what the difference is, and how i could
correct/work-around it?
thanks in advance.
suomi
15 years, 10 months
F8, currently offered grub update. Safe?
by Gene Heskett
With a 400GB sata drive on a sata_sil pci card and initrd loaded driver module
in the mix, which some of the grub stuff insists is /dev/sda when its
actually /dev/sdc on this system, is this so-called update safe, or will I be
reaching for install dvd's I don't have yet other than Ubuntu-8.04, when I find
it won't reboot cuz the bios does NOT see that drive, and it therefore is now
non-bootable.
So is this update safe for me?
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Gentlemen, I want you to know that I am not always right, but I am
never wrong. -Samuel Goldwyn
15 years, 10 months
Re: OAFIID:GNOME_NotificationAreaApplet
by James Corteciano
I see.. This issue must be address to the gnome and fedora developers.
Anyway I will try to switch to KDE to test if the problem is still
persistent or not.
Thanks once again.
Cheers,
-james
On Thu, Jun 26, 2008 at 3:18 AM, Robin Laing <Robin.Laing(a)drdc-rddc.gc.ca>
wrote:
> James Corteciano wrote:
>
>> Great, its working! How did you manage to find solution by deleting files
>> associated with user from /tmp ?
>>
>> -james
>>
>>
> I had this happen to me (When I used gnome) and one of my kids using switch
> user. It was frustrating and I just started to look at all the config files
> that are used by gnome.
>
> I then ended up with only the /tmp files left so I deleted them. All was
> well. :) It was a late night find so the details are not the best thing to
> remember.
>
> It seems random when it happens and free time at home is to short to test
> this for now.
>
> I have not seen this issue with kde.
>
> Now why /tmp affects your desktop is an issue that I have just thought
> could be a security issue for I don't feel any settings for an individual
> user should be stored in /tmp.
>
>
> --
> Robin Laing
>
--
Linux Registered User #380364
15 years, 10 months
