[uClinux-dev] setting up the network
Hello all, Can someone please tell me the general instructions on setting up the network in uClinux for any platform? I am using h8/edosk platform for my application. Thanks and Regards Kailash - You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
RE: [uClinux-dev] setting up the network
Quoth kailash toshniwal: > Can someone please tell me the general instructions on setting > up the network in uClinux for any platform? Much like any other linux system: you run ifconfig and/or a DHCP client. Getting DHCP working isn't trivial, since most common DHCP clients tend to use scripts, which aren't supported by the default sash shell. But there's probably some available that don't, or you could switch to a different shell. Or just go with a static IP. ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] setting up the network
Getting DHCP working isn't trivial, since most common DHCP clients tend to use scripts, which aren't supported by the default sash shell. sash does not support scripts ? That does not seem very useful. Do you know a document that explains what shells provide which capabilities ? Is sash a (or the only) shell that does not need link files (and thus reloading of the "busybox" executable) when calling a command ? Is it a real problem to use (e.g.) bash in busybox ? -Michael ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] setting up the network
On Thu 3 Apr 2008 23:27, kailash toshniwal pondered: > Hello all, > Can someone please tell me the general instructions on setting up the > network in uClinux for any platform? http://docs.blackfin.uclinux.org/doku.php?id=setting_up_the_network Should get you most of the way there. ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
RE: [uClinux-dev] setting up the network
Quoth Michael Schnell: > sash does not support scripts ? That does not seem very useful. > Do you know a document that explains what shells provide which > capabilities ? Looking at the docs for each shell is how I did it. Note that what I said is slightly misleading -- you can write "scripts" and run them in sash, but it does not support input/output redirection nor parameters, which limits their usefulness significantly. I usually use busybox msh, since that does support all of that, but it has less integrated commands so you need more in your bindir. But yes, those can also be busybox commands if you like. > Is sash a (or the only) shell that does not need link files (and thus > reloading of the "busybox" executable) when calling a command ? I think you have completely the wrong end of the stick there. Sash is unrelated to busybox and doesn't get any magical benefit from things compiled into busybox. What it does have going for it is simplified functionality of a lot of bintools built directly into it, so they're internal commands rather than external ones. > Is it a real problem to use (e.g.) bash in busybox ? Bash requires an MMU, last time I checked (because it requires full glibc, which requires an MMU). And again it's unrelated to busybox. ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] setting up the network
you can write "scripts" and run them in sash, but it does not support input/output redirection nor parameters, which limits their usefulness significantly. OK I do understand now. I usually use busybox msh, since that does support all of that, but it has less integrated commands so you need more in your bindir. But yes, those can also be busybox commands if you like. OK, as with my project, I am not tight with RAM or flash resources thus I can use msh. Is sash a (or the only) shell that does not need link files (and thus reloading of the "busybox" executable) when calling a command ? What it does have going for it is simplified functionality of a lot of bintools built directly into it, so they're internal commands rather than external ones. I see. "Internal commands" is why there are no symlinks for the commands and that is why no executable needs to be loaded (which is beneficial with those non-MMU architectures that can't share code pages between multiple "loaded" processes). Bash requires an MMU, last time I checked (because it requires full glibc, which requires an MMU). And again it's unrelated to busybox. I see, Thus supposedly msh is the way to go :) Now finally back to the original question: can you explain what is required to activate DHCP ? Thanks a lot -Michael ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] setting up the network
Gavin Lambert wrote: > > Is it a real problem to use (e.g.) bash in busybox ? > > Bash requires an MMU, last time I checked (because it requires full glibc, > which requires an MMU). And again it's unrelated to busybox. I'm pretty sure Bash works with uClibc just fine - I've used it on an x86 uClibc build. However, Bash is large and slow and not recommended for a small device, especially with no MMU. But it should work, if you don't mind that. Busybox comes with several shell choices, not just msh. I use msh because it's the smallest, but it does have a few bugs and many limitations. -- Jamie ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] setting up the network
Jamie Lokier wrote: I'm pretty sure Bash works with uClibc just fine ... Even with static linking ? Built into busybox or as a dedicated executable ? Do you suggest that I should try to use bash in a project with enough RAM and flash ? -Michael ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] setting up the network
Jivin Michael Schnell lays it down ... > Jamie Lokier wrote: > >I'm pretty sure Bash works with uClibc just fine ... > Even with static linking ? Bash will work with uClibc, but it needs an MMU. Cheers, Davidm > Built into busybox or as a dedicated executable ? > > Do you suggest that I should try to use bash in a project with enough RAM > and flash ? > -Michael > > ___ > uClinux-dev mailing list > uClinux-dev@uclinux.org > http://mailman.uclinux.org/mailman/listinfo/uclinux-dev > This message was resent by uclinux-dev@uclinux.org > To unsubscribe see: > http://mailman.uclinux.org/mailman/options/uclinux-dev > -- David McCullough, [EMAIL PROTECTED], Ph:+61 734352815 Secure Computing - SnapGear http://www.uCdot.org http://www.cyberguard.com ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] setting up the network
Bash will work with uClibc, but it needs an MMU. I don't have one. OTOH, I don't understand. uCLinux does not handle the MMU and a user land program can't do that on itself. So it should not matter it any MMU hardware is present. -Michael ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
RE: [uClinux-dev] setting up the network
Quoth Michael Schnell: > I don't have one. OTOH, I don't understand. uCLinux does not handle the > MMU and a user land program can't do that on itself. So it should not > matter it any MMU hardware is present. Without an MMU, userland constructs such as fork()s and certain kinds of mmap() won't work. So unless bash has been patched to use alternate constructs in the absence of an MMU, it won't work either. ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] setting up the network
Without an MMU, userland constructs such as fork()s and certain kinds of mmap() won't work. So unless bash has been patched to use alternate constructs in the absence of an MMU, it won't work either. Right you are. But as with uCLinux, the Kernel does not provide fork(), and so a uCLinux compatible libC will not provide the appropriate header. Thus IMHO a program (like bash, as you seem to assume) that calls that function can't be compiled. -Michael ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] setting up the network
Michael Schnell wrote: > >Without an MMU, userland constructs such as fork()s and certain kinds of > >mmap() won't work. So unless bash has been patched to use alternate > >constructs in the absence of an MMU, it won't work either. > > > Right you are. > > But as with uCLinux, the Kernel does not provide fork(), and so a > uCLinux compatible libC will not provide the appropriate header. Thus > IMHO a program (like bash, as you seem to assume) that calls that > function can't be compiled. Actually, calls to fork() can be compiled, but it is a stub which returns ENOSYS. This is occasionally annoying. A compile/link-time warning, at least, would have been nice. -- Jamie ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] setting up the network
But as with uCLinux, the Kernel does not provide fork(), and so a uCLinux compatible libC will not provide the appropriate header. Thus IMHO a program (like bash, as you seem to assume) that calls that function can't be compiled. Actually, calls to fork() can be compiled, but it is a stub which returns ENOSYS. This is occasionally annoying. A compile/link-time warning, at least, would have been nice. I see. So I suppose it will compile but not run with uCLinux. -Michael ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] setting up the network
Getting DHCP working isn't trivial, since most common DHCP clients tend to use scripts, which aren't supported by the default sash shell. But there's probably some available that don't, or you could switch to a different shell. Or just go with a static IP. I just do dhcpcd & (in the command line or the "rc" script, no "special dhcp" script involved). Do you suggest that some miniature shell does not acknowledge the "&" ? -Michael ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] setting up the network
Michael Schnell wrote: > >Getting DHCP working isn't trivial, since most common DHCP clients tend to > >use scripts, which aren't supported by the default sash shell. But there's > >probably some available that don't, or you could switch to a different > >shell. Or just go with a static IP. > > I just do > > dhcpcd & > > (in the command line or the "rc" script, no "special dhcp" script involved). > > Do you suggest that some miniature shell does not acknowledge the "&" ? I think it's more that, for example, udhcpc, _runs_ scripts in order to bring up/down the network interface. The scripts do things like edit /etc/resolv.conf and call ifconfig/route. Of course, they don't really need to be scripts. You can write a small C program to do the same thing. -- Jamie ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] setting up the network
I think it's more that, for example, udhcpc, _runs_ scripts in order to bring up/down the network interface. The scripts do things like edit /etc/resolv.conf and call ifconfig/route. Right you are ! I took a closer look and see that there is a file /usr/share/udhcpc/default.script that seems to be used by the dhcp client daemon. -Michael ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
Re: [uClinux-dev] setting up the network
Jamie Lokier wrote: I think it's more that, for example, udhcpc, _runs_ scripts in order to bring up/down the network interface. The scripts do things like edit /etc/resolv.conf and call ifconfig/route. With the dhcpcd from Buildroot I found this. If I remove the "default.script" file dhcp seems to work anyhow. Maybe it only can do standard features (getting IP-address, Network mask and gateway) but not extended features (like transferring the local name to the DHCP server to have it pass it to the DNS server. I found that "default.script" starts with "#!/bin/msh". I don't have such a file (in fact no "msh" shell at all at this time). In fact I tried the "-I" parameter to transfer a name to the DHCP server to have it pass it to the DNS server. This does not work. Maybe I'm wrong assuming "-I" to be used for that feature, maybe the problem really is that I don't have /bin/msh. -Michael ___ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
