WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: BusyBox shell  (Read 144 times)

Offline kmhill

  • WikiUser
  • *
  • Posts: 17
BusyBox shell
« on: August 25, 2017, 05:29:01 PM »
Hello folks, I've been doing some digging into BusyBox and have a question or two.

I've noticed that in Linux systems, that /bin/sh is a symbolic link to a shell program. In looking in RasPi TC, I see that it's a symbolic link to BusyBox. But then in reading about BusyBox and playing with the BusyBox configuration tool I see that BusyBox can be built along with the source code for some variant of ash or for hush.

In looking about the forum I see that for the RasPi TC, BusyBox is configured and built with ash. Now I'm curious if there is simple way to figure out that it's actually ash? Just curious.

Krista

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 5385
Re: BusyBox shell
« Reply #1 on: August 25, 2017, 06:31:36 PM »
Hi kmhill
... I see that BusyBox can be built along with the source code for some variant of ash or for hush.

 ... Now I'm curious if there is simple way to figure out that it's actually ash? Just curious.

If you enter  busybox  at the command line, it will print out a list of everything that has been compiled into it. That list currently
includes ash.

Offline kmhill

  • WikiUser
  • *
  • Posts: 17
Re: BusyBox shell
« Reply #2 on: August 25, 2017, 08:18:58 PM »
Ah, of course, thank you!