09-29-2009
Messed up my boot environment or root profile
Ok, a couple weeks ago I was fixing a cron report about perl not happy with 'locale' info (LANG and LC not set). As a result, I was experimenting with setting the correct 'locale' in several areas (like /etc/sysconfig/i18n and who knows where). Somehow after a reboot, as soon as the OS starts loading (first at populating /dev), I get the following error:
'Cannot execute binary file'.
At first I thought there was a problem with /sbin/start_udev however if I get into single user mode and then init to level 3, all scripts return the same error 'Cannot execute bianry file'. It is clear to me that I somehow messed up the root or boot environment so it doesn't know what to do with startup scripts. Can someone give me some point form instructions as to what I should systematically look at in order to fix this? I've spent two weeks reading forums/google and I'm at a loss.
Thanks a million for any/all help.
Gary.
OS: StrongBolt on Sun Cobalt Cube 3 Pro running Centos 4
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i messed up while installing freebsd into a dual os wannabe system.
Now, how do i del it( so i wouldn't get prompted to choose freebsd during boot?)so that i could try installing a different flavour of linux?
cheers:eek: (1 Reply)
Discussion started by: coffeecoolers
1 Replies
2. UNIX for Dummies Questions & Answers
All,
I want to run a non-root script as the root user with non-root environment variables with crontab. The non-root user would have environment variables for database access such as Oracle or Sybase. The root user does not have the Oracle or Sybase enviroment variables. I thought you could do... (2 Replies)
Discussion started by: bubba112557
2 Replies
3. Solaris
Hi,
I'm using solaris 8 and I need to know where I can add the following variable to have it applied to all my user Ids.
I tried to add this to /etc/profile but not working when i check with "env" command :
export PW_MATRIX=/usr/local/ccms/security/dat/.PASSWORD_MATRIX
export... (2 Replies)
Discussion started by: unclefab
2 Replies
4. Solaris
Hi friends,
On a Solaris system is the .profile executed for the user root also as it is for any normal user ?
if i have to change the PATH variable can i add it to the .profile?
and by default ther .profile is not found in the / directory. i can see it in /etc as /etc/profile.
Should i... (1 Reply)
Discussion started by: sveera
1 Replies
5. Shell Programming and Scripting
:(
1.) How is .profile and environment variable linked.?
2.) What happens when we execute a script.? (3 Replies)
Discussion started by: guhas
3 Replies
6. Solaris
I don't know where the environment config file for root user is in the Bourne shell on Solaris 10?
Can you help me, or am I helpless???? (2 Replies)
Discussion started by: Joncamp
2 Replies
7. AIX
Hello
This is the format of present profile which we use for a AIX user
export DMRUNuser ; DMRUNuser="owbrunuser_10"
export DMRUNpasswd ; DMRUNpasswd="ods$12345"
DMRUNuser&DMRUNpasswd were the environmental users which store the user id and password of a... (1 Reply)
Discussion started by: kalpana.anuga
1 Replies
8. Shell Programming and Scripting
Hello ,
i am on sles 11, and i can't figure out how can i locate my profile file,
the one that is use for setting the environment when i log in.
oracle@r200:~> cd
oracle@r200:~> pwd
/opt/oracle
oracle@r200:~> echo $SHELL
/bin/bash
oracle@r200:~>
oracle@r200:~> cat .profile
cat: .profile:... (4 Replies)
Discussion started by: tonijel
4 Replies
9. AIX
Hello.
I restore an mksysb image (AIX 5.3 TL 11) from one model to another model of Power (power 5 to power 7). Everything seems good, but I lost environment variables of at least one of a user profile. The result of the "env" command show me great differences between two servers, first of them... (2 Replies)
Discussion started by: stephnane
2 Replies
10. UNIX for Advanced & Expert Users
Hi All,
I have my own .profile file and environment file.
To execute some commands I always need to load some module using module command and change my environment files to project environment file (. /some/project/some/path/init.environ).Without changing my environment file to project file,... (2 Replies)
Discussion started by: saps19
2 Replies
reboot(1M) reboot(1M)
NAME
reboot - restart the operating system
SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments]
The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel.
Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending
loss of service. See shutdown(1M) for details.
The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On
systems, reboot may also update the boot archive as needed to ensure a successful reboot.
The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting
file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present.
Normally, the system reboots itself at power-up or after crashes.
The following options are supported:
-d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps.
-l Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot.
-n Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync
filesystems prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to
sync filesystems.
-q Quick. Reboot quickly and ungracefully, without shutting down running processes first.
The following operands are supported:
boot_arguments An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel
upon restart. The form and list of arguments is described in the boot(1M) and kernel(1M) man pages.. If the arguments are
specified, whitespace between them is replaced by single spaces unless the whitespace is quoted for the shell. If the
boot_arguments begin with a hyphen, they must be preceded by the -- delimiter (two hyphens) to denote the end of the reboot
argument list.
Example 1: Passing the -r and -v Arguments to boot
In the following example, the delimiter -- (two hyphens) must be used to separate the options of reboot from the arguments of boot(1M).
example# reboot -dl -- -rv
Example 2: Rebooting Using a Specific Disk and Kernel
The following example reboots using a specific disk and kernel.
example# reboot disk1 kernel.test/unix
/var/adm/wtmpx login accounting file
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
mdb(1), boot(1M), dumpadm(1M), fsck(1M), halt(1M), init(1M), kernel(1M), shutdown(1M), sync(1M), syslogd(1M), sync(2), uadmin(2),
reboot(3C), attributes(5)
The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown
of system services, use shutdown(1M) or init(1M) to reboot a Solaris system.
11 Apr 2005 reboot(1M)