Sponsored Content
Full Discussion: Linux booting options
Operating Systems Linux Debian Linux booting options Post 302744143 by fpmurphy on Friday 14th of December 2012 12:18:18 AM
Old 12-14-2012
One way might be to define a separate runlevel for the specialized software. Or set up the OS to run in kiosk mode.
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

booting up in Redhat Linux 7.1

When I created the redhat installation, I configured it to boot directly into GNOME, but now I want it to boot into the shell login screen. How can I change that? Thanks. (1 Reply)
Discussion started by: dangral
1 Replies

2. Solaris

Dual booting Linux and Solaris

Ok, so I'm a bit new to the whole Unix/Linux thing, but I'm no stranger to dual booting... However, the problem that I am having is that I am unable to create a dual boot with Unix (in this case I's using Sun Solaris 9.0 x86) and for linux either RH 9 or Mandrake 9.1, but for the purpose of just... (1 Reply)
Discussion started by: AndroidI6
1 Replies

3. Linux

Booting Linux from an USB stick

I got Puppy linux and installed it on a usb stick. In the BIOS i selected to boot from USB-FDD but it goes to my HD and ignores the USB stick, What going on ?? (2 Replies)
Discussion started by: perleo
2 Replies

4. UNIX for Dummies Questions & Answers

A Big Problem in LINUX Booting

i have some problem in linux booting will u please help me the problem is i was using federo core 1 on my system everything was fine i made one entry in /etc/fstab file for accessing E drive of WINDOWS XP in that i had given file system as VFAT after rebooting system it was not... (1 Reply)
Discussion started by: great_indian
1 Replies

5. Ubuntu

Problem while booting linux

Hi all, We are using linux Redhat 9. While booting the server, it says /proc not mounted and it says "Segmentation fault" and doesn't continue with booting. Basically, it started while we inserted a pen drive and removed it without mounting and un mounting it. After removing the pen drive &... (1 Reply)
Discussion started by: mjdarm
1 Replies

6. Filesystems, Disks and Memory

Problem booting a linux (RAID5)

Hello, we have a problem with our system, a machine with a RAID5: - We can boot the system from CD only, if we try to boot from hard-disk the GRUB seems to be "freezed". What is the difference, why we can boot from CD if something is wrong? - Allways we retreive an error like: "raid array is... (6 Replies)
Discussion started by: aristegui
6 Replies

7. Hardware

Linux not booting when keyboard is unplugged

Hello, I have two linux pc towers and both works normally. I have only one keyboard. When i plug the keyboard into the first pc, I connect to 2nd pc remotely and send reboot command. Second pc stucks on black screen. Could you please guide me what I should do? Thanks in advance Boris (6 Replies)
Discussion started by: baris35
6 Replies
RUNLEVEL(8)                                                          runlevel                                                          RUNLEVEL(8)

NAME
runlevel - Print previous and current SysV runlevel SYNOPSIS
runlevel [options...] OVERVIEW
"Runlevels" are an obsolete way to start and stop groups of services used in SysV init. systemd provides a compatibility layer that maps runlevels to targets, and associated binaries like runlevel. Nevertheless, only one runlevel can be "active" at a given time, while systemd can activate multiple targets concurrently, so the mapping to runlevels is confusing and only approximate. Runlevels should not be used in new code, and are mostly useful as a shorthand way to refer the matching systemd targets in kernel boot parameters. Table 1. Mapping between runlevels and systemd targets +---------+-------------------+ |Runlevel | Target | +---------+-------------------+ |0 | poweroff.target | +---------+-------------------+ |1 | rescue.target | +---------+-------------------+ |2, 3, 4 | multi-user.target | +---------+-------------------+ |5 | graphical.target | +---------+-------------------+ |6 | reboot.target | +---------+-------------------+ DESCRIPTION
runlevel prints the previous and current SysV runlevel if they are known. The two runlevel characters are separated by a single space character. If a runlevel cannot be determined, N is printed instead. If neither can be determined, the word "unknown" is printed. Unless overridden in the environment, this will check the utmp database for recent runlevel changes. OPTIONS
The following option is understood: --help Print a short help text and exit. EXIT STATUS
If one or both runlevels could be determined, 0 is returned, a non-zero failure code otherwise. ENVIRONMENT
$RUNLEVEL If $RUNLEVEL is set, runlevel will print this value as current runlevel and ignore utmp. $PREVLEVEL If $PREVLEVEL is set, runlevel will print this value as previous runlevel and ignore utmp. FILES
/run/utmp The utmp database runlevel reads the previous and current runlevel from. SEE ALSO
systemd(1), systemd.target(5), systemctl(1) systemd 237 RUNLEVEL(8)
All times are GMT -4. The time now is 03:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy