|
|
Sponsored Content
Top Forums
UNIX for Advanced & Expert Users
Gave up waiting for root device.
Post 302572755 by liklstar on Saturday 12th of November 2011 12:44:22 AM
11-12-2011
|
|
8 More Discussions You Might Find Interesting
1. Linux
We are intending to protect a set of user specified files using LVM mirroring where the protected space on which the user files are stored is mirrored on an LV on a different disk. Our problem is that for a user with a custom layout has installed linux with 2 partitons for swap and / and there is... (0 Replies)
Discussion started by: kickdgrass
0 Replies
2. SuSE
hi all
waiting for a device /dev/sda2 to appear:... not found -- device nodes: console disk fb0 full hdc input kmem kmsg loop0 loop1 loop2 loop3... (1 Reply)
Discussion started by: revenna
1 Replies
3. BSD
Hello there. I installed NetBSD yesterday on an older system to try it out. Everytime I boot, I have to enter in the root device (disk) manually wd0 which then proceeds into asking to define the dump device: is the default then, the sbin/init My question is where am I supposed to... (1 Reply)
Discussion started by: septima.pars
1 Replies
4. Shell Programming and Scripting
Can Anybody help to create a pseudo-device and write a device driver for it. The pseudo-device provides a “backdoor” for gaining root access for a particular user. Instead of compiling the device driver into the kernel. Modules are object binaries that can be dynamically loaded into the kernel.
... (1 Reply)
Discussion started by: nyjilgeorge1
1 Replies
5. Homework & Coursework Questions
Problem statement.
In this part of the assignment, delegates will create a pseudo-device and write a device driver for it. The pseudo-device provides a “backdoor” for gaining root access for a particular user. Instead of compiling the device driver into the kernel, delegate will create a module.... (1 Reply)
Discussion started by: nyjilgeorge1
1 Replies
6. Debian
I have a Debian OpenBox that boots from any usb port. The Debian LXDE will only boot from one specific port. It needs to look at all of them to find and be root, and mount the root filesystem by UUID. Both are full installs to 16GB flash drives.
That is not being done.
It says during boot... (0 Replies)
Discussion started by: patrick013
0 Replies
7. Solaris
I added in the configuration file of a whole root zone the following device match entries:
<device match="/dev/rmt/*"/>
<device match="/dev/sg/*"/>
after the reboot the zone was able to see all the devices of its global zone, and let under /dev/rmt and /dev/sg the special files created with... (1 Reply)
Discussion started by: hugo_perez
1 Replies
8. Ubuntu
I cannot access or boot from my C drive. I'm running Zorin 9 and the drive is a Samsung SSD. The disk was encrypted on install, and that has not given me any problems before.
When I start the system it gets to the memory test page, and does not then load the password prompt, which it used to.... (1 Reply)
Discussion started by: David4321
1 Replies
LEARN ABOUT FREEBSD
reboot
REBOOT(8) BSD System Manager's Manual REBOOT(8) NAME
reboot, halt, fastboot, fasthalt -- stopping and restarting the system SYNOPSIS
halt [-lnpq] [-k kernel] reboot [-dlnpq] [-k kernel] fasthalt [-lnpq] [-k kernel] fastboot [-dlnpq] [-k kernel] DESCRIPTION
The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and, respectively, halt or restart the system. The action is logged, including entering a shutdown record into the user accounting database. The options are as follows: -d The system is requested to create a crash dump. This option is supported only when rebooting, and it has no effect unless a dump device has previously been specified with dumpon(8). -k kernel Boot the specified kernel on the next system boot. If the kernel boots successfully, the default kernel will be booted on successive boots, this is a one-shot option. If the boot fails, the system will continue attempting to boot kernel until the boot process is interrupted and a valid kernel booted. This may change in the future. -l The halt or reboot is not logged to the system log. This option is intended for applications such as shutdown(8), that call reboot or halt and log this themselves. -n The file system cache is not flushed. This option should probably not be used. -p The system will turn off the power if it can. If the power down action fails, the system will halt or reboot normally, depending on whether halt or reboot was called. -q The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n option is not specified). This option should probably not be used. The fasthalt and fastboot utilities are nothing more than aliases for the halt and reboot utilities. Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending doom and cleanly terminating specific programs. SEE ALSO
getutxent(3), boot(8), dumpon(8), nextboot(8), savecore(8), shutdown(8), sync(8) HISTORY
A reboot utility appeared in Version 6 AT&T UNIX. BSD
October 11, 2010 BSD