date:20131115

On Fri, 2013-11-15 at 16:46 -0700, Bob Proulx wrote:
> Mark a few of the top level ones and then run autoremove, answer 'n'o.
> Then pick another top level package and mark it.  Then run autoremove
> again and answer 'n'o again.  Repeat until you have marked to keep all
> of the packages that you want to keep.

As root running a command that could remove packages, just to monitor
something, is bad practice. Soon or later it will result in "Oops,
accidentally removed".

"-s, --simulate, --just-print, --dry-run, --recon, --no-act
No action. Perform a simulation of events that would occur but do not
actually change the system." - http://linux.die.net/man/8/apt-get 

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1384587118.707.12.camel@archlinux

Re: Automatic installs

2013-11-15 Thread Bob Proulx

Brad Alexander wrote:
> Hi Bob,
> 
> (every time I see your avatar, it makes me want to go back and finish up my
> pilot's license. :) )

If you do that then I have done my good deed for the day!  :-)
Remember that it is never too late to have a happy childhood.

Bob

signature.asc
Description: Digital signature

Re: Why Debian

2013-11-15 Thread Alberto Salvia Novella


Thanks for your comments on this topic.

Have a nice week ☕


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/5286e111.8060...@gmail.com

Re: Automatic installs

2013-11-15 Thread Brad Alexander

Hi Bob,

(every time I see your avatar, it makes me want to go back and finish up my
pilot's license. :) )

Thanks for your advice. I think the package manager got confused, but I was
able to apt-get install kde-full. It added about half a dozen packages, but
it also brought the ones i was having issues with back into the fold.

Thanks for pushing me in the right direction.

--b


On Fri, Nov 15, 2013 at 6:46 PM, Bob Proulx  wrote:

> Brad Alexander wrote:
> > Calculating upgrade... The following packages were automatically
> installed
> > and are no longer required:
> >   akonadiconsole akregator amor ark avogadro-data blinken blogilo bomber
> > bovo
> >   cantor cervisia crda cvs cvsservice dnsmasq-base dragonplayer easy-rsa
> > gnugo
> >  ...snip...
> >   step svgpart sweeper texlive-latex-base texlive-latex-base-doc
> >   translate-toolkit umbrello usb-modeswitch usb-modeswitch-data valgrind
> >   valgrind-dbg vpnc wireless-regdb wpasupplicant
> > Use 'apt-get autoremove' to remove them.
>
> Did you install these with KDE and then along the way remove the kde
> meta package?
>
> > I am deathly afraid to apt-get autoremove, because I see a lot of things
> in
> > there that I use, such as akregator, gwenview, kwalletmanager,
>
> Then in that case mark them as being something you want to keep
> around.  The easy way is simply to fire the install command on them.
>
>   apt-get install akregator gwenview kwalletmanager ...
>
> That will say that they are up to date and then also say that it is
> marking them as manually installed.
>
> There is also the 'apt-mark manual foo' command to mark foo as
> manually installed too.  Either way is fine.  For this apt-get install
> is one less thing to remember.
>
> > So is this for real, and if I apt-get autoremove, it will gut my
> > system, or am I missing some detail and it's all good?
>
> As currently known if you run apt-get autoeremove it will remove those
> packages.  But if you are using those packages then don't do that. :-)
> Instead simply mark them as being manually installed.
>
> Mark a few of the top level ones and then run autoremove, answer 'n'o.
> Then pick another top level package and mark it.  Then run autoremove
> again and answer 'n'o again.  Repeat until you have marked to keep all
> of the packages that you want to keep.  Almost certainly along the way
> you will find some package that you don't want and will decide to let
> it go.  The automatically installed list is just a helper to help you
> maintain your system.  But it is a simple thing and doesn't know about
> all cases such as the removal of a kde meta package.  You are
> certainly encouraged to use judgement and drive it the way you want.
>
> Bob
>

Re: Automatic installs

2013-11-15 Thread Bob Proulx

Brad Alexander wrote:
> Calculating upgrade... The following packages were automatically installed
> and are no longer required:
>   akonadiconsole akregator amor ark avogadro-data blinken blogilo bomber
> bovo
>   cantor cervisia crda cvs cvsservice dnsmasq-base dragonplayer easy-rsa
> gnugo
>  ...snip...
>   step svgpart sweeper texlive-latex-base texlive-latex-base-doc
>   translate-toolkit umbrello usb-modeswitch usb-modeswitch-data valgrind
>   valgrind-dbg vpnc wireless-regdb wpasupplicant
> Use 'apt-get autoremove' to remove them.

Did you install these with KDE and then along the way remove the kde
meta package?

> I am deathly afraid to apt-get autoremove, because I see a lot of things in
> there that I use, such as akregator, gwenview, kwalletmanager,

Then in that case mark them as being something you want to keep
around.  The easy way is simply to fire the install command on them.

  apt-get install akregator gwenview kwalletmanager ...

That will say that they are up to date and then also say that it is
marking them as manually installed.

There is also the 'apt-mark manual foo' command to mark foo as
manually installed too.  Either way is fine.  For this apt-get install
is one less thing to remember.

> So is this for real, and if I apt-get autoremove, it will gut my
> system, or am I missing some detail and it's all good?

As currently known if you run apt-get autoeremove it will remove those
packages.  But if you are using those packages then don't do that. :-)
Instead simply mark them as being manually installed.

Mark a few of the top level ones and then run autoremove, answer 'n'o.
Then pick another top level package and mark it.  Then run autoremove
again and answer 'n'o again.  Repeat until you have marked to keep all
of the packages that you want to keep.  Almost certainly along the way
you will find some package that you don't want and will decide to let
it go.  The automatically installed list is just a helper to help you
maintain your system.  But it is a simple thing and doesn't know about
all cases such as the removal of a kde meta package.  You are
certainly encouraged to use judgement and drive it the way you want.

Bob

signature.asc
Description: Digital signature

SOLVED was: Re: eth0 "disabled" after upgrade Squeeze to Wheezy

Hi, Andrei!
On Friday 15 November 2013 19:35:50 Andrei POPESCU wrote:
> On Vi, 15 nov 13, 18:34:36, Lisi Reisz wrote:
> > I did - and have just checked again.  network-manger is preceded
> > by a "p" if I do an "aptitude search network manager".  Pity. 
> > Removing network-manager would be so simple!!
>
> Ok, considering that your previous setup was DHCP I would try
> setting up the connection "manually".
>
> # dhclient eth0

Worked!!  So I was in a position to send verbatim errors and long 
files ot teh list. :-)

> If this works you'll know the basic infrastructure works and you
> can look at why ifupdown is failing. BTW, did you try reinstalling
> it? What does dpkg think about it:

I ran *all* the following commands in the order here, and took care to 
save the results.  But see later.
> $ dpkg -l ifupdown
>
> Other things to check:
>
> $ aptitude search '?broken'
> $ dpkg --audit

Showed that ifupdown - and a whole lot of other packages - was not 
configured.  It needed iproute to agree to configure, so I configured 
both and now I have netwrok connectivity. \o/

> Check also the output of 'mount' and compare to /etc/fstab. See
> also that /run exists (it should be a tmpfs).
>
> Did you try booting text only? For kdm the simplest method seems to
> be
>
> # update-rc.d kdm disable ; reboot
>
> (you can reverse this with 'enable' or 'defaults')
>
> Hope this helps,

It most certainly did.  Thank you very much,
Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201311152334.40162.lisi.re...@gmail.com

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Friday 15 November 2013 19:18:26 Glenn English wrote:
> On Nov 15, 2013, at 12:01 PM, Lisi Reisz  
wrote:
> >> Re-adding the two etho lines should fix it all for you - unless
> >> a reboot deletes them, somehow!
> >
> > it did. :-(
>
> Noob here. How about fixing /etc/network/interfaces, removing all
> write permissions from the file, rebooting, and looking for write
> errors? In hopes of finding what's writing over the file...

Thank you for the help.  I really appreciate all the help that you 
kind folks are giving me.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201311152248.41099.lisi.re...@gmail.com

Re: Wich port should I use for Xeon E3-1230v2 processor ?

2013-11-15 Thread Stan Hoeppner

On 11/15/2013 10:48 AM, John Ostrowski wrote:
> Hi, I recently bought Dell PowerEdge T110 II with  Intel Xeon
> E3-1230v2 Processor (3.3GHz, 4C/8T, 8M Cache). I don't know which
> port I should use. At the moment I am using Debian 7.1.0 AMD64 and I

AMD64 is the correct architectural port for all Xeon Processors going
back at least 8 years.

> have serious issue. Desktop keeps locking all the time. I can move
> mouse but system does not react. Best regards. John Ostrowski

The problem is most likely your graphics driver.  Which GPU is in this Dell?

-- 
Stan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52869a27.7050...@hardwarefreak.com

Re: Why Debian

On Fri, 2013-11-15 at 22:41 +0100, Ralf Mardorf wrote:
> On Fri, 2013-11-15 at 13:25 -0500, Miles Fidelman wrote:
> > checkinstall
> 
> I can't answer your question, but I love checkinstall :). Unfortunately
> checkinstall doesn't work always.

PS:

"Make love, not install!" - A quote from somebody who prefers to remain
anonymous.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1384552083.707.5.camel@archlinux

Re: Why Debian

On Fri, 2013-11-15 at 13:25 -0500, Miles Fidelman wrote:
> checkinstall

I can't answer your question, but I love checkinstall :). Unfortunately
checkinstall doesn't work always.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1384551694.707.1.camel@archlinux

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

2013-11-15 Thread Neal Murphy

On Friday, November 15, 2013 11:38:16 AM Lisi Reisz wrote:
> Thanks, Andrei,
> 
> On Friday 15 November 2013 16:15:20 Andrei POPESCU wrote:
> > On Vi, 15 nov 13, 15:06:59, Lisi Reisz wrote:
> > > I have just upgraded a client's computer to Wheezy.  It appeared
> > > to go well and there was certainly an internet connection: it
> > > would not have been able to upgrade otherwise!
> > > 
> > > Now there is  none.  I have checked /etc/network/interfaces and
> > > changed "allow-hotplug" to "auto", just for something to try. :-(
> > > 
> > >  It made no difference.  I pinged the gateway, largely so that I
> > > 
> > > could report that I had done so.  I got the error message
> > > "Network is unreachable".
> > > 
> > > KControl tells me that eth0 is "disabled".  How and why is it
> > > disabled?  More importantly, **how do I enable it?**
> > 
> > How is the network configuration handled? Network Manager,
> > ifupdown, etc.?
> 
> /etc/network/interfaces file and ifupdown, etc..  (Network Manager and
> I are not on speaking terms.)
> 
> Lisi

'ls /sys/class/net' to see all known network devices.
'ip link' to see their states: up/down, (no)carrier, PtP/broadast, et alia

If eth0 is there and appears to be a broadcast medium with carrier present, 
you can manually bring it up and verify connectivity:
-
ip link set dev eth0 up
ip addr add 192.168.0.2/24 dev eth0
ip route add default via 192.168.0.1
ping 8.8.8.8
-

If it works, then the immutable bit in my previous message should aim your 
20mm cannon on the guilty culprit.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201311151522.42892.neal.p.mur...@alum.wpi.edu

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

2013-11-15 Thread Neal Murphy

On Friday, November 15, 2013 02:18:26 PM Glenn English wrote:
> On Nov 15, 2013, at 12:01 PM, Lisi Reisz  wrote:
> >> Re-adding the two etho lines should fix it all for you - unless a
> >> reboot deletes them, somehow!
> > 
> > it did. :-(
> 
> Noob here. How about fixing /etc/network/interfaces, removing all write
> permissions from the file, rebooting, and looking for write errors? In
> hopes of finding what's writing over the file...

Close, Glenn. Set the file's 'immutable' bit so it *can't* be changed or 
deleted. That should surely raise the hackles of the quisling.
--
mkdir /run/network
# edit /etc/network/interfaces to restore eth0

chattr +i /run/network /etc/network/interfaces
--


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201311151512.44290.neal.p.mur...@alum.wpi.edu

Automatic installs

2013-11-15 Thread Brad Alexander

Have a question about automatic dependencies. I just updated my sid
machine, as more and more of KDE 4.11 was uploaded this week. Well, when I
did, I got the following during the dist-upgrade:

Calculating upgrade... The following packages were automatically installed
and are no longer required:
  akonadiconsole akregator amor ark avogadro-data blinken blogilo bomber
bovo
  cantor cervisia crda cvs cvsservice dnsmasq-base dragonplayer easy-rsa
gnugo
 ...snip...
  step svgpart sweeper texlive-latex-base texlive-latex-base-doc
  translate-toolkit umbrello usb-modeswitch usb-modeswitch-data valgrind
  valgrind-dbg vpnc wireless-regdb wpasupplicant
Use 'apt-get autoremove' to remove them.

I am deathly afraid to apt-get autoremove, because I see a lot of things in
there that I use, such as akregator, gwenview, kwalletmanager,
network-manager, etc. I did a quick check, using apt-file, thinking that
maybe the package name for the app might have changed:

$ apt-file search /usr/bin/akregator
akregator: /usr/bin/akregator
akregator: /usr/bin/akregatorstorageexporter
kdepim-dbg: /usr/lib/debug/usr/bin/akregator
kdepim-dbg: /usr/lib/debug/usr/bin/akregatorstorageexporter

But they didn't as far as I can tell. So is this for real, and if I apt-get
autoremove, it will gut my system, or am I missing some detail and it's all
good?

Thanks,
--b

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Vi, 15 nov 13, 18:34:36, Lisi Reisz wrote:
> 
> I did - and have just checked again.  network-manger is preceded by 
> a "p" if I do an "aptitude search network manager".  Pity.  Removing 
> network-manager would be so simple!!

Ok, considering that your previous setup was DHCP I would try setting up 
the connection "manually".

# dhclient eth0

If this fails (and please post the error messages) you could even try to 
set it up manually (this time without the quotes):

# ifconfig eth0 192.168 netmask 255.255.255.0 up
# route add default gw 192.168.
# echo 'nameserver 8.8.8.8' > /etc/resolv.conf

(this of course assumes you can get the relevant information about the 
local network)

If this works you'll know the basic infrastructure works and you can 
look at why ifupdown is failing. BTW, did you try reinstalling it? What 
does dpkg think about it:

$ dpkg -l ifupdown

Other things to check:

$ aptitude search '?broken'
$ dpkg --audit

Check also the output of 'mount' and compare to /etc/fstab. See also 
that /run exists (it should be a tmpfs).

Did you try booting text only? For kdm the simplest method seems to be

# update-rc.d kdm disable ; reboot

(you can reverse this with 'enable' or 'defaults')

Hope this helps,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt

signature.asc
Description: Digital signature

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

2013-11-15 Thread Glenn English

On Nov 15, 2013, at 12:01 PM, Lisi Reisz  wrote:

>> Re-adding the two etho lines should fix it all for you - unless a
>> reboot deletes them, somehow!
> 
> it did. :-(

Noob here. How about fixing /etc/network/interfaces, removing all write 
permissions from the file, rebooting, and looking for write errors? In hopes of 
finding what's writing over the file...

-- 
Glenn English
Disclaimer: Any disclaimer attached to this message may be ignored.

smime.p7s
Description: S/MIME cryptographic signature

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Friday 15 November 2013 18:40:23 Tom H wrote:
> On Fri, Nov 15, 2013 at 5:53 PM, Lisi Reisz  
wrote:
> > On Friday 15 November 2013 17:06:55 Tom H wrote:
> >> On Fri, Nov 15, 2013 at 4:13 PM, Lisi Reisz
> >> 
> >
> > wrote:
> >>> On Friday 15 November 2013 15:55:59 Lisi Reisz wrote:
>  On Friday 15 November 2013 15:29:00 Tom H wrote:
> > On Fri, Nov 15, 2013 at 3:06 PM, Lisi Reisz
> >
> >  wrote:

> >> KControl tells me that eth0 is "disabled". How and why is it
> >> disabled? More importantly, **how do I enable it?**
> >
> > Has eth0 been renamed? What's the output of "ip a"?
> 
>  # ifup -a
>  ifup: failed to open statefile /run/network/ifstate: No such
>  file or directory
> 
>  I misread at first - but "ifup a" produces the same result.
> 
> > (Did you run "ifup -a" or "ifup eth0" after changing
> > "allow-hotplug" to "auto"?)
> 
>  Yes - and have restarted several times now. :-(
> 
>  "ifconfig -a" shows eth0 and lo, neither of which has an IP.
> >>>
> >>> # mkdir /run/network
> >>> # ifup lo
> >>>
> >>> lo now has an IP address.
> >>> eth0 is still "unknown interface" :-(
> >>
> >> cat /etc/network/interfaces
> >
> > It was:
> > -
> > # This file describes the network interfaces available on your
> > system # and how to activate them. For more information, see
> > interfaces(5).
> >
> > # The loopback network interface
> > auto lo
> > iface lo inet loopback
> >
> > # The primary network interface
> > auto eth0
> > iface eth0 inet dhcp
> > ---
> >
> > It is now <%$&()&^$£%>:
> > 
> > # This file describes the network interfaces available on your
> > system # and how to activate them. For more information, see
> > interfaces(5).
> >
> > # The loopback network interface
> > auto lo
> > iface lo inet loopback
> >
> > # The primary network interface
> > 
>
> Are you comparing pre- and post-diest-upgrade?

No - both post dist-upgrade.  I edited the interfaces file from 
allow-hotplug to auto as an early attempt at troubleshooting.  Then 
the lines disappeared altogether during this trouble-shooting.

> Re-adding the two etho lines should fix it all for you - unless a
> reboot deletes them, somehow!

it did. :-(

> If it happened via the dist-upgrade (and not via debconf), grepping
> "/var/lib/dpkg/info/*" for "/etc/network/interfaces" might give you
> the culprit; most likely the ifupdown scripts in there.

It happened the first time I rebooted _after_ the dist-upgrade. 

grep drew a blank, so I searched manually.  There are some Trinity 
files re network that I had better look into before I bother you two 
further.  I am most grateful for all the help.

Lisi


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201311151901.45288.lisi.re...@gmail.com

Re: Investigating dependency trees

2013-11-15 Thread Richard Owlett


Tom H wrote:

On Fri, Nov 15, 2013 at 5:25 PM, Richard Owlett  wrote:


Synaptic and dselect provide this information for *ONE* level down from a
particular package *IF* an actual installation and repository exist.


apt-cache depends --recurse 
apt-cache rdepends --recurse 



Reading the man page suggests it solves my problem in a slightly 
different way than I was visualizing. But it has a major plus, 
the references to 
GraphViz{http://www.research.att.com/sw/tools/graphviz/} and VCG 
tool{http://rw4.cs.uni-sb.de/users/sander/html/gsvcg1.html} 
indicate the output problem is essentially solved ;!


Now to run some test cases.
Thank you.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/52866cd4.80...@cloud85.net

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Friday 15 November 2013 18:33:21 Tom H wrote:
> On Fri, Nov 15, 2013 at 5:38 PM, Lisi Reisz  
wrote:
> > On Friday 15 November 2013 17:05:04 Tom H wrote:
> >> On Fri, Nov 15, 2013 at 3:55 PM, Lisi Reisz
> >> 
> >
> > wrote:
> >>> On Friday 15 November 2013 15:29:00 Tom H wrote:
>  On Fri, Nov 15, 2013 at 3:06 PM, Lisi Reisz
> 
>   wrote:
>>  eth0 is "disabled". How and why is it
> > disabled? More importantly, **how do I enable it?**
> >>>
> >>> # ifup -a
> >>> ifup: failed to open statefile /run/network/ifstate: No such
> >>> file or directory
> >>
> >> "ifup -a" should bring up all interfaces marked "auto" (or
> >> "allow-auto") in "/etc/network/interfaces". (Is the latter OK?)
> >>
> >> The "networking" init script must (I haven't checked it) create
> >> "/run/network". etc.
> >>
> >> Change the shebang of "/etc/init.d/networking" to "#!/bin/sh
> >> -ex" and run "/etc/init.d/networking stop" then
> >> "/etc/init.d/networking start".
> >
> > Done.
> > #ping 192.168.0.1
> > connect: Network is unreachable
> >
> > :-(
> :
> :(
>
> Indeed!
>
> Did the "-x" make the start of the daemon more verbose?

Not noticeably, but the beginning was out of reach anyway.  (Konsole 
will only go back so far.)

I see that there are in fact error messages during the operation of 
the daemon.  But the main problem must still be whatever is 
overwriting everything to do with networks.

Thanks, guys,
Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201311151848.03702.lisi.re...@gmail.com

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Fri, Nov 15, 2013 at 5:53 PM, Lisi Reisz  wrote:
> On Friday 15 November 2013 17:06:55 Tom H wrote:
>> On Fri, Nov 15, 2013 at 4:13 PM, Lisi Reisz 
> wrote:
>>> On Friday 15 November 2013 15:55:59 Lisi Reisz wrote:
 On Friday 15 November 2013 15:29:00 Tom H wrote:
> On Fri, Nov 15, 2013 at 3:06 PM, Lisi Reisz
>  wrote:
>>
>> I have just upgraded a client's computer to Wheezy. It
>> appeared to go well and there was certainly an internet
>> connection: it would not have been able to upgrade otherwise!
>>
>> Now there is none. I have checked /etc/network/interfaces and
>> changed "allow-hotplug" to "auto", just for something to try.
>>
>> :-( It made no difference. I pinged the gateway, largely so
>>
>> that I could report that I had done so. I got the error
>> message "Network is unreachable".
>>
>> KControl tells me that eth0 is "disabled". How and why is it
>> disabled? More importantly, **how do I enable it?**
>
> Has eth0 been renamed? What's the output of "ip a"?

 # ifup -a
 ifup: failed to open statefile /run/network/ifstate: No such
 file or directory

 I misread at first - but "ifup a" produces the same result.

> (Did you run "ifup -a" or "ifup eth0" after changing
> "allow-hotplug" to "auto"?)

 Yes - and have restarted several times now. :-(

 "ifconfig -a" shows eth0 and lo, neither of which has an IP.
>>>
>>> # mkdir /run/network
>>> # ifup lo
>>>
>>> lo now has an IP address.
>>> eth0 is still "unknown interface" :-(
>>
>> cat /etc/network/interfaces
>
> It was:
> -
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> auto eth0
> iface eth0 inet dhcp
> ---
>
> It is now <%$&()&^$£%>:
> 
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> 

Are you comparing pre- and post-diest-upgrade?

Re-adding the two etho lines should fix it all for you - unless a
reboot deletes them, somehow!

If it happened via the dist-upgrade (and not via debconf), grepping
"/var/lib/dpkg/info/*" for "/etc/network/interfaces" might give you
the culprit; most likely the ifupdown scripts in there.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOdo=SyrYSuf-xwcNJu7M=O-BWr-6ABzmm1DfjHHMymp8=h...@mail.gmail.com

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Friday 15 November 2013 17:19:30 Tom H wrote:
> On Fri, Nov 15, 2013 at 4:59 PM, Andrei POPESCU
>
>  wrote:
> > On Vi, 15 nov 13, 16:38:16, Lisi Reisz wrote:
> >>> How is the network configuration handled? Network Manager,
> >>> ifupdown, etc.?
> >>
> >> /etc/network/interfaces file and ifupdown, etc.. (Network
> >> Manager and I are not on speaking terms.)
> >
> > I'd check if Network Manager didn't get pulled in during the
> > dist-upgrade.
>
> Unless an NM post-install script is commenting out any non-lo
> interface in "/etc/network/interfaces", having NM install itself
> should affect the network because its default is not to manage
> interfaces that are defined in "/etc/network/interfaces".

How would I search?  And the lo interface doesn't make a great deal of 
difference - even lo doesn't get an IP. :-(

I need to find what is suppressing any attempt at creating a:
/run/network/ifstate

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201311151838.36366.lisi.re...@gmail.com

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Friday 15 November 2013 16:59:28 Andrei POPESCU wrote:
> On Vi, 15 nov 13, 16:38:16, Lisi Reisz wrote:
> > > How is the network configuration handled? Network Manager,
> > > ifupdown, etc.?
> >
> > /etc/network/interfaces file and ifupdown, etc..  (Network
> > Manager and I are not on speaking terms.)
>
> I'd check if Network Manager didn't get pulled in during the
> dist-upgrade.

I did - and have just checked again.  network-manger is preceded by 
a "p" if I do an "aptitude search network manager".  Pity.  Removing 
network-manager would be so simple!!

Thanks for the continued help, 
Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201311151834.36689.lisi.re...@gmail.com

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Fri, Nov 15, 2013 at 5:38 PM, Lisi Reisz  wrote:
> On Friday 15 November 2013 17:05:04 Tom H wrote:
>> On Fri, Nov 15, 2013 at 3:55 PM, Lisi Reisz 
> wrote:
>>> On Friday 15 November 2013 15:29:00 Tom H wrote:
 On Fri, Nov 15, 2013 at 3:06 PM, Lisi Reisz
  wrote:
>
> I have just upgraded a client's computer to Wheezy. It appeared
> to go well and there was certainly an internet connection: it
> would not have been able to upgrade otherwise!
>
> Now there is none. I have checked /etc/network/interfaces and
> changed "allow-hotplug" to "auto", just for something to try.
> :-( It made no difference. I pinged the gateway, largely so
> that I could report that I had done so. I got the error message
> "Network is unreachable".
>
> KControl tells me that eth0 is "disabled". How and why is it
> disabled? More importantly, **how do I enable it?**
>>>
>>> # ifup -a
>>> ifup: failed to open statefile /run/network/ifstate: No such file
>>> or directory
>>
>> "ifup -a" should bring up all interfaces marked "auto" (or
>> "allow-auto") in "/etc/network/interfaces". (Is the latter OK?)
>>
>> The "networking" init script must (I haven't checked it) create
>> "/run/network". etc.
>>
>> Change the shebang of "/etc/init.d/networking" to "#!/bin/sh -ex"
>> and run "/etc/init.d/networking stop" then "/etc/init.d/networking
>> start".
>
> Done.
> #ping 192.168.0.1
> connect: Network is unreachable
>
> :-(

:(

Indeed!

Did the "-x" make the start of the daemon more verbose?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOdo=Sxqvi-_7bcy_apKqtFVQySov8K_Egcixi7=myqfrrw...@mail.gmail.com

Re: Why Debian

2013-11-15 Thread Miles Fidelman


Ralf Mardorf wrote:

On Mon, 2013-11-11 at 17:15 +, Karl E. Jorgensen wrote:

Is there a better distro for managing
source-based in installs from upstream (and I'm not talking Gentoo,
where Portage is a packaging system for source code - I'm talking
semi-automatic management and updates from upstream source.  Any
thoughts?

You'll still end up with some "package" concept

True, but that's not an issue, it does allow you to install a "package"
and this package then will download the source from upstream. You will
be ask if you want to automatically let build the package, or if you
want to configure it first.


It occurs to me to ask: is there anything like this for Debian?  (I know 
about checkinstall, but it doesn't "download source from upstream").


Thanks,

Miles Fidelman

--
In theory, there is no difference between theory and practice.
In practice, there is.    Yogi Berra


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/52866735.2050...@meetinghouse.net

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Friday 15 November 2013 17:06:55 Tom H wrote:
> On Fri, Nov 15, 2013 at 4:13 PM, Lisi Reisz  
wrote:
> > On Friday 15 November 2013 15:55:59 Lisi Reisz wrote:
> >> On Friday 15 November 2013 15:29:00 Tom H wrote:
> >>> On Fri, Nov 15, 2013 at 3:06 PM, Lisi Reisz
> >>>
> >>>  wrote:
>  I have just upgraded a client's computer to Wheezy. It
>  appeared to go well and there was certainly an internet
>  connection: it would not have been able to upgrade otherwise!
> 
>  Now there is none. I have checked /etc/network/interfaces and
>  changed "allow-hotplug" to "auto", just for something to try.
> 
>  :-( It made no difference. I pinged the gateway, largely so
> 
>  that I could report that I had done so. I got the error
>  message "Network is unreachable".
> 
>  KControl tells me that eth0 is "disabled". How and why is it
>  disabled? More importantly, **how do I enable it?**
> >>>
> >>> Has eth0 been renamed? What's the output of "ip a"?
> >>
> >> # ifup -a
> >> ifup: failed to open statefile /run/network/ifstate: No such
> >> file or directory
> >>
> >> I misread at first - but "ifup a" produces the same result.
> >>
> >>> (Did you run "ifup -a" or "ifup eth0" after changing
> >>> "allow-hotplug" to "auto"?)
> >>
> >> Yes - and have restarted several times now. :-(
> >>
> >> "ifconfig -a" shows eth0 and lo, neither of which has an IP.
> >
> > # mkdir /run/network
> > # ifup lo
> >
> > lo now has an IP address.
> > eth0 is still "unknown interface" :-(
>
> cat /etc/network/interfaces

It was:
-
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp
---

It is now <%$&()&^$£%>:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface


Whatever is doing the overwriting is clearly overwriting this too.  It 
certainly behaves like Network Manager, but I have checked, and 
rechecked, and Network Mangler is definitely not there, anyhow 
according to both aptitude and apt-cache.

Thanks for your continued help.
Lisi


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201311151753.07519.lisi.re...@gmail.com

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Friday 15 November 2013 17:05:04 Tom H wrote:
> On Fri, Nov 15, 2013 at 3:55 PM, Lisi Reisz  
wrote:
> > On Friday 15 November 2013 15:29:00 Tom H wrote:
> >> On Fri, Nov 15, 2013 at 3:06 PM, Lisi Reisz
> >> 
> >
> > wrote:
> >>> I have just upgraded a client's computer to Wheezy. It appeared
> >>> to go well and there was certainly an internet connection: it
> >>> would not have been able to upgrade otherwise!
> >>>
> >>> Now there is none. I have checked /etc/network/interfaces and
> >>> changed "allow-hotplug" to "auto", just for something to try.
> >>> :-( It made no difference. I pinged the gateway, largely so
> >>> that I could report that I had done so. I got the error message
> >>> "Network is unreachable".
> >>>
> >>> KControl tells me that eth0 is "disabled". How and why is it
> >>> disabled? More importantly, **how do I enable it?**

> > # ifup -a
> > ifup: failed to open statefile /run/network/ifstate: No such file
> > or directory
>
> "ifup -a" should bring up all interfaces marked "auto" (or
> "allow-auto") in "/etc/network/interfaces". (Is the latter OK?)
>
> The "networking" init script must (I haven't checked it) create
> "/run/network". etc.
>
> Change the shebang of "/etc/init.d/networking" to "#!/bin/sh -ex"
> and run "/etc/init.d/networking stop" then "/etc/init.d/networking
> start".

Done.
#ping 192.168.0.1
connect: Network is unreachable

:-(

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201311151738.20248.lisi.re...@gmail.com

Re: Investigating dependency trees

On Fri, Nov 15, 2013 at 5:25 PM, Richard Owlett  wrote:
>
> Synaptic and dselect provide this information for *ONE* level down from a
> particular package *IF* an actual installation and repository exist.

apt-cache depends --recurse 
apt-cache rdepends --recurse 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOdo=SwPVH+Gx+OgMR2=Wjp6UxY=ayyru8+sfsbbror+44s...@mail.gmail.com

Investigating dependency trees

2013-11-15 Thread Richard Owlett


I'm working on a very customized minimal install.
A selection criteria for top level applications will be how many 
packages will it pull in that are not used by other packages.
A further optimization may be which packages automatically 
installed by Debian Installer are not needed by actual target 
audience.


Synaptic and dselect provide this information for *ONE* level 
down from a particular package *IF* an actual installation and 
repository exist.


All the information exists in "control" of "*.deb". For my 
purposes there is a lot of irrelevant information also. What I 
envision is a relational database containing the package name, 
Version, Depends, Suggests(doubtful), and Recommends(doubtful) 
fields.


How the data would be displayed in interactive mode - haven't 
decided yet.


In a "batch" mode I envision entering a list of "top level 
packages" and getting out a list of lower level packages required 
and how many (and which of) the "top level packages" required each.


Any suggestions of applications with similar goals?

TIA


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/52865924.2080...@cloud85.net

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Fri, Nov 15, 2013 at 4:59 PM, Andrei POPESCU
 wrote:
> On Vi, 15 nov 13, 16:38:16, Lisi Reisz wrote:
>>>
>>> How is the network configuration handled? Network Manager,
>>> ifupdown, etc.?
>>
>> /etc/network/interfaces file and ifupdown, etc.. (Network Manager and
>> I are not on speaking terms.)
>
> I'd check if Network Manager didn't get pulled in during the
> dist-upgrade.

Unless an NM post-install script is commenting out any non-lo
interface in "/etc/network/interfaces", having NM install itself
should affect the network because its default is not to manage
interfaces that are defined in "/etc/network/interfaces".


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOdo=syjbabqah2fg9obpppxladp3x-h+hcxgbkqlqm1t9z...@mail.gmail.com

Re: Wich port should I use for Xeon E3-1230v2 processor ?

2013-11-15 Thread Jochen Spieker

John Ostrowski:
>
> I recently bought Dell PowerEdge T110 II with  Intel Xeon E3-1230v2
> Processor (3.3GHz, 4C/8T, 8M Cache).
> I don't know which port I should use.

If you used the wrong port your system wouldn't boot. AMD64 is fine for
any non-Itanium CPU from Intel.

> At the moment I am using Debian 7.1.0 AMD64 and I have serious issue.
> Desktop keeps locking all the time. I can move mouse but system does
> not react.

Check /´var/log/syslog and /var/log/Xorg.0.log.

J.
-- 
The houses of parliament make me think of school bullies.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Fri, Nov 15, 2013 at 4:22 PM, Ralf Mardorf
 wrote:
> On Fri, 2013-11-15 at 15:29 +, Tom H wrote:
>>
>> Has eth0 been renamed?
>
> IIRC Lisi killfiled me. I'm aware that Debian still does use init and
> not systemd, but since udev is part of systemd (merged by upstream), it
> anyway might be systemd related.
>
> [root@archlinux rocketmouse]# dmesg | grep renamed
> [   10.540169] systemd-udevd[149]: renamed network interface eth0 to enp3s0

ifconfig -a returned eth0 so there's no renaming to eth1 or one of the
slot-name names.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOdo=sw6+dqvvpxnz_rxzyz5gp2zgrojta4wzyvswx2nl+r...@mail.gmail.com

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Fri, Nov 15, 2013 at 4:13 PM, Lisi Reisz  wrote:
> On Friday 15 November 2013 15:55:59 Lisi Reisz wrote:
>> On Friday 15 November 2013 15:29:00 Tom H wrote:
>>> On Fri, Nov 15, 2013 at 3:06 PM, Lisi Reisz
>>>  wrote:

 I have just upgraded a client's computer to Wheezy. It
 appeared to go well and there was certainly an internet
 connection: it would not have been able to upgrade otherwise!

 Now there is none. I have checked /etc/network/interfaces and
 changed "allow-hotplug" to "auto", just for something to try.
 :-( It made no difference. I pinged the gateway, largely so
 that I could report that I had done so. I got the error
 message "Network is unreachable".

 KControl tells me that eth0 is "disabled". How and why is it
 disabled? More importantly, **how do I enable it?**
>>>
>>> Has eth0 been renamed? What's the output of "ip a"?
>>
>> # ifup -a
>> ifup: failed to open statefile /run/network/ifstate: No such file
>> or directory
>>
>> I misread at first - but "ifup a" produces the same result.
>>
>>> (Did you run "ifup -a" or "ifup eth0" after changing
>>> "allow-hotplug" to "auto"?)
>>
>> Yes - and have restarted several times now. :-(
>>
>> "ifconfig -a" shows eth0 and lo, neither of which has an IP.
>
> # mkdir /run/network
> # ifup lo
>
> lo now has an IP address.
> eth0 is still "unknown interface" :-(

cat /etc/network/interfaces


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOdo=sx95ske452ejmu69zct0+ha+qogtrg_g7ugbkepxyb...@mail.gmail.com

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Fri, Nov 15, 2013 at 3:55 PM, Lisi Reisz  wrote:
> On Friday 15 November 2013 15:29:00 Tom H wrote:
>> On Fri, Nov 15, 2013 at 3:06 PM, Lisi Reisz 
> wrote:


>>> I have just upgraded a client's computer to Wheezy. It appeared
>>> to go well and there was certainly an internet connection: it
>>> would not have been able to upgrade otherwise!
>>>
>>> Now there is none. I have checked /etc/network/interfaces and
>>> changed "allow-hotplug" to "auto", just for something to try. :-(
>>> It made no difference. I pinged the gateway, largely so that I
>>> could report that I had done so. I got the error message
>>> "Network is unreachable".
>>>
>>> KControl tells me that eth0 is "disabled". How and why is it
>>> disabled? More importantly, **how do I enable it?**
>>
>> Has eth0 been renamed? What's the output of "ip a"?



> Thanks, Tom. :-)

You're welcome.


> # ifup -a
> ifup: failed to open statefile /run/network/ifstate: No such file or
> directory
>
> I misread at first - but "ifup a" produces the same result.
>
>> (Did you run "ifup -a" or "ifup eth0" after changing
>> "allow-hotplug" to "auto"?)
>
> Yes - and have restarted several times now. :-(
>
> "ifconfig -a" shows eth0 and lo, neither of which has an IP.

"ip a" == "ip address show" (== "ifconfig -a").

"ifup -a" should bring up all interfaces marked "auto" (or
"allow-auto") in "/etc/network/interfaces". (Is the latter OK?)

The "networking" init script must (I haven't checked it) create
"/run/network". etc.

Change the shebang of "/etc/init.d/networking" to "#!/bin/sh -ex" and
run "/etc/init.d/networking stop" then "/etc/init.d/networking start".


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOdo=SwH-a+fv1RyG_8=k3nhefast4aids0eadn-8ypozux...@mail.gmail.com

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Vi, 15 nov 13, 16:38:16, Lisi Reisz wrote:
> >
> > How is the network configuration handled? Network Manager,
> > ifupdown, etc.?
> 
> /etc/network/interfaces file and ifupdown, etc..  (Network Manager and 
> I are not on speaking terms.)

I'd check if Network Manager didn't get pulled in during the 
dist-upgrade.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Wich port should I use for Xeon E3-1230v2 processor ?

2013-11-15 Thread John Ostrowski

Hi,
I recently bought Dell PowerEdge T110 II with  Intel Xeon E3-1230v2 Processor 
(3.3GHz, 4C/8T, 8M Cache).
I don't know which port I should use.
At the moment I am using Debian 7.1.0 AMD64 and I have serious issue. Desktop 
keeps locking all the time. I can move mouse but system does not react.
Best regards.
John Ostrowski

John Ostrowski
Software Engineer

[CSE Servelec Logo]D +44 1246 437593   P 
+44 1246 437580   F +44 1246 437401   A Rotherside Road, Eckington, Sheffield. 
S21 4HL
E john.ostrow...@cse-servelec.com   W 
www.cse-servelec.com
This email including any attachments is for the named person or persons use 
only. It may contain confidential or legally privileged information. No 
confidentiality or privilege is waived or lost by any mis-transmission. If you 
receive this email in error, please notify the sender, delete the email 
immediately, and remove all copies from your system. You must not, directly or 
indirectly, use, disclose, distribute, print, or copy any part of this message 
if you are not the intended recipient. All opinions expressed in this message 
are that of the individual sender, except where the message states otherwise 
and the sender is so authorised. Any liability (in negligence or otherwise) 
arising from any third party relying on this email is excluded. The company 
reserves the right to monitor all email communication for compliance purposes 
and to protect our business. CSE Servelec is part of the CSE Global (UK) group 
of companies www.cse-globaluk.com. CSE-Global (UK) 
Limited is a subsidiary of CSE Global (Singapore). CSE-Servelec Limited is a 
private limited company registered in England and Wales Co. No. 6879601 UK. VAT 
Number: GB648280518.
P Please consider the environment and do not print this email unless absolutely 
necessary. CSE encourages environmental awareness.

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

Thanks, Andrei,

On Friday 15 November 2013 16:15:20 Andrei POPESCU wrote:
> On Vi, 15 nov 13, 15:06:59, Lisi Reisz wrote:
> > I have just upgraded a client's computer to Wheezy.  It appeared
> > to go well and there was certainly an internet connection: it
> > would not have been able to upgrade otherwise!
> >
> > Now there is  none.  I have checked /etc/network/interfaces and
> > changed "allow-hotplug" to "auto", just for something to try. :-(
> >  It made no difference.  I pinged the gateway, largely so that I
> > could report that I had done so.  I got the error message
> > "Network is unreachable".
> >
> > KControl tells me that eth0 is "disabled".  How and why is it
> > disabled?  More importantly, **how do I enable it?**
>
> How is the network configuration handled? Network Manager,
> ifupdown, etc.?

/etc/network/interfaces file and ifupdown, etc..  (Network Manager and 
I are not on speaking terms.)

Lisi



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201311151638.16831.lisi.re...@gmail.com

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Friday 15 November 2013 16:13:23 Lisi Reisz wrote:
> On Friday 15 November 2013 15:55:59 Lisi Reisz wrote:
> > Thanks, Tom. :-)
> >
> > On Friday 15 November 2013 15:29:00 Tom H wrote:
> > > On Fri, Nov 15, 2013 at 3:06 PM, Lisi Reisz
> > > 
> >
> > wrote:
> > > > I have just upgraded a client's computer to Wheezy.  It
> > > > appeared to go well and there was certainly an internet
> > > > connection: it would not have been able to upgrade otherwise!
> > > >
> > > > Now there is  none.  I have checked /etc/network/interfaces
> > > > and changed "allow-hotplug" to "auto", just for something to
> > > > try.
> > > >
> > > > :-( It made no difference.  I pinged the gateway, largely so
> > > >
> > > > that I could report that I had done so.  I got the error
> > > > message "Network is unreachable".
> > > >
> > > > KControl tells me that eth0 is "disabled".  How and why is it
> > > > disabled?  More importantly, **how do I enable it?**
> > >
> > > Has eth0 been renamed? What's the output of "ip a"?
> >
> > # ifup -a
> > ifup: failed to open statefile /run/network/ifstate: No such file
> > or directory
> >
> > I misread at first - but "ifup a" produces the same result.
> >
> > > (Did you run "ifup -a" or "ifup eth0" after changing
> > > "allow-hotplug" to "auto"?)
> >
> > Yes - and have restarted several times now. :-(
> >
> > "ifconfig -a" shows eth0 and lo, neither of which has an IP.
>
> # mkdir /run/network
> # ifup lo
>
> lo now has an IP address.
> eth0 is still "unknown interface"  :-(

After a reboot, the directory /run/network has disappeared and lo no 
longer has an IP. :-(


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201311151635.09092.lisi.re...@gmail.com

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Fri, 2013-11-15 at 15:29 +, Tom H wrote:
> Has eth0 been renamed?

IIRC Lisi killfiled me. I'm aware that Debian still does use init and
not systemd, but since udev is part of systemd (merged by upstream), it
anyway might be systemd related.

[root@archlinux rocketmouse]# dmesg | grep renamed
[   10.540169] systemd-udevd[149]: renamed network interface eth0 to enp3s0

Hth,
Ralf


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1384532529.661.23.camel@archlinux

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Vi, 15 nov 13, 15:06:59, Lisi Reisz wrote:
> I have just upgraded a client's computer to Wheezy.  It appeared to go 
> well and there was certainly an internet connection: it would not 
> have been able to upgrade otherwise!
> 
> Now there is  none.  I have checked /etc/network/interfaces and 
> changed "allow-hotplug" to "auto", just for something to try. :-(  It 
> made no difference.  I pinged the gateway, largely so that I could 
> report that I had done so.  I got the error message "Network is 
> unreachable". 
> 
> KControl tells me that eth0 is "disabled".  How and why is it 
> disabled?  More importantly, **how do I enable it?**

How is the network configuration handled? Network Manager, ifupdown, 
etc.?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Friday 15 November 2013 15:55:59 Lisi Reisz wrote:
> Thanks, Tom. :-)
>
> On Friday 15 November 2013 15:29:00 Tom H wrote:
> > On Fri, Nov 15, 2013 at 3:06 PM, Lisi Reisz
> > 
>
> wrote:
> > > I have just upgraded a client's computer to Wheezy.  It
> > > appeared to go well and there was certainly an internet
> > > connection: it would not have been able to upgrade otherwise!
> > >
> > > Now there is  none.  I have checked /etc/network/interfaces and
> > > changed "allow-hotplug" to "auto", just for something to try.
> > > :-( It made no difference.  I pinged the gateway, largely so
> > > that I could report that I had done so.  I got the error
> > > message "Network is unreachable".
> > >
> > > KControl tells me that eth0 is "disabled".  How and why is it
> > > disabled?  More importantly, **how do I enable it?**
> >
> > Has eth0 been renamed? What's the output of "ip a"?
>
> # ifup -a
> ifup: failed to open statefile /run/network/ifstate: No such file
> or directory
>
> I misread at first - but "ifup a" produces the same result.
>
> > (Did you run "ifup -a" or "ifup eth0" after changing
> > "allow-hotplug" to "auto"?)
>
> Yes - and have restarted several times now. :-(
>
> "ifconfig -a" shows eth0 and lo, neither of which has an IP.

# mkdir /run/network
# ifup lo

lo now has an IP address.
eth0 is still "unknown interface"  :-(

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201311151613.23228.lisi.re...@gmail.com

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

# dmesg | grep renamed


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1384531778.661.19.camel@archlinux

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

Thanks, Tom. :-)

On Friday 15 November 2013 15:29:00 Tom H wrote:
> On Fri, Nov 15, 2013 at 3:06 PM, Lisi Reisz  
wrote:
> > I have just upgraded a client's computer to Wheezy.  It appeared
> > to go well and there was certainly an internet connection: it
> > would not have been able to upgrade otherwise!
> >
> > Now there is  none.  I have checked /etc/network/interfaces and
> > changed "allow-hotplug" to "auto", just for something to try. :-(
> >  It made no difference.  I pinged the gateway, largely so that I
> > could report that I had done so.  I got the error message
> > "Network is unreachable".
> >
> > KControl tells me that eth0 is "disabled".  How and why is it
> > disabled?  More importantly, **how do I enable it?**
>
> Has eth0 been renamed? What's the output of "ip a"?

# ifup -a
ifup: failed to open statefile /run/network/ifstate: No such file or 
directory

I misread at first - but "ifup a" produces the same result. 

> (Did you run "ifup -a" or "ifup eth0" after changing
> "allow-hotplug" to "auto"?)

Yes - and have restarted several times now. :-(

"ifconfig -a" shows eth0 and lo, neither of which has an IP.

I have checked hardware with a live CD, since it is not beyond the 
bounds of possibility that the card could break coincidentally with 
my finishing the upgrade.  But, not only is it fine, but the results 
above suggest software not hardware.

I am now googling on the error mesage; but all help most welcome!

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201311151555.59162.lisi.re...@gmail.com

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

On Fri, Nov 15, 2013 at 3:06 PM, Lisi Reisz  wrote:
>
> I have just upgraded a client's computer to Wheezy.  It appeared to go
> well and there was certainly an internet connection: it would not
> have been able to upgrade otherwise!
>
> Now there is  none.  I have checked /etc/network/interfaces and
> changed "allow-hotplug" to "auto", just for something to try. :-(  It
> made no difference.  I pinged the gateway, largely so that I could
> report that I had done so.  I got the error message "Network is
> unreachable".
>
> KControl tells me that eth0 is "disabled".  How and why is it
> disabled?  More importantly, **how do I enable it?**

Has eth0 been renamed? What's the output of "ip a"?

(Did you run "ifup -a" or "ifup eth0" after changing "allow-hotplug" to "auto"?)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOdo=SwYGJs3UD058FC=VLreVUJeFHmsJL+n=zc645zsd0z...@mail.gmail.com

Re: eth0 "disabled" after upgrade Squeeze to Wheezy

2013-11-15 Thread basti

Hello Lisi,

Is eth1 up? so check /etc/udev/rules.d/70-persistent-net.rules for
multiple entrys.

Regards,
basti
||
On 15.11.2013 16:06, Lisi Reisz wrote:
> I have just upgraded a client's computer to Wheezy.  It appeared to go 
> well and there was certainly an internet connection: it would not 
> have been able to upgrade otherwise!
>
> Now there is  none.  I have checked /etc/network/interfaces and 
> changed "allow-hotplug" to "auto", just for something to try. :-(  It 
> made no difference.  I pinged the gateway, largely so that I could 
> report that I had done so.  I got the error message "Network is 
> unreachable". 
>
> KControl tells me that eth0 is "disabled".  How and why is it 
> disabled?  More importantly, **how do I enable it?**
>
> Thanks,
> Lisi
>
>

eth0 "disabled" after upgrade Squeeze to Wheezy

I have just upgraded a client's computer to Wheezy.  It appeared to go 
well and there was certainly an internet connection: it would not 
have been able to upgrade otherwise!

Now there is  none.  I have checked /etc/network/interfaces and 
changed "allow-hotplug" to "auto", just for something to try. :-(  It 
made no difference.  I pinged the gateway, largely so that I could 
report that I had done so.  I got the error message "Network is 
unreachable". 

KControl tells me that eth0 is "disabled".  How and why is it 
disabled?  More importantly, **how do I enable it?**

Thanks,
Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201311151506.59325.lisi.re...@gmail.com

Any leiningen user here

2013-11-15 Thread Gian Uberto Lauri

Hello there, 

since I am going to play a bit with clojure, I installed leiningen
using the apt command.

But when I run it, i.e. with the command 

saint@quigley:~
14:57:40 [1] $lein run

I am greeted with this stack trace:

Exception in thread "main" clojure.lang.LispReader$ReaderException: 
java.lang.Exception: EOF while reading
at clojure.lang.LispReader.read(LispReader.java:180)
at clojure.core$read.invoke(core.clj:2884)
at clojure.core$read.invoke(core.clj:2882)
at clojure.main$eval_opt.invoke(main.clj:233)
at clojure.main$initialize.invoke(main.clj:254)
at clojure.main$script_opt.invoke(main.clj:270)
at clojure.main$main.doInvoke(main.clj:354)
at clojure.lang.RestFn.invoke(RestFn.java:482)
at clojure.lang.Var.invoke(Var.java:381)
at clojure.lang.AFn.applyToHelper(AFn.java:178)
at clojure.lang.Var.applyTo(Var.java:482)
at clojure.main.main(main.java:37)
Caused by: java.lang.Exception: EOF while reading
at clojure.lang.LispReader.readDelimitedList(LispReader.java:1043)
at clojure.lang.LispReader$ListReader.invoke(LispReader.java:900)
at clojure.lang.LispReader.read(LispReader.java:145)
... 11 more

Any leiningen user here around can help me? Thank you in advance.

-- 
ing. Gian Uberto Lauri
Solution Developer Senior
Direzione Ricerca e Innovazione
gianuberto.la...@eng.it

Sun Java Certified Programmer

Engineering Ingegneria Informatica spa
Corso Stati Uniti 23/C, 35127 Padova (PD)

Tel. +39-049.8283.517 | main(){printf(&unix["\021%six\012\0"],
Fax  +39-049.8283.569 |(unix)["have"]+"fun"-0x60);}
http://www.eng.it |  David Korn, AT&T Bell Labs
  |  ioccc best One Liner, 1987


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/21126.11352.290162.459...@mail.eng.it

Re: GMail like mail workflow

2013-11-15 Thread Jonathan Dowland

On Fri, Nov 15, 2013 at 11:25:26AM +0100, Florian Lindner wrote:
> - Instead of deleting messages for archiving, move them to some Archiv
> folder. Since archiving is a very frequent action this involves much
> more cliks in the MUA than just deleting. Or some configuration change
> in the client.

Some MUAs have built-in support for archiving with one key (e.g.
Thunderbird/Icedove, 'a'), however *all* mail clients have built-in
support for deleting with one key. I adjusted my mail operation around
that principle, and have filter rules that make archive copies of
incoming mail, so the mail that hits my inbox is a copy that can be
safely deleted.

You need good search/indexing support in your MUA(s) for this to work.

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131115132800.ga8...@bryant.redmars.org

Re: GMail like mail workflow

On Vi, 15 nov 13, 11:25:26, Florian Lindner wrote:
> 
> How would you do that? I'm also open to entirely different
> suggestions! What I want are basically these things:
> - Never delete legitimate mail
> - Use the Inbox as a workspace for mails that are still of some
> interest. This can also be quite old mail, time based archiving does
> not work.
> - Have some kind of mail archive.

I'm using mutt to access my Gmail account with a very similar workflow. 
If I remember correctly the necessary bits are these:

set spoolfile=imaps://imap.gmail.com/INBOX
set mbox="imaps://imap.gmail.com/[Gmail]/All Mail"
set keep_flagged
set move=ask-yes

With this configuration mutt will ask (and default to "Yes" so I can 
just press Enter) to move all read e-mail from $spoolfile to the $mbox 
folder. If I want to keep something around I just flag it (Shift+F by 
default).

Hope this helps,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt

signature.asc
Description: Digital signature

GMail like mail workflow

2013-11-15 Thread Florian Lindner

Hello!

I'm about to migrate my mails from GMail back to my self hosted
solution, using Dovecot imap server on Debian Stable.

I really like the gmail workflow:

- (Almost) all mail goes to inbox.
- Most mail is read and not important anymore, it is archived and
moved to "all messages".
- Inbox stays more or less clean, with only mails that are still of
some interest.
- Mail (except Spam) is never deleted, just archived.

How can I achieve such a workflow using Dovecot and some MUA
(Roundcube and probably KMail).

- I can simply delete messages that I want to archive, Trash will
never be purged. Problems: Some mail clients have settings like "Purge
Trash at exit", so my mail is always in danger of being deleted
accidently. Futhermore it does not really have the semantics of what I
am actually doing.

- Instead of deleting messages for archiving, move them to some Archiv
folder. Since archiving is a very frequent action this involves much
more cliks in the MUA than just deleting. Or some configuration change
in the client.

How would you do that? I'm also open to entirely different
suggestions! What I want are basically these things:
- Never delete legitimate mail
- Use the Inbox as a workspace for mails that are still of some
interest. This can also be quite old mail, time based archiving does
not work.
- Have some kind of mail archive.

Thanks!

Florian

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/cajtbfr-3bzbw0bgzbgyanqujt-agdt7rdfpcqbx4twdafwq...@mail.gmail.com

Re: Procedure to uninstall nvidia drivers and restore nouveau