Sponsored Content
Full Discussion: Unable to boot Fedora 10
Operating Systems Linux Red Hat Unable to boot Fedora 10 Post 302475380 by Praveen_218 on Sunday 28th of November 2010 11:51:30 AM
Old 11-28-2010
Hi Vinorda,
I could see that your RedHat /boot is available under /dev/sdb5 (hoping its data has not been overwritten); Please try to mount the same as below:
Code:
mkdir /mnt/redhat;
mount -t ext3 /dev/sdb5 /mnt/redhat

You may use either Ubuntu or your Fedora-1 (preferably) to execute the above command.

Now copy that /mnt/redhat/grub/grub.conf and save the same somewhere as rehat9_grub.conf.

You now need to copy the same file from your fedora-10 (i.e. /boot/grub/grub.conf) and save that too somethis as fedora_grub.conf.

Now could you please post back here with there two files again?
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Fedora Core 3 boot diskette

I want to upgrade from Red Hat Linux 8.0 to Fedora Core 3. I have already downloaded FC3 on CD's. My current config. on my PC is that I have Win XP on primary hard drive and Red Hat 8.0 on another hard drive. Because my Compaq Presario reserves the first cylinder of my primary hard drive, I... (1 Reply)
Discussion started by: Mark McWilliams
1 Replies

2. Linux

Dual Boot Win XP And Fedora with Fedora Installed First

Hi everyone, I hope this question goes here. Anyways, I have a unique situation where my friend's comp has Fedora installed and wants to add Win XP as a dual boot without formatting the drive. Is it possible to create a partition on the current hard drive and then install win xp? I couldn't find... (4 Replies)
Discussion started by: eltinator
4 Replies

3. UNIX for Advanced & Expert Users

Lesson Learned: Dual boot XP and Fedora 9

This post captures my recent experience in getting my Dell XPS Gen 3 to support dual boot of Windows XP (Professional) and the Fedora 9 Linux distribution. I searched quite a bit on the internet and found, of course, a variety of opinions regarding how to setup this type (dual boot) of... (1 Reply)
Discussion started by: rlandon@usa.net
1 Replies

4. Linux

How to boot Fedora 8 from USB

Hi, friends, can anyone suggest me how to boot fedora 8 from USB flash drive? thanks. :confused: (3 Replies)
Discussion started by: MULTIVERSE
3 Replies

5. Red Hat

boot floppy for fedora 13

Is there a way to create a boot floppy for a fedora 13 system? Rescue disk image from the official boot.iso is too big. (1 Reply)
Discussion started by: druidmatrix
1 Replies

6. Red Hat

fedora grub help, moving to tri boot (XP, ubuntu, fedora soemething)

I will shortly be adding a fedora flavor to my devel box. I currently have XP (installed first on an ssd), ubuntu 10.04 (installed second on the first partition of a platter drive), and I want to add either Cent or SL on the second partition of the platter drive. I will probably also want to... (0 Replies)
Discussion started by: LMHmedchem
0 Replies

7. Red Hat

Kernel can not boot after upgrade on Fedora OS 15.

Hello, everyone. I am using Fedora 15, and want to upgrade to version 16. I follow the official link Upgrading Fedora using yum - FedoraProject to upgrade my OS by the following command: yum update kernel* --releasever=16 yum groupupdate Base --releasever=16 reboot After reboot, OS... (2 Replies)
Discussion started by: 915086731
2 Replies

8. Red Hat

Unable to boot after updating to kernel-3.1.4-1 in fedora 16

hi guys, I was using kernel-3.1.2-1 in fedora 16. then updated to kernel-3.1.4-1. after reboot now grub shows command prompt instead of boot menu. i tried to load manually with: set root=(hd0,msdos3) linux /vmlinuz-3.1.4-1.fc16.x86_64 initrd /initramfs-3.1.4-1.fc16.x86_64.imgbut in the middle... (0 Replies)
Discussion started by: majid.merkava
0 Replies

9. Red Hat

Fedora 17 - No video after boot

Hi, I'm new to the Linux world and I'm having issues. Screen goes blank after Fedora boots up. I can see the POST and Fedora Grub screen but afterwards, goes blank. I believe I installed something but I cant remember what....its been a couple days. (0 Replies)
Discussion started by: gps1976
0 Replies
ns_sched(3aolserver)					    AOLserver Built-In Commands 				      ns_sched(3aolserver)

__________________________________________________________________________________________________________________________________________________

NAME
ns_after, ns_cancel, ns_pause, ns_resume, ns_schedule_daily, ns_schedule_proc, ns_schedule_weekly, ns_unschedule_proc - commands SYNOPSIS
ns_after seconds {script | procname ?args?} ns_cancel id ns_pause id ns_resume id ns_schedule_daily ?-thread? ?-once? hour minute {script | procname ?args?} ns_schedule_proc ?-thread? ?-once? interval {script | procname ?args?} ns_schedule_weekly ?-thread? ?-once? day hour minute {script | procname ?args?} ns_unschedule_proc id _________________________________________________________________ DESCRIPTION
ns_after run the specified script or procedure after the specified number of seconds ns_after returns an id which can be used with the ns_pause, ns_cancel and ns_resume apis. ns_cancel stops the scheduled running of the id returned by an ns_after returns 1 if unscheduled 0 if the script of procedure couldn't be unscheduled ns_pause pauses the scheduled running of the id returned by an ns_after returns 1 if paused, 0 if the script of procedure couldn't be paused ns_resume resumes the scheduled running of the id returned by an ns_after returns 1 if resumed, 0 if the script of procedure couldn't be resumed ns_schedule_daily ns_schedule_daily runs the specified Tcl script or procedure (procname) once a day at the time specified by hour and minute. The hour can be from 0 to 23, and the minute can be from 0 to 59. Specify -thread if you want a thread created to run the procedure. This will allow the scheduler to continue with other scheduled procedures. Specifying -thread is appropriate in situations where the script will not return immediately, such as when the script performs network activity. Specify -once if you want the script to run only one time. The default is that the script will be re-scheduled after each time it is run. ns_schedule_daily returns an id number for the scheduled procedure that is needed to stop the scheduled procedure with ns_unsched- ule_proc. ns_schedule_proc ns_schedule_proc runs the specified Tcl script or procedure (procname) at an interval specified by interval. The interval is the number of seconds between runs of the script. Specify -thread if you want a thread created to run the procedure. This will allow the scheduler to continue with other scheduled procedures. Specifying -thread is appropriate in situations where the script will not return immediately, such as when the script performs network activity. Specify -once if you want the script to run only one time. The default is that the script will be re-scheduled after each time it is run. ns_schedule_proc returns an id number for the scheduled procedure that is needed to stop the scheduled procedure with ns_unsched- ule_proc. ns_schedule_weekly ns_schedule_weekly runs the specified Tcl script or procedure (procname) once a week on the day specified by day and the time speci- fied by hour and minute. The day can be from 0 to 6, where 0 represents Sunday. The hour can be from 0 to 23, and the minute can be from 0 to 59. Specify -thread if you want a thread created to run the procedure. This will allow the scheduler to continue with other scheduled procedures. Specifying -thread is appropriate in situations where the script will not return immediately, such as when the script performs network activity. Specify -once if you want the script to run only one time. The default is that the script will be re-scheduled after each time it is run. ns_schedule_weekly returns an id number for the scheduled procedure that is needed to stop the scheduled procedure with ns_unsched- ule_proc. ns_unschedule_proc id ns_unschedule_proc stops a scheduled procedure from executing anymore. The scheduled procedure to be stopped is identified by its id, which was returned by the ns_schedule* function that was used to schedule the procedure. EXAMPLES
ns_after ns_cancel ns_pause ns_resume This example illustrates a web interface used to manage jobs. Depending on the action provided a job can be created, cancelled, paused or resumed. set action [ns_queryget action] set job [ns_queryget job] switch $action { create { set job [ns_after 10 [ns_queryget script]] ns_puts "Job created with id: $job" } cancel { if {[ns_cancel $job]} { ns_puts "Job $job cancelled" } else { ns_puts "Job $job not cancelled" } } pause { if {[ns_pause $job]} { ns_puts "Job $job paused" } else { ns_puts "Job $job not paused } } resume { if {[ns_resume $job]} { ns_puts "Job $job resumed" } else { ns_puts "Job $job couldn't be resumed" } } default { ns_puts "Invalid action $action" } } ns_schedule_daily This example defines a script called rolllog that uses ns_accesslog to roll the access log to a file with an extension containing the current date. The ns_schedule_daily function is used to execute the rolllog script on a daily basis. # Script to roll and rcp log file to host "grinder" proc rolllog {} { set suffix [ns_strftime "%y-%m-%d"] set new [ns_accesslog file].$suffix ns_accesslog roll $new exec rcp $new grinder:/logs/[file tail $new] } # Schedule "rolllog" to run at 3:30 am each morning ns_schedule_daily -thread 3 30 rolllog ns_schedule_proc proc dosomething blah { ns_log Notice "proc with arg '$blah'" } ns_schedule_proc 10 dosomething $arg1 SEE ALSO
KEYWORDS
schedule pause resume unschedule cancel after AOLserver 4.0 ns_sched(3aolserver)
All times are GMT -4. The time now is 03:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy