On 2022-05-08 22:58, Hussein Yahia wrote:
Hi,
I'm new to Linux, sorry if my question is naive.
I just installed debian 11 on my computer. It's wire-connected to
internet. I have another computer, a mac, which is connected through
wifi.
I can connect from my mac to the Linux desktop. But I can't
On Sun, May 8, 2022 at 5:06 PM Hussein Yahia wrote:
>
>
> I can connect from my mac to the Linux desktop. But I can't connect
> from the Linux to the mac: when I go in the "Network" directory, the
> mac does not appear. I installed smb on the Linux desktop.
>
>
I'm suspecting that you need to go
On Mon, 09 May 2022 04:10:01 +0200 Charles Curley
wrote:
> On Mon, 09 May 2022 01:31:35 +0200
> Hussein Yahia wrote:
>
>> What exactly do you mean by "connect"? SSH? ping? If you mean via
>> SMB, that suggests you successfully set the Linux computer up as
>> an SMB server. Did you?
>>
>> I don'
On Mon, 09 May 2022 01:31:35 +0200
Hussein Yahia wrote:
> > What exactly do you mean by "connect"? SSH? ping? If you mean via
> > SMB,
> > that suggests you successfully set the Linux computer up as an SMB
> > server. Did you?
>
> I don't remeber to have installed smb on my Linux. I just downl
Hi Charles,
Thank you for quick answering me.
I'm going to guess that this is a simple network, such as a home,
> with
> just the two computers on it.
Yes !
> What exactly do you mean by "connect"? SSH? ping? If you mean via
> SMB,
> that suggests you successfully set the Linux computer up as
On Sun, 08 May 2022 23:58:28 +0200
Hussein Yahia wrote:
> I'm new to Linux, sorry if my question is naive.
Your question isn't naive. But we need a lot more information from you
in order to help you.
Some of it may be obtained by executing command line commands we
provide. Open a terminal, copy
You might want to take a look at "Computer Networks" by A.S. Tanenbaum and D.J.
Wetherall. It's available for free online at
https://docs.google.com/viewer?a=v&pid=sites&srcid=ZGVmYXVsdGRvbWFpbnxza21pbmh8Z3g6NjQxMTI2MmYxMTAwZmNjZQ
Or you can buy a copy from your local bookseller.
Enjoy!
R
On 5/6/2022 12:36 AM, Tom Browder wrote:
On Thu, May 5, 2022 at 16:07 David Christensen
wrote:
On 5/5/22 12:31, john doe wrote:
At the time I set up this, I googled this subject and came to the
conclusion that SSH through VPN was a better fit (flexibility, two
layers of security, VPN advanta
Tom Browder wrote:
> On Thu, May 5, 2022 at 16:07 David Christensen
> wrote:
>
> > On 5/5/22 12:31, john doe wrote:
> >
> > > At the time I set up this, I googled this subject and came to the
> > > conclusion that SSH through VPN was a better fit (flexibility, two
> > > layers of security, VPN a
On Thu, 5 May 2022 17:36:14 -0500
Tom Browder wrote:
> On Thu, May 5, 2022 at 16:07 David Christensen
> wrote:
>
> > On 5/5/22 12:31, john doe wrote:
> >
> > > At the time I set up this, I googled this subject and came to the
> > > conclusion that SSH through VPN was a better fit (flexibility,
On Thu, May 5, 2022 at 16:07 David Christensen
wrote:
> On 5/5/22 12:31, john doe wrote:
>
> > At the time I set up this, I googled this subject and came to the
> > conclusion that SSH through VPN was a better fit (flexibility, two
> > layers of security, VPN advantages when connecting on public
On 5/5/22 12:31, john doe wrote:
At the time I set up this, I googled this subject and came to the
conclusion that SSH through VPN was a better fit (flexibility, two
layers of security, VPN advantages when connecting on public wifi) for me.
I prefer to have SSH available both via old-school p
On 5/4/22 09:07, john doe wrote:
> Here are some comments in addition to this thread:
> - Do not use the router capability provided by your ISP.
> This is mainly to avoid letting your ISP remotely control the thing and
> disable the firewall for example.
>
> If you can, use your own router.
>
> If
On 5/5/2022 4:34 PM, Tom Browder wrote:
On Wed, May 4, 2022 at 11:07 john doe wrote:
On Tue, May 3, 2022 at 15:18 john doe wrote:
On 5/3/2022 9:42 PM, Tom Browder wrote:
- Use VPN to access your servers remotely.
I find it easier to use a VPN (responsible for public remote connection)
t
On Wed, May 4, 2022 at 11:07 john doe wrote:
> > On Tue, May 3, 2022 at 15:18 john doe wrote:
> >> On 5/3/2022 9:42 PM, Tom Browder wrote:
>>> I'm about to sign up for a fixed IPv4 address to my home. I know a bit
> >>> about setting up simple internal networks, but want to make sure I'm
>>
On 5/3/2022 10:35 PM, Tom Browder wrote:
On Tue, May 3, 2022 at 15:18 john doe wrote:
On 5/3/2022 9:42 PM, Tom Browder wrote:
I'm about to sign up for a fixed IPv4 address to my home. I know a bit
about setting up simple internal networks, but want to make sure I'm
doing it all correctly and
On 4/5/22 12:57 pm, to...@tuxteam.de wrote:
On Wed, May 04, 2022 at 04:27:52AM +0800, Jeremy Ardley wrote:
[...]
[...] NAT in itself
provides quite good security because internal hosts can't be scanned by
attackers.
Uh, oh. I think general opinion these days disagree with this
statement stro
On Wed, May 04, 2022 at 04:27:52AM +0800, Jeremy Ardley wrote:
[...]
> [...] NAT in itself
> provides quite good security because internal hosts can't be scanned by
> attackers.
Uh, oh. I think general opinion these days disagree with this
statement strongly (see e.g. [1], but this has been roug
On 5/3/22 12:42, Tom Browder wrote:
I'm about to sign up for a fixed IPv4 address to my home. I know a bit
about setting up simple internal networks, but want to make sure I'm
doing it all correctly and securely. Does anyone have a good book they
recommend for such use?
On 5/3/22 13:35, Tom Br
On Tue, May 3, 2022 at 17:27 Bob Weber wrote:
...
> Have you thought of using a small VM in the cloud?
>
Yes, I have, Bob, and I have a Digital Ocean account and plan to use it for
another use case soon. But I do love having my master source and webserver
where I can touch them and fix hardware p
On 5/3/22 17:14, Tom Browder wrote:
I appreciate all the responses, and I realize, once again, that I should have
given a little more background for the question:
I have been running 10+ websites using SNI on Apache on two leased remote
servers for many years. I am now moving the whole opera
On Tue, May 3, 2022 at 16:21 Greg Wooledge wrote:
...
You think your home Internet connection is going to be able to handle
> this traffic?
The sites are historically low traffic, but I'll watch out for problems.
Our current ISP is AT&T and they are laying fiber quickly in my area.
> In additi
On Tue, May 03, 2022 at 04:14:40PM -0500, Tom Browder wrote:
> I have been running 10+ websites using SNI on Apache on two leased remote
> servers for many years.
You think your home Internet connection is going to be able to handle
this traffic?
> In addition to the webserver being accessed exte
On Tue, May 3, 2022 at 14:42 Tom Browder wrote:
> I'm about to sign up for a fixed IPv4 address to my home. I know a bit
> about setting up simple internal networks, but want to make sure I'm
> doing it all correctly and securely. Does anyone have a good book they
> recommend for such use?
I ap
Tom Browder wrote:
> I'm considering HaProxy downsteam from the router.
>
> That also brings the question, why do you need a static IPv4 address?
If you want a service inside your network to be available to
people outside your network (i.e. on the Internet), they need to
be able to name it and g
Tom Browder wrote:
> I'm about to sign up for a fixed IPv4 address to my home. I know a bit
> about setting up simple internal networks, but want to make sure I'm
> doing it all correctly and securely. Does anyone have a good book they
> recommend for such use?
Almost certainly what you want is
On Tue, 2022-05-03 at 14:30 -0600, Charles Curley wrote:
> [...]
> You will want to parcel out IP addresses and host names on your home
> network, so DNS and DHCP. There are other programs to do those things,
> but bind and dhcpd are classics, and talk to each other.
Or dnsmasq which does both job
On Tue, May 3, 2022 at 15:18 john doe wrote:
> On 5/3/2022 9:42 PM, Tom Browder wrote:
> > I'm about to sign up for a fixed IPv4 address to my home. I know a bit
> > about setting up simple internal networks, but want to make sure I'm
> > doing it all correctly and securely. Does anyone have a go
On Tue, 3 May 2022 14:42:16 -0500
Tom Browder wrote:
> I'm about to sign up for a fixed IPv4 address to my home. I know a bit
> about setting up simple internal networks, but want to make sure I'm
> doing it all correctly and securely. Does anyone have a good book they
> recommend for such use?
On 4/5/22 4:18 am, john doe wrote:
What do you mean by "correctly and securly", the networking is never
secure.
Depending on what you need, you might want firewall ...
That also brings the question, why do you need a static IPv4 address?
For almost all domestic installations a single stati
On 5/3/2022 9:42 PM, Tom Browder wrote:
I'm about to sign up for a fixed IPv4 address to my home. I know a bit
about setting up simple internal networks, but want to make sure I'm
doing it all correctly and securely. Does anyone have a good book they
recommend for such use?
What do you mean by
On Friday, February 01, 2019 10:27:05 AM Curt wrote:
> Maybe inconclusive. What's a gnome application, anyway?
I'd like to try to answer that:
* I would say that a GNOME application is one that is in some sense
supported by the GNOME (I guess GNU?) organization -- it is probably hosted
(i.e.
On 2019-02-01, Kenneth Parker wrote:
> --1724fb0580ce49f7
> Content-Type: text/plain; charset="UTF-8"
>
> On Thu, Jan 31, 2019 at 4:21 AM Joe wrote:
>
>
>> ... NM is a Gnome application. ...
>>
>
>
> That's funny: Last year, I installed Kubuntu (not Debian, but same Package
> Manager
On Fri 01 Feb 2019 at 00:19:09 (-0500), Kenneth Parker wrote:
> On Thu, Jan 31, 2019 at 4:21 AM Joe wrote:
>
>
> > ... NM is a Gnome application. ...
> >
>
>
> That's funny: Last year, I installed Kubuntu (not Debian, but same Package
> Manager) and, even though no Gnome, Network Manager was
On Thu, Jan 31, 2019 at 4:21 AM Joe wrote:
> ... NM is a Gnome application. ...
>
That's funny: Last year, I installed Kubuntu (not Debian, but same Package
Manager) and, even though no Gnome, Network Manager was installed.
--
> Joe
>
Kenneth Parker
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Also in reply to:
20190131092106.2a6b3...@jresid.jretrading.com
q2ugqc$4kcj$1...@blaine.gmane.org
20190131115051.3276c...@jresid.jretrading.com
On 2019-01-31 09:21 + "Joe" wrote:
>By 'removing' Cinnamon, do you mean that you uninstalled it?
>I
On Thu, 31 Jan 2019 10:57:42 +0100
deloptes wrote:
> Joe wrote:
>
> > NM is a Gnome application.
>
> Are you sure? IMO it is not a gnome only tool although it is
> developed by gnome
> https://developer.gnome.org/NetworkManager/stable/NetworkManager.html
>
That's what I mean. It was develop
Joe wrote:
> NM is a Gnome application.
Are you sure? IMO it is not a gnome only tool although it is developed by
gnome
https://developer.gnome.org/NetworkManager/stable/NetworkManager.html
Description-en: network management framework (daemon and userspace tools)
NetworkManager is a system netw
On Thu, 31 Jan 2019 07:21:10 +
"Harley A.W. Lorenzo" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> After digging around more, the service file isn't just the only thing
> gone, the entire package has been removed as well. Honestly, I have
> no idea what could have resulted i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
After digging around more, the service file isn't just the only thing gone,
the entire package has been removed as well. Honestly, I have no idea what could
have resulted in this package being removed suddenly given the only circumstance
that changed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thank you.
To my surprise, the service was masked. I unmasked it, and the service is
completely gone now. I'm going to write it back in and see if this fixes
the issue, but now I'm very curious why the service masked itself after
switching desktop e
On 1/31/2019 3:04 AM, Harley A.W. Lorenzo wrote:
> On a Debian testing laptop that I switched from Cinnamon to XFCE4 (without
> xfce4-goodies initially) rebooting into the new desktop environment caused
> all my network interfaces except from loopback to fail. The network manager
> doesn't appea
Le primidi 11 fructidor, an CCXXIV, Michael Milliman a écrit :
> And the difference??
This question was already asked and answered.
signature.asc
Description: Digital signature
On 08/26/2016 06:19 AM, Nicolas George wrote:
Le decadi 10 fructidor, an CCXXIV, Pol Hallen a écrit :
I suggests him to separate each networks:
floor1 - 192.168.1.0/24
floor2 - 192.168.2.0/24
floor3 - 192.168.3.0/24
floor4 - 192.168.4.0/24
Why?
You give way too few information about the nee
On Fri, 26 Aug 2016, Pol Hallen wrote:
> >Why do you want to separate it?
>
> try to discover a network problem when there're many many devices
> online... if you separate is become "easy" audit network
You divide number of computers affected by a problem by 4 and
add many new problems caused b
sorry for the incomplete question: each floor will has not more than
20/30 devices (mixed: wifi + wired). We connect some AP to switch 1-4
and thanks for all replies :-)
Pol
On 08/26/2016 12:43 PM, Pol Hallen wrote:
Hi all, I'm helping a friend to create a small network on his office (4
floor
Why do you want to separate it?
try to discover a network problem when there're many many devices
online... if you separate is become "easy" audit network
Is your organisation divided into floors or
into sections, divisions etc...?
this scenario by floors. Is it strange? :-|
If you reall
On Fri, Aug 26, 2016 at 6:19 AM, Nicolas George wrote:
>
> (Also, I wonder why people always fiddle with the cumbersome 192.168
> instead
> of going for simply 10.)
>
>
While it shouldn't matter, I've seen some serious networking brain damage
if your router or the border router happen to be both
Le 26/08/2016 à 14:22, Debian maillists a écrit :
If you really need to separate your organisation sections
use managed switches and VLANs, not subnetworks.
How do you use VLANs without subnetting ?
Le 26/08/2016 à 13:55, Karl E. Jorgensen a écrit :
You may want to for different networks to allow for future
expansion. Your current scheme will only allow for max ~ 250 clients
per floor. And you have the IP ranges rubbing against each other
without gaps...
It is usually a good idea to leave
On Fri, 26 Aug 2016, Pol Hallen wrote:
> I suggests him to separate each networks:
>
> floor1 - 192.168.1.0/24
> floor2 - 192.168.2.0/24
> floor3 - 192.168.3.0/24
> floor4 - 192.168.4.0/24
Why do you want to separate it?
And if you really need separation then why just on floor
borders? Is your o
On Fri, Aug 26, 2016 at 12:43:30PM +0200, Pol Hallen wrote:
> Hi all, I'm helping a friend to create a small network on his office (4
> floors)
>
> I suggests him to separate each networks:
>
> floor1 - 192.168.1.0/24
> floor2 - 192.168.2.0/24
> floor3 - 192.168.3.0/24
> floor4 - 192.168.4.0/24
>
Le decadi 10 fructidor, an CCXXIV, Pascal Hambourg a écrit :
> What's cumbersome in 192.168 ? More digits to type ?
Yes, that, and all that goes along: readability and ease to see typos, ease
to remember for non-tech-savvy people, etc.
signature.asc
Description: Digital signature
Le 26/08/2016 à 13:19, Nicolas George a écrit :
You give way too few information about the needs of your friend to allow
anyone to give relevant advice.
Indeed. A "best" solution is only optimal for a given set of requirements.
(Also, I wonder why people always fiddle with the cumbersome 192
Le decadi 10 fructidor, an CCXXIV, Pol Hallen a écrit :
> I suggests him to separate each networks:
>
> floor1 - 192.168.1.0/24
> floor2 - 192.168.2.0/24
> floor3 - 192.168.3.0/24
> floor4 - 192.168.4.0/24
Why?
You give way too few information about the needs of your friend to allow
anyone to gi
Hi Dan
1. Use a switch for each floor, connect them individually to a
router. All cross-floor communication will need to pass through
the router. This is good for control - you can do firewall
functions between floors as well as to the outside.
nice :-)
3. Use a switch for each floor and con
On Fri, Aug 26, 2016 at 12:43:30PM +0200, Pol Hallen wrote:
> Hi all, I'm helping a friend to create a small network on his office (4
> floors)
>
> I suggests him to separate each networks:
>
> floor1 - 192.168.1.0/24
> floor2 - 192.168.2.0/24
> floor3 - 192.168.3.0/24
> floor4 - 192.168.4.0/24
>
On Tue, Aug 9, 2016 at 8:16 PM, Tom Browder wrote:
> I have read the current Debian networking docs on the subject
> (https://wiki.debian.org/NetworkConfiguration#iproute2_method). I
> want to use at least two IPv4 static addresses on the same physical
> NIC. Following examples I have tried this
Le 10/08/2016 à 14:43, Tom Browder a écrit :
$ ip -4 addr
1: lo: mtu 65536 qdisc noqueue state UNKNOWN
group default
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
inet 192.168.0.17/24 br
On Wed, Aug 10, 2016 at 7:13 AM, Pascal Hambourg wrote:
> Le 10/08/2016 à 13:22, Tom Browder a écrit :
>>
>>
>> Ping from the test host itself to its primary first alias IP:
>>
>> PING 192.168.0.18 (192.168.0.18) 56(84) bytes of data.
>>>
>>> From 192.168.0.17 icmp_seq=1 Destination Host Unreachab
Le 10/08/2016 à 13:22, Tom Browder a écrit :
Ping from the test host itself to its primary first alias IP:
PING 192.168.0.18 (192.168.0.18) 56(84) bytes of data.
From 192.168.0.17 icmp_seq=1 Destination Host Unreachable
It really looks like the secondary address is not configured on the
hos
On Wednesday, August 10, 2016, Pascal Hambourg wrote:
>
> Le 10/08/2016 à 03:16, Tom Browder a écrit :
>>
>> Then, as root, I executed "service networking restart" and all looked
>> well until I logged in to another host and tried to ping the new IP
>> and got no good ping.
>
> Can you elaborate "
Le 10/08/2016 à 03:16, Tom Browder a écrit :
Then, as root, I executed "service networking restart" and all looked
well until I logged in to another host and tried to ping the new IP
and got no good ping.
Can you elaborate "all looked well" and "no good ping" ?
Commands, results ?
What's the
Hi,
> I have read the current Debian networking docs on the subject
> (https://wiki.debian.org/NetworkConfiguration#iproute2_method).
> I want to use at least two IPv4 static addresses on the same physical NIC.
[..]
# The primary network interface
allow-hotplug eth0
iface eth0 inet static
ad
Le 28/07/2016 à 20:47, Ric Moore a écrit :
On 07/28/2016 04:44 AM, Steve Matzura wrote:
ifconfig -a
eth0 Link encap:Ethernet HWaddr bc:5f:f4:5b:80:09
inet addr:192.168.1.130 Bcast:192.168.1.255
You might be caught up in an "improvement"
ric@iam:~$ sudo ifconfig
[sudo] pas
Le 28/07/2016 à 20:13, Pascal Hambourg a écrit :
Le 28/07/2016 à 11:26, Reco a écrit :
Check your Ethernet cable. NO-CARRIER either means that the cable is
unplugged from your NIC, or from whenever other end of the cable should
be plugged to, or the cable itself is damaged.
Or the internet po
Damn, I hit send without checking send to:
Forwarded Message
Subject: Re: Networking nonfunctional on 8.0
Date: Thu, 28 Jul 2016 14:46:19 -0400
From: Ric Moore
To: Steve Matzura
On 07/28/2016 04:44 AM, Steve Matzura wrote:
ifconfig -a
eth0 Link encap:Ethernet
Le 28/07/2016 à 11:26, Reco a écrit :
Check your Ethernet cable. NO-CARRIER either means that the cable is
unplugged from your NIC, or from whenever other end of the cable should
be plugged to, or the cable itself is damaged.
Or the internet port is damaged, or the remote port is damaged or di
Yes. While I was waiting for a reply, I did try another, and either
the connector has gone bad, or some other thing, because that seems to
have been the problem. Very odd that it would fail in the manner which
it did, just died in the middle of the day.
On Thu, 28 Jul 2016 12:26:16 +0300, you wrot
Hi.
On Thu, Jul 28, 2016 at 04:44:09AM -0400, Steve Matzura wrote:
> 2: eth0: mtu 1500 qdisc pfifo_fast
> state DOWN group default qlen 1000
Check your Ethernet cable. NO-CARRIER either means that the cable is
unplugged from your NIC, or from whenever other end of the cable should
be plu
On Wed, 27 Jul 2016 20:46:23 +0200, you wrote:
>Le 27/07/2016 à 15:43, Steve Matzura a écrit :
>> My 8.0 system has been running great up until Monday evening when
>> users started reporting they were unable to connect. Sure enough, I
>> couldn't even connect from my LAN. I rebooted, looked at mes
Le 27/07/2016 à 15:43, Steve Matzura a écrit :
My 8.0 system has been running great up until Monday evening when
users started reporting they were unable to connect. Sure enough, I
couldn't even connect from my LAN. I rebooted, looked at messages from
dmesg, and saw nothing unusual--nothing that
This turned out to be a hardware problem after all - short in an
ethernet cable. Though I don't understand how I got quite the symptoms I
did, it has now all been working for a couple of days so I guess that
was it.
Graham
On 03/11/15 15:33, Graham Seaman wrote:
> On 03/11/15 15:15, Renaud (Ron)
On 03/11/15 15:15, Renaud (Ron) OLGIATI wrote:
> On Tue, 3 Nov 2015 12:49:44 +
> Graham Seaman wrote:
>
>> For some years I've been using a debian system as my household
>> firewall/router. It's been sitting quietly working without any major
>> changes, but has suddenly stopped doing so follow
On Tue, 3 Nov 2015 12:49:44 +
Graham Seaman wrote:
> For some years I've been using a debian system as my household
> firewall/router. It's been sitting quietly working without any major
> changes, but has suddenly stopped doing so following my last aptitude
> update/upgrade.
> Any suggesti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I've written a new script to promote the correct use of kernel options
and queue disciplines for improving network performance in Linux.
I'm keen for feeback technical or not.
https://github.com/mikejonesey/net-check
Kind Regards,
Mike
On Thursday, August 14, 2014 10:10:02 PM UTC+5:30, Michael Biebl wrote:
> Am 14.08.2014 16:02, schrieb Rusi Mody:
> > On Thursday, August 14, 2014 3:40:03 PM UTC+5:30, Michael Biebl wrote:
> >> Am 14.08.2014 um 05:32 schrieb Rusi Mody:
> >>> Aug 14 08:13:15 debian64 pppd[594]: Couldn't open the /de
On Tue, 19 Aug 2014, Chris Bannister wrote:
> On Mon, Aug 18, 2014 at 05:38:13AM -0700, Rusi Mody wrote:
> > More specifically my concerns are:
> > 1. Which apt package 'owns' which file?
>
> Use 'dpkg -S' e.g.:
And if you need to do this often, I recommend the "dlocate" package.
--
"One disk
On Mon, Aug 18, 2014 at 05:38:13AM -0700, Rusi Mody wrote:
> More specifically my concerns are:
> 1. Which apt package 'owns' which file?
Use 'dpkg -S' e.g.:
root@tal:~# dpkg -S /bin/systemd
systemd: /bin/systemd
root@tal:~# dpkg -S /lib/systemd/systemd
systemd: /lib/systemd/systemd
--
"If you'
On Thursday, August 14, 2014 10:10:02 PM UTC+5:30, Michael Biebl wrote:
> Am 14.08.2014 16:02, schrieb Rusi Mody:
> > On Thursday, August 14, 2014 3:40:03 PM UTC+5:30, Michael Biebl wrote:
> >> Am 14.08.2014 um 05:32 schrieb Rusi Mody:
> >>> Aug 14 08:13:15 debian64 pppd[594]: Couldn't open the /de
On Thu, Aug 14, 2014 at 12:14 PM, Rusi Mody wrote:
> On Thursday, August 14, 2014 9:10:02 PM UTC+5:30, Tom H wrote:
>> On Thu, Aug 14, 2014 at 10:32 AM, Rusi Mody wrote:
>>>
>>> To add to my earlier report:
>>> I managed to remove graphviz and its associated libraries.
>>> So that now aptitude dis
On Thursday, August 14, 2014 10:10:02 PM UTC+5:30, Michael Biebl wrote:
> Am 14.08.2014 16:02, schrieb Rusi Mody:
> > On Thursday, August 14, 2014 3:40:03 PM UTC+5:30, Michael Biebl wrote:
> >> Am 14.08.2014 um 05:32 schrieb Rusi Mody:
> >>> Aug 14 08:13:15 debian64 pppd[594]: Couldn't open the /de
On Thursday, August 14, 2014 3:40:03 PM UTC+5:30, Michael Biebl wrote:
> Am 14.08.2014 um 05:32 schrieb Rusi Mody:
> > Aug 14 08:13:15 debian64 pppd[594]: Couldn't open the /dev/ppp device: No
> > such file or directory
> Since you don't have the /dev/ppp device, I assume you are not using
> udev
Am 14.08.2014 16:02, schrieb Rusi Mody:
> On Thursday, August 14, 2014 3:40:03 PM UTC+5:30, Michael Biebl wrote:
>> Am 14.08.2014 um 05:32 schrieb Rusi Mody:
>>> Aug 14 08:13:15 debian64 pppd[594]: Couldn't open the /dev/ppp device: No
>>> such file or directory
>
>> Since you don't have the /dev
On Thursday, August 14, 2014 9:10:02 PM UTC+5:30, Tom H wrote:
> On Thu, Aug 14, 2014 at 10:32 AM, Rusi Mody wrote:
> > To add to my earlier report:
> > I managed to remove graphviz and its associated libraries.
> > So that now aptitude dist-upgrade gives me only 1 'issue' :
> > The following pack
On Thu, Aug 14, 2014 at 10:32 AM, Rusi Mody wrote:
>
> To add to my earlier report:
>
> I managed to remove graphviz and its associated libraries.
>
> So that now aptitude dist-upgrade gives me only 1 'issue' :
>
> The following packages have unmet dependencies:
> systemd-sysv : Conflicts: sysvin
On Thursday, August 14, 2014 8:00:03 PM UTC+5:30, Rusi Mody wrote:
> On Thursday, August 14, 2014 3:40:03 PM UTC+5:30, Michael Biebl wrote:
> > Could you please post the version of udev (and systemd) you are using?
>
>
> Thanks Michael
To add to my earlier report:
I managed to remove graphviz a
On Thursday, August 14, 2014 3:40:03 PM UTC+5:30, Michael Biebl wrote:
> Am 14.08.2014 um 05:32 schrieb Rusi Mody:
> > Aug 14 08:13:15 debian64 pppd[594]: Couldn't open the /dev/ppp device: No
> > such file or directory
> Since you don't have the /dev/ppp device, I assume you are not using
> udev
Am 14.08.2014 um 05:32 schrieb Rusi Mody:
> Aug 14 08:13:15 debian64 pppd[594]: Couldn't open the /dev/ppp device: No
> such file or directory
Since you don't have the /dev/ppp device, I assume you are not using
udev 208-7?
Could you please post the version of udev (and systemd) you are using?
On Tuesday, August 12, 2014 3:20:02 PM UTC+5:30, Andrei POPESCU wrote:
> On Lu, 11 aug 14, 07:57:05, Rusi Mody wrote:
> > If I start from grub using init=/bin/systemd it boots but networking
> > does not work.
>
>
> Please attach the file 'bootlog' after running:
>
> journalctl -alb > bootlo
On Lu, 11 aug 14, 07:57:05, Rusi Mody wrote:
>
> If I start from grub using init=/bin/systemd it boots but networking
> does not work.
Please attach the file 'bootlog' after running:
journalctl -alb > bootlog
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discus
On Friday 13 June 2014 20:11:37 Bret Busby wrote:
> On 14/06/2014, Lisi Reisz wrote:
> > On Saturday 07 June 2014 08:35:14 Lisi Reisz wrote:
> >> Two questions. And yes, I am googling and RTFMing, but I am left with
> >> two
> >> immediate questions. And as of now I have not got access to the de
On Sat 14 Jun 2014 at 03:11:37 +0800, Bret Busby wrote:
> 1. The use of the acronyms can make it difficult to understand such
> messages. After a while, I believe that figured out the "AIO" (= All
> in One?), but I do not understand the "ULD". If people could avoid the
> use of acronyms, it would
On 14/06/2014, Lisi Reisz wrote:
> On Saturday 07 June 2014 08:35:14 Lisi Reisz wrote:
>> Two questions. And yes, I am googling and RTFMing, but I am left with
>> two
>> immediate questions. And as of now I have not got access to the device
>> and
>> network in question. I am trying to do my "h
On Saturday 07 June 2014 08:35:14 Lisi Reisz wrote:
> Two questions. And yes, I am googling and RTFMing, but I am left with two
> immediate questions. And as of now I have not got access to the device and
> network in question. I am trying to do my "homework" in advance.
>
> The AIO in question
On Sat, 7 Jun 2014 08:35:14 +0100
Lisi Reisz wrote:
Hello Lisi,
>2) Can it scan over the network? Again, I assume so, but would be
Scanning can be controlled by any computer with the correct software and
access rights.
--
Regards _
/ ) "The blindingly obvious is
On Saturday 07 June 2014 11:13:21 ken wrote:
> On 06/07/2014 04:11 AM Lisi Reisz wrote:
> > On Saturday 07 June 2014 08:35:14 Lisi Reisz wrote:
> >> Two questions. And yes, I am googling and RTFMing, but I am left with
> >> two immediate questions. And as of now I have not got access to the
> >>
On Saturday 07 June 2014 11:18:24 Brian wrote:
> On Sat 07 Jun 2014 at 08:35:14 +0100, Lisi Reisz wrote:
> > 1) I assume that if the printer is connected by ethernet to a router,
> > amd that router is a wireless router, the printer can be controlled from
> > a laptop wirelessly connected to the r
On Sat 07 Jun 2014 at 08:35:14 +0100, Lisi Reisz wrote:
> 1) I assume that if the printer is connected by ethernet to a router, amd
> that router is a wireless router, the printer can be controlled from a laptop
> wirelessly connected to the router. Is this correct?
Your printer speaks ipp. S
On 06/07/2014 04:11 AM Lisi Reisz wrote:
On Saturday 07 June 2014 08:35:14 Lisi Reisz wrote:
Two questions. And yes, I am googling and RTFMing, but I am left with two
immediate questions. And as of now I have not got access to the device and
network in question. I am trying to do my "homework
1 - 100 of 561 matches
Mail list logo
