Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm running a Minix using VirtualBox. Minix is set to use the DHCP. And the network adapter is using a bridged connection*.

When I last saved the state of the machine its IP was (ifconfig) and was connected to wlan0 (VirtualBox network settings). When I resumed the machine I changed the network adapter to eth0 -- the DHCP on this network* hands-out IP in the range 192.168.0.X-- but the IP that the system is assuming is, for obvious reasons, which of course can't be reached. For say, ssh-ing.

I know Minix conforms with the POSIX standards. But like in Ubuntu (Linux) I couldn't use service networking restart nor could I find anything under /etc that could provide a hint. Of course I could use something like ifconfig -h netmask mtu 1500. But I want to get the IP from the DHCP.


  • How can I restart (command) the network dev/manager in Minix? (Assuming that way I could get a new IP)

  • How can I request (command) a new IP from the DHCP?

*please excuse/correct my (if any) technically inaccurate description.

share|improve this question
"for obvious reasons" -- Are you sure the reason is just self-evident? Do you believe the minix kernel is making this mistake, or is it some userland application? It's implied here that by "saved state" you mean, while the system was running (as opposed to cleanly shut down). It's also implicit that you are using some kind of dhcp client (normal linux networking does). If both those implications are true, the issue is with the userland dhcp client. You need to restart that. – goldilocks Apr 5 '14 at 20:05
Isn't there any docs for that? – Pavel Šimerda Apr 5 '14 at 20:05
@TAFKA'goldilocks' I maybe outright wrong because I'm new at this. Since I have read a fair deal of material on micro- and macro-kernels so I can assume it's a userland application and not the kernel's mistake. I'll have to find DHCP client process since the first answer is yes and the second one could be yes (not sure) because I choose DHCP during installation. Thanks. – Bleeding Fingers Apr 5 '14 at 20:22
@PavelŠimerda Google and DDG failed be at it. – Bleeding Fingers Apr 5 '14 at 20:23
@BleedingFingers: The Minix docs I just quickly scanned through indeed don't seem to be very verbose on that. – Pavel Šimerda Apr 5 '14 at 20:26

Reading the documentation and man pages leads me to believe that you should use netconf. According to its manual page, something like:

netconf -a

and then answering any interactive questions, likely does what you wan. You're existing configuration exists in:


It seems you can also get dhcpd to print its current view of the world with:

dhcpd -q

And it further seems that you can restart all network services with


Note that this is just from reading the pretty sparse documentation and poking around the system for a few minutes, but hopefully it gives you some places to continue to investigate. I would also try reading the boot man page and then looking at the various rc scripts it calls on system init. The /etc/rs.inet command above is used in /usr/etc/rc by the service command, which also has a restart action that might be interesting to you.

share|improve this answer
"You might have to reboot for the changes to take effect." – Bleeding Fingers Apr 5 '14 at 20:30
Added some more that I found that might help. – Steven D Apr 5 '14 at 20:42
Deleted the other answer as it was a small subset of this one. – Pavel Šimerda Apr 7 '14 at 18:17

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.