Re: Booting into Busybox shell

2010-10-18 Thread David Suna
On 18/10/2010 3:57 PM, Tzafrir Cohen wrote: On Mon, Oct 18, 2010 at 03:52:20PM +0200, David Suna wrote: I have an Ubuntu 8.04 system that was not shut down cleanly (because of a power outage) and when I rebooted it it came up into a Busybox shell. I simply rebooted again and it came up fine.

Re: Booting into Busybox shell

2010-10-18 Thread Tzafrir Cohen
On Mon, Oct 18, 2010 at 03:52:20PM +0200, David Suna wrote: > > > I have an Ubuntu 8.04 system that was not shut down cleanly (because of > a power outage) and when I rebooted it it came up into a Busybox shell. > I simply rebooted again and it came up fine. > > > What does this mean? Does it

Booting into Busybox shell

2010-10-18 Thread David Suna
I have an Ubuntu 8.04 system that was not shut down cleanly (because of a power outage) and when I rebooted it it came up into a Busybox shell. I simply rebooted again and it came up fine. What does this mean? Does it indicate some problem that I should deal with? Thanks, -- David Suna

Re: firewall with real IP's

2010-10-18 Thread Amos Shapira
2010/10/18 Hetz Ben Hamo : > * What would you recommend as a good firewall (please, only the ones who are > being updated and have docs. ipcop for example has old documents and you > really need to "hunt" for some good instructions. Smoothwall is old [2007] > and it's not being updated at all) How

Re: What's up with Bezeq ? Can people please try the following:

2010-10-18 Thread ik
I'm redirected to google: " Run your web applications on Google's infrastructure. " I'm using ccc as my ISP (had enough with the "big" ISP), but OpenDNS as my dns server. Ido 2010/10/18 Maxim Veksler > Hi, > > Something very strange is going on these days with Bezeq ISP network. > I seem to be

Re: What's up with Bezeq ? Can people please try the following:

2010-10-18 Thread Maxim Veksler
Hmmm, thanks but I meant to try to reach the servers using your connection. Pingdom seems to be working fine but I don't know what IP they resolve too. Them issue seems to be resolved now, can it really be that it was a Google issue? Note the following: This was the DNS resolution I was getting