I thought that I had never seen an attachment on the list before but I
was not sure. So here is the lazy output. (Power Management bus
mastering PCI capabilities listing VGA compatible controller VT8375
[ProSavage8 KM266/KL266] [5333:8D04] S3 Graphics Ltd. [5333] 0
pci@:01:00.0 00 32 6600
hardware.
>> That installation failed to install
>>net-tools
>
> This is to be expected, net-tools is no longer installed by default,
> the alleged successor is iproute2.
>
>> The whole installation "seemed" to go well,
>> and on reboot the desktop interfa
On 2017-04-06 11:09 -0400, Jameson Burt wrote:
> On Sunday, April 2, I installed from scatch on all new hardware.
> That installation failed to install
>net-tools
This is to be expected, net-tools is no longer installed by default,
the alleged successor is iproute2.
&g
On Sunday, April 2, I installed from scatch on all new hardware.
That installation failed to install
net-tools
The whole installation "seemed" to go well,
and on reboot the desktop interface worked well.
While the installation properly used some networking during installation,
af
> I tried to read the docs to see how the ifconfig in inetutils-tools is
> different from the one in net-tools, but saw nothing.
> Is it okay to have both? Should I pick one or the other?
well, inetutils-tools just break stuff for me and that`s all.
actually i don`t really get the
I tried to read the docs to see how the ifconfig in inetutils-tools is
different from the one in net-tools, but saw nothing.
Is it okay to have both? Should I pick one or the other?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Cont
Hi,
accidentally, i erased net-tools packages, netstat, hostname,
dnsdomainname ... etc. Then,
i re-install then, but for the netstat,
unable to make backup link of `./bin/netstat' before installing new
version: Operation not permitted
how i can re-install net-tools packages?
thanks
| * backported ifconfig change from 1.59 to avoid closing socket too early
| on some systems (depending on the protocols installed).
| Closes Bug: #85688, #85743
This didn't resolve my NFS error 111 problem. Does anyone have other
suggestions? (I have checked that the portmapper starts
"Ken Sandell" <[EMAIL PROTECTED]> wrote:
>Has the net-tools bug been fixed yet? I mean, jeez..I would have
>thought so...after fixing it once, I thought I could wait 3 days and
>it'd be fixed...but no..I did a dist-upgrade again and my system drops
>to the floor
Has the net-tools bug been fixed yet? I mean,
jeez..I would have thought so...after fixing it once, I thought I could wait 3
days and it'd be fixed...but no..I did a dist-upgrade again and my system drops
to the floor like before..so I punch the door and wait for some
more.
My goo
On Wed, 14 Feb 2001, Nathan Dabney wrote:
> On Tue, Feb 13, 2001 at 01:38:32PM +0100, Bernd Eckenfels wrote:
> >
> > BTW: the Problem is upstream and fixed in 1.59. I have uploaded 1.58-2 which
> > will fix that, too. Don't know why it is not installed yet.
>
> So when should 1.58-2 come down the
On Tue, Feb 13, 2001 at 01:38:32PM +0100, Bernd Eckenfels wrote:
>
> BTW: the Problem is upstream and fixed in 1.59. I have uploaded 1.58-2 which
> will fix that, too. Don't know why it is not installed yet.
>
So when should 1.58-2 come down the pipe to sid anyway?
Unless I am just blind...
-
On Tue, Feb 13, 2001 at 01:38:32PM +0100, Bernd Eckenfels wrote:
> On Mon, Feb 12, 2001 at 08:25:40PM -0800, Michael Epting wrote:
> > This was hilarious. I had shut down my laptop this morning after reading,
> > but not entirely absorbing, the above.
>
> Thanks for sharing that with us :)
>
>
On Mon, Feb 12, 2001 at 08:25:40PM -0800, Michael Epting wrote:
> This was hilarious. I had shut down my laptop this morning after reading,
> but not entirely absorbing, the above.
Thanks for sharing that with us :)
BTW: the Problem is upstream and fixed in 1.59. I have uploaded 1.58-2 which
wi
ing up networking, I couldn't get to this email, which
> I had read by ssh'ing to my workstation. I have only the current **bad**
> net-tools .deb in my /var/cache/apt/archives, of course, so there is no
> hope of restoring the last good one quickly.
I agree. That's hila
rking, I couldn't get to this email, which
I had read by ssh'ing to my workstation. I have only the current **bad**
net-tools .deb in my /var/cache/apt/archives, of course, so there is no
hope of restoring the last good one quickly.
OK, no problem, I go to my workstation, which I had also
On Mon, Feb 12, 2001 at 10:17:24PM +1030, David Purton wrote:
> On Mon, 12 Feb 2001, Wichert Akkerman wrote:
>
> > ip route add 0.0.0.0/0 dev eth0 metric 1
> >
>
> Slightly off topic, but can anyone explain to me what the metric field
> does - the man page is bit brief for my level of understand
On Mon, 12 Feb 2001, Wichert Akkerman wrote:
> ip route add 0.0.0.0/0 dev eth0 metric 1
>
Slightly off topic, but can anyone explain to me what the metric field
does - the man page is bit brief for my level of understanding in these
things :)
$ man route
metric M
set the metri
Previously Wichert Akkerman wrote:
> Needless to say this is *EXTREMELY* stupid behaviour of ifconfig
> and completely breaks your system.
Okay, for those of you who have iproute installed, you can still get things
up and running using the ip tool. Like this:
ip addr add 127.0.0.1 dev lo
ip link
It seems the new version of net-tools in unstable is completely and utterly
broken to the point where it is no longer possibile to configure any
network interface:
fog:~# ifconfig lo 127.0.0.1
SIOCSIFADDR: Bad file descriptor
lo: unknown interface: Bad file descriptor
lo: unknown interface: Bad
20 matches
Mail list logo
