On 11/11/14 11:59 AM, Christian Seiler wrote:
Am 11.11.2014 um 17:48 schrieb Gary Dale:
Update: booting using sysrescuecd, I removed the
/etc/rcS.d/S13networking link and rebooted into single-user mode. It
completed OK, so I then ran /etc/init.d/networking start, which
exhibited the same problem
Am 11.11.2014 um 17:48 schrieb Gary Dale:
>> Update: booting using sysrescuecd, I removed the
>> /etc/rcS.d/S13networking link and rebooted into single-user mode. It
>> completed OK, so I then ran /etc/init.d/networking start, which
>> exhibited the same problems it did when run by init. However
On 04/11/14 01:10 AM, Gary Dale wrote:
On 03/11/14 12:23 PM, Gary Dale wrote:
After the last upgrade (kernel 3.2.0-4-amd64 and wget), I have a
Debian/Wheezy server that isn't starting. It gets to the network then
stops.
The system isn't hung - it will still output messages to the screen
when
On 03/11/14 12:23 PM, Gary Dale wrote:
After the last upgrade (kernel 3.2.0-4-amd64 and wget), I have a
Debian/Wheezy server that isn't starting. It gets to the network then
stops.
The system isn't hung - it will still output messages to the screen
when I plug and unplug USB devices, and I ca
After the last upgrade (kernel 3.2.0-4-amd64 and wget), I have a
Debian/Wheezy server that isn't starting. It gets to the network then
stops.
The system isn't hung - it will still output messages to the screen
when I plug and unplug USB devices, and I can use the SysRq key to do
the reisu
5 matches
Mail list logo
