10-01-2008
Grub boot runlevel 3 is what I found in Google -- still depends on your boot loader etc but if you can't get that to work, tell us more. (In particular, do you have Grub, and what does its default entry look like.)
8 More Discussions You Might Find Interesting
1. HP-UX
hi,
i figured why i need to boot in MMB,some of which are missing or corrupt LABEL (LIF labeL ,i guess) on the boot disk.
To explicitly corrupt this entry i think a simple dd will work.
ok let me elaborate this issue:
i need to check this functionality.
so i have one LVM boot disk
and one... (0 Replies)
Discussion started by: mxms755
0 Replies
2. Shell Programming and Scripting
Hello
I'm working on a PHP project right now and when I try to run 'mkdir' I've been getting an error:
code:
mkdir("<full path>/test", 0700);
error:
PHP Warning: mkdir() : SAFE MODE Restriction in effect. The script whose uid is 10002 is not allowed to access <full path> owned by uid... (2 Replies)
Discussion started by: recluse8912
2 Replies
3. AIX
Hi All,
I have AIX 5.1 & I forgot the root password. I find out the solution is to boot in single-mode and remove the root password from the /etc/passwd file. My question is how to boot in single-mode? Also is there any password required when booting in this mode? (9 Replies)
Discussion started by: aldowsary
9 Replies
4. UNIX for Dummies Questions & Answers
My machine is a HP-UX 11iV2. I want to boot it in the single user mode.
Any ideas?
Regards (7 Replies)
Discussion started by: sube
7 Replies
5. SuSE
Hi All,
I used to have my suse linux(VM) server in graphic mode but not anymore since morning. I cant rolback since i loose somuch work. Any idea how to it back to normal. Thanks (6 Replies)
Discussion started by: s_linux
6 Replies
6. Solaris
Hi,
I am Solaris 9 developer and notice that the documentation does not provide a clear notion of the inherent concurrency in routines defined as "Async-Signal-Safe".
Routines defined as "MT-Safe" obviously have the best level of concurrency, compared to normal "Safe" interfaces.
I have... (1 Reply)
Discussion started by: tristan12
1 Replies
7. Solaris
I have Sun 240 server with Solaris 8 installed. I go to OBP and try to boot in single-user mode but it is getting hung in the middle and the only way to get out of this situation is by going to the LOM and resetting the server. Here is what is happening:
{0} ok boot -s
SC Alert: Host System... (18 Replies)
Discussion started by: StarSol
18 Replies
8. AIX
Hi,
I do not get to boot an IBM P5 9131-52A in normal mode. I mean I want to get rid of the SMS menu, just an automatic boot to AIX.
I installed AIX 5L V5.3. diag give me this when I run "Normal Mode Bootlist | Display Current bootlist":
******************************
CURRENT BOOTLIST... (3 Replies)
Discussion started by: rinunez
3 Replies
BOOTCTL(1) bootctl BOOTCTL(1)
NAME
bootctl - Control the firmware and boot manager settings
SYNOPSIS
bootctl [OPTIONS...] status
bootctl [OPTIONS...] list
bootctl [OPTIONS...] update
bootctl [OPTIONS...] install
bootctl [OPTIONS...] remove
DESCRIPTION
bootctl checks, updates, installs or removes the boot loader from the current system.
bootctl status checks and prints the currently installed versions of the boot loader binaries and all current EFI boot variables.
bootctl list displays all configured boot loader entries.
bootctl update updates all installed versions of systemd-boot, if the current version is newer than the version installed in the EFI system
partition. This also includes the EFI default/fallback loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is
created if there is no current entry. The created entry will be added to the end of the boot order list.
bootctl install installs systemd-boot into the EFI system partition. A copy of systemd-boot will be stored as the EFI default/fallback
loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is created and added to the top of the boot order list.
bootctl remove removes all installed versions of systemd-boot from the EFI system partition, and removes systemd-boot from the EFI boot
variables.
If no command is passed, status is implied.
OPTIONS
The following options are understood:
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
--path=
Path to the EFI System Partition (ESP). If not specified, /efi, /boot, and /boot/efi are checked in turn. It is recommended to mount
the ESP to /boot, if possible.
-p, --print-path
This option modifies the behaviour of status. Just print the path to the EFI System Partition (ESP) to standard output and exit.
--no-variables
Do not touch the EFI boot variables.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
SEE ALSO
Boot loader specification[1] systemd boot loader interface[2]
NOTES
1. Boot loader specification
https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec
2. systemd boot loader interface
https://www.freedesktop.org/wiki/Software/systemd/BootLoaderInterface
systemd 237 BOOTCTL(1)