View previous topic :: View next topic |
Author |
Message |
mr sk Apprentice
Joined: 15 Jul 2004 Posts: 174 Location: Hollis
|
Posted: Wed Sep 01, 2004 12:20 pm Post subject: Very Odd no grub.conf, Way to many symlinks from boot->bo |
|
|
[code]lrwxrwxrwx 1 root root 1 Jul 27 20:26 /boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot/boot -> .[/code]
also, if i dont type the " -l " on ls, I get
>to many levels of symbolik links.
Also, I can't find my grub. /boot/..? _________________ "In times of universal deceit, telling the truth becomes a *revolutionary act" - George Orwell.
www.intrusionsec.com [root wars (free)] |
|
Back to top |
|
|
hjnenc Veteran
Joined: 15 Aug 2004 Posts: 1599 Location: Vienna, Austria
|
Posted: Wed Sep 01, 2004 12:24 pm Post subject: |
|
|
Did you mount your boot partition? |
|
Back to top |
|
|
mr sk Apprentice
Joined: 15 Jul 2004 Posts: 174 Location: Hollis
|
Posted: Wed Sep 01, 2004 12:59 pm Post subject: |
|
|
my system runs fine. I just wanted to set my grub timeout less than 30 seconds..
im not sure.
[code]# /etc/fstab: static file system information.
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.14 2003/10/13 20:03:38 azarah Exp $
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail and tail freely.
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda1 /boot ext2 noauto,noatime 1 1
/dev/hda3 / xfs noatime 0 0
/dev/hda2 none swap sw 0 0
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0
#/dev/fd0 /mnt/floppy auto noauto 0 0
# NOTE: The next line is critical for boot!
none /proc proc defaults 0 0
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not populated with files)
# Adding the following line to /etc/fstab should take care of this:
none /dev/shm tmpfs defaults 0 0
[/code] _________________ "In times of universal deceit, telling the truth becomes a *revolutionary act" - George Orwell.
www.intrusionsec.com [root wars (free)] |
|
Back to top |
|
|
jammin Guru
Joined: 21 Jun 2004 Posts: 340
|
Posted: Wed Sep 01, 2004 1:35 pm Post subject: |
|
|
I had this problem yesterday:
As hjnenc says
Quote: | Did you mount your boot partition? |
Should do it, then try to edit your /boot/grub/grub.conf |
|
Back to top |
|
|
mr sk Apprentice
Joined: 15 Jul 2004 Posts: 174 Location: Hollis
|
Posted: Wed Sep 01, 2004 1:52 pm Post subject: |
|
|
would i have to mount it everyime my system restarts..i dont get it?
i mean i understand what your saying, but i don't understand why its working the way it is.
im going to try and mount boot now...
but it must be mounting it when it starts because it does properlly startup, no errors and grub works fine. bootspahs, imgz, etc..... _________________ "In times of universal deceit, telling the truth becomes a *revolutionary act" - George Orwell.
www.intrusionsec.com [root wars (free)] |
|
Back to top |
|
|
jammin Guru
Joined: 21 Jun 2004 Posts: 340
|
Posted: Wed Sep 01, 2004 2:23 pm Post subject: |
|
|
No you would not, the /boot partion is used for just that, booting. I think it then umounts itself (it must really)
You would only need to mount it again if you wanted to change your grub or add a new kernel image in there. (there are probs many more reasons, im still a n00b).
By the way, when i was mounting /boot, i was forgeting to umount it. This caused gnome to freeze when i attempted to log out (at least i think this was it) so remember to umount it before restarting.
Hope this helps |
|
Back to top |
|
|
Cryofix n00b
Joined: 05 Jun 2004 Posts: 20
|
Posted: Wed Sep 01, 2004 2:41 pm Post subject: |
|
|
I think that its a security precaution, if somone was to gain access to your system without being root they would have direct access to your kernel file which could possibly be used to inject a hack in the kernel.
I also think its a saftey thing, you cant delete what is not mounted, either if you have been hacked or if you mistype a command.
these are my theories and im stickin to them. |
|
Back to top |
|
|
jammin Guru
Joined: 21 Jun 2004 Posts: 340
|
Posted: Wed Sep 01, 2004 2:47 pm Post subject: |
|
|
That make sense to me. |
|
Back to top |
|
|
DaveArb Guru
Joined: 29 Apr 2004 Posts: 510 Location: Texas, USA
|
Posted: Wed Sep 01, 2004 2:49 pm Post subject: |
|
|
WRT: /boot/boot/boot and so on...
If you mount /boot, and look in it in a long listing, you'll see that by default, /boot/boot is a link to '.'. Therefore, you can `cd boot` for as long as patience or system pathname length hold out.
Reason for this is no doubt some old bit of software that defaulted to looking for files in /boot/boot, for the same files that are more commonly placed in /boot now. It's an elegant fix.
WRT: default unmounted boot partition
I agree with Cryofix, "I also think its a saftey thing, you cant delete what is not mounted". The files in /boot are rarely accessed by a user anyway.
If it bugs the heck out of you though, just set the partition to automatically mount. It's all about choice.
Dave |
|
Back to top |
|
|
mr sk Apprentice
Joined: 15 Jul 2004 Posts: 174 Location: Hollis
|
Posted: Wed Sep 01, 2004 10:43 pm Post subject: |
|
|
Thanks all for the responses!! makes sense!
gotta love gentoo _________________ "In times of universal deceit, telling the truth becomes a *revolutionary act" - George Orwell.
www.intrusionsec.com [root wars (free)] |
|
Back to top |
|
|
|