Didn't the Debian Constitution ultimately help in screwing that distro
up? Or was it some other bureaucratic device?
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Agree
Indeed thats the issue,
And also the reason why things need to be though in a different manner
hence not bureaucratic.
n.
On 09/28/2015 10:04 AM, Nuno Magalhães wrote:
> Didn't the Debian Constitution ultimately help in screwing that
> di
On 26/09/15 19:39, Steve Litt wrote:
> On Sat, 26 Sep 2015 16:34:58 +0200
> John Crisp wrote:
>
>> On 25/09/15 17:07, Hleb Valoshka wrote:
>
>>> I don't see any reason to throw away wicd and replace it with your
>>> tool.
>>
>> Excellent. Who said you had too ? Is it compulsory or obligatory ? I
Thanks Edward for your great effort, commitment and persistence and
Aitor for packaging.
I have yet to work out how to automatically connect on boot. A manpage
is needed.
An installation and some live images here use (self-compiled) eudev. The
wireless inteface is not necessarily wlanx but a
To connect automatically on boot you only need to pass --auto-conn
parameter to netman, the frontend GUI. I use it that way and it
connects as soon as I log into XFCE4. Configure your desktop or window
manager to run netman with --auto-conn as a parameter.
So, the command should be like this:
/usr
You can use udev to map wlan0 to the new device name so that netman would work.
I was thinking about a configuration file for the backend so that it
would be able to substitute wlan0 and eth0 with other device names as
set up by the user. I was thinking about this format:
wlanX=wireless-device-nam
Hi All,
My next coding will be to add support for network interfaces other
than wlan0 and eth0. Regarding this, I would like to have your ideas
about how should I go not to minimally disrupt the already existing C
code that is already working.
My present idea is this:
a) To connect to a wifi the
@Edward and David:
Don't know if this is helpful or if you've already seen it...
Here's how the new network interface naming scheme works (or is supposed
to work):
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
From that page:
"By default, systemd v197 will n
fsmithred writes:
> @Edward and David:
>
> Don't know if this is helpful or if you've already seen it...
>
> Here's how the new network interface naming scheme works (or is supposed
> to work):
> http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
Something worthy o
If I were to write this implementation I would do it this way:
i) do the above as described to obtain a list of devices
ii) sort the list alphabetically by name
iii) rename the list as usual.
That would get rid of all randomness.
Edward
On 28/09/2015, Rainer Weikusat wrote:
> fsmithred writes
Ooops, it gets rid of randomness *provided the same hardware is used*
but it should work if one changes slots etc.
On 28/09/2015, Edward Bartolo wrote:
> If I were to write this implementation I would do it this way:
> i) do the above as described to obtain a list of devices
> ii) sort the list a
Il 26/set/2015 20:54, "Hendrik Boom" ha scritto:
> I looked for a netman package in aptitude; it doesn't seem to be around
> in jessie yet. Should I look in ascii or ceres? Or aren't we at that
> stage yet?
Good question, but there are none right now AFAIK!
> Is ascii generally as reliable as
On Mon, 28 Sep 2015 15:00:46 +0200
Edward Bartolo wrote:
> Hi All,
>
> My next coding will be to add support for network interfaces other
> than wlan0 and eth0. Regarding this, I would like to have your ideas
> about how should I go not to minimally disrupt the already existing C
> code that is
On Mon, 28 Sep 2015 15:45:03 +0100
Rainer Weikusat wrote:
> ... and who wouldn't want his network interface to be named
> "enp0s29u1u2"? After all, anybody unterstands the meaning of eth0 ---
> how terribly boring!
I don't like it either, but even anti-systemd distros are going for
this Freedesk
Hi natacha,The first four sections look pretty standard.
But if you haven't done a fairly accurate assessment of how the community
actually getswork done, it's highly unlikely that what is written about
governance will reflect reality. Insteadit will confuse and frustrate
newcomers, who will be
Quote: "Some way to display the IP address when connected, either on-demand or
along with the word, Connected, or some other way."
---
Which ip address? If a pc is connected to a wifi the address is
something like 192.168.1.102. Are you talking about the ip addr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 09/28/2015 08:10 PM, Jonathan Wilkes wrote:
> Hi natacha,The first four sections look pretty standard.
Yes, it is standard and very minimal, by curiosity, which txt are you
talking about?
> But if you haven't done a fairly accurate assessment
- Original Message -
> From: "Rainer Weikusat"
> Laurent Bercot writes:
>> I'm talking normal use cases here, i.e. situations where the services
>> *will* succeed. In those situations, it is better to start everything
>> according to the dependency graph, because then you do *not* trigg
I'm talking about the LAN address. A lot of times, one of the first things
I do after booting into a new system is use sftp to move files.
Also, with wicd, I've gotten used to seeing the local address, and I feel
like it's a more reliable indicator that I'm online than just the word,
Connected. Bu
Hi Aitor.
I ran the following and got this error.
E: Release signed by unknown key (key id CBF8D6FD518E17E1)
Ozi
lb clean --purge
lb init
lb config -a amd64 \
--binary-images iso \
--distribution jessie \
--win32-loader false \
--checksums md5 \
--archive-areas "m
So, you are talking about the address displayed by "ip addr"? Please,
forgive me to ask again, but I have to be certain to avoid writing
code in vain.
On 28/09/2015, fsmithred wrote:
> I'm talking about the LAN address. A lot of times, one of the first things
> I do after booting into a new syste
On 28/09/2015 22:05, Rob Owens wrote:
Here is a real-world scenario that has caused me trouble over the years.
I have a system that connects wirelessly to my local network. The system
uses wicd to manage the network connections, and wicd starts at boot.
This system is supposed to mount several N
No awk necessary; the same system calls that /sbin/ip uses are
available for Netman. And strace even reveals their names and the
appropriate arguments.
Arnt
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo
Yes, the address displayed by "ip addr". I'm getting the 192.168.x.x
number with that command, and that's the one I need. Sorry I wasn't clear.
fsr
On 09/28/2015 04:26 PM, Edward Bartolo wrote:
> So, you are talking about the address displayed by "ip addr"? Please,
> forgive me to ask again, but
On Mon, Sep 28, 2015 at 09:39:08PM +0200, natacha wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
>
> On 09/28/2015 08:10 PM, Jonathan Wilkes wrote:
> > Hi natacha,The first four sections look pretty standard.
> Yes, it is standard and very minimal, by curiosity, which txt are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>
> Perhaps what we need is a document that describes how devuan does
> operate rather than one that says how it ought to operate. A
> descriptive, rathr than a prescriptive document.
Yes, this could be the way to the roadmap that was suggested by
You must change default mirrors:
lb config -a amd64 \
--binary-images iso \
--distribution jessie \
--win32-loader false \
--checksums md5 \
--archive-areas "main" \
--apt-recommends false \
--apt aptitude \
--apt-options --yes \
--build-with-chroot false \
27 matches
Mail list logo
