Tzafrir Cohen wrote:
On Mon, Jun 29, 2009 at 03:47:13PM -0400, Ed Sutter wrote:
Ok, next question...
My original reason for upgrading from etch to lenny was because a
tool (cross compiler) I'm using complained because it needed
GLIBC_2.4, and apparently etch only went up to GLIBC_2.3.8.
Ok, next question...
My original reason for upgrading from etch to lenny was because a
tool (cross compiler) I'm using complained because it needed
GLIBC_2.4, and apparently etch only went up to GLIBC_2.3.8.
Now I've updated to Lenny, and the tool no longer complains about
GLIBC_2.4. That's the
Rich Griffiths wrote:
On Mon, 29 Jun 2009 19:30:19 +0200, Ed Sutter wrote:
Hi,
Last week I attempted to upgrade to lenny. Everything *seemed* to go
well, until I rebooted.. Now at startup I see a few errors (see below)
and end up with no GUI, and no network connectivity.
Bottom line...
It
Ed Sutter wrote:
Hi,
Last week I attempted to upgrade to lenny.
Everything *seemed* to go well, until I rebooted..
Now at startup I see a few errors (see below) and end up
with no GUI, and no network connectivity.
Bottom line...
It ain't good. :-(
Anyone have a clue what may have hap
Hi,
Last week I attempted to upgrade to lenny.
Everything *seemed* to go well, until I rebooted..
Now at startup I see a few errors (see below) and end up
with no GUI, and no network connectivity.
Bottom line...
It ain't good. :-(
Anyone have a clue what may have happened?
Thanks in advance,
Ed
I can run gconf-editor, but there is no NetworkManagerApplet
under apps.
I see that there is something called NetworkManager and
NetworkManagerDispatcher
under /usr/sbin; but when I run gconf-editor, there's no
apps->NetworkManagerApplet
entry.
continued thanks...
sed in the "man interfaces"
was referring to some call to ifup that was being done during
system startup somewhere; hence, the reason for my reboot.
See what I mean?
Shachar Or wrote:
On Wednesday 20 August 2008 23:29, Ed Sutter wrote:
Thanks for the responses!
My /etc/network/interf
the "auto eth0" line and rebooted.
No change.
Then I put "auto eth0" back in and commented out "allow-hotplug eth0".
Same thing.
Any other thoughts?
Ed
Shachar Or wrote:
On Wednesday 20 August 2008 22:46, Sebastian Canagaratna wrote:
Ed Sutter wrote:
Hi,
I have Debian 4.
Hi,
I have Debian 4.0 on a machine now for 2 days.
Thanks to this list, my screen resolution problem is
resolved. Next (and hopefully last) problem is that
each time I boot the system I have to manually enable
my network connection. When Gnome starts up, I see in
the top of the screen a small et
Modeline "1440x900" 106.5 1440 1520 1672 1904 900 901 904 932 -HSync
+VSync
EndSection
i don't know what those parameters are exactly, so maybe taking some
time to understand it can help a bit =D
i'll be out for today, but when i'm back i'll get into it agai
Driver
if it is using vesa, then your card's driver is not being loaded...
i can't count how many times this was the main problem for me =)
On Tue, Aug 19, 2008 at 15:23, Ed Sutter <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Hi,
New to this list, and new
Hi,
New to this list, and new to Debian. Just installed this over top of
an old installation of RH9, which worked fine, just a bit dated. My
machine is a K6-2, old but reliable.
I installed by creating a small install CD, booting from CD and then
basically letting it do its thing for an hour dow
12 matches
Mail list logo
