Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2003 12:56 AM
08-21-2003 12:56 AM
the root shell to /usr/bin/sh since I view the /etc/passwd root belong to /sbin/sh ?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2003 12:57 AM
08-21-2003 12:57 AM
Re: sh
DO NOT CHANGE IT !!!!!
Massimo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2003 01:04 AM
08-21-2003 01:04 AM
SolutionNever change the /sbin/sh entry in /etc/passwd as your system will lose the ability to boot. The main reason is that /usr does not boot in single user mode. You can see the differences with the 'chatr' command.
This old posting explains more than I can type.
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x2efaa14d9abcd4118fef0090279cd0f9,00.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2003 01:16 AM
08-21-2003 01:16 AM
Re: sh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2003 01:31 AM
08-21-2003 01:31 AM
Re: sh
Quote Bill Hassel
subject: incorrectly edited the default shell for root user and now system has halted!
As you have seen, changing root's shell is a very bad idea. bash (and ksh and csh, etc) use shared libraries that are located on /usr. However, in single user mode there are no mounted filesystems except / and /stand. Leave root as /sbin/sh (which like all POSIX shells is quite compatible with bash). It's important to never login as root unless you are doing some specific system administration.
end quote
Regards,
Robert-Jan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2003 02:20 AM
08-22-2003 02:20 AM
Re: sh
As the others said, removing it is really dangerous. And if by any chance your system hangs/ disks are not mounted, you can use /sbin commands to make system recovery to some extent. I will give you one example.
Someone has renamed libdld.sl After this, no single command was working as this was the very basic library. not even ls and mv. Then rebooting the system in single user mode and using /sbin/mv for moving libdls.sl to original name made the system up. So, the contents of /sbin are very important and do not play with /sbin commands.
Regards
VJ.