On 23.09.24 13:33, Richard Lewis wrote:
Lukas Märdian writes:
On 23.09.24 12:27, Ansgar 🙀 wrote:
On Mon, 2024-09-23 at 12:22 +0200, Lukas Märdian wrote:
On 22.09.24 15:58, Ansgar 🙀 wrote:
On Fri, 2024-09-20 at 13:12 +0200, Lukas Märdian wrote:
The benefit that Netplan would provide in
On 23.09.24 12:27, Ansgar 🙀 wrote:
On Mon, 2024-09-23 at 12:22 +0200, Lukas Märdian wrote:
On 22.09.24 15:58, Ansgar 🙀 wrote:
On Fri, 2024-09-20 at 13:12 +0200, Lukas Märdian wrote:
I've repeated the reasons why I think a hybrid stack using Netplan is a
feasible solution many tim
On 22.09.24 12:22, Chris Hofstaedtler wrote:
* Lukas Märdian [240920 13:13]:
I've repeated the reasons why I think a hybrid stack using Netplan is a
feasible solution many times in previous threads, therefore I'd like to refer
to a list of frequently asked questions, instead of spre
udev
rules and configuring the [device-*].managed={true,false} NetworkManager
settings accordingly.
-- Lukas
Hi!
On 22.09.24 15:58, Ansgar 🙀 wrote:
On Fri, 2024-09-20 at 13:12 +0200, Lukas Märdian wrote:
I've repeated the reasons why I think a hybrid stack using Netplan is a
feasible solution many times in previous threads, therefore I'd like to refer
to a list of frequently asked question
On 23.09.24 11:04, Marco d'Itri wrote:
On Sep 23, Holger Levsen wrote:
ifupdown2 is like ifupdown, just rewritten in python.
Yes, that's the problem: there was a consensus that it is not an
appropriate dependency for the base system.
ifupdown2 will still be around for anybody who wants to ins
nd systemd-networkd (as part of the systemd package). This
leaves us with some network configuration fragmentation, but still feels like a
reasonable step into the right direction. Dropping network related packages
from the base installation is not part of this proposal. Let's keep this for
anoth
On 04.09.24 21:41, Daniel Baumann wrote:
sorry, one more..
On 9/4/24 18:00, Lukas Märdian wrote:
But we ought to look at the bigger picture!
From that point of view, it doesn't make sense to even consider netplan.
No distribution other than ubuntu is using it.
If Debian uses ne
On 05.09.24 11:36, Daniel Baumann wrote:
On 9/5/24 10:43, Marc Haber wrote:
I don't see a problem with keeping ifupdown{2,-ng,} if none of those
packages is part of the default install and we remove it from the
beginner- and intermediate-level docs.
right, me neither; but Lukas' ar
iproute2
* Netplan
* NetworkManager
* systemd-networkd
Which one to choose? Well it all depends on the underlying stack, which
the average user might not necessarily know. So it's very confusing.
-- Lukas
[debconf21]
https://debconf21.debconf.org/talks/52-contemporary-networking-configuration-with-ifupdown-ng/
On 04.09.24 13:28, Daniel Baumann wrote:
On 9/3/24 18:24, Lukas Märdian wrote:
The nice thing about Netplan is that it [...] functions as a
layer on top.
I don't understand what actual problem netplan is trying to solve.
On servers I want systemd-networkd directly anyway (for lacp, vla
ion.
In our documentation we could reference a single Netplan configuration,
that would get applied to both of the underlying stacks. As stated
previously, advanced users can easily configure the underlying stack
natively and Netplan will get out of their way.
Cheers,
Lukas
already do. In such cases Netplan can easily
be ignored and the underlying NetworkManager or systemd-netword stacks
can be configured natively, as you do today. Netplan will by default get
out of your way if you don't configure it specifically.
Cheers,
Lukas
Hi Daniel,
On 20.08.24 16:25, Daniel Gröber wrote:
Hi Lukas,
CCing d-devel,
This email was intended to first gauge opinions from networking maintainers,
before pushing it out to debian-devel@l.d.o.. All the points still hold and
are fine to be public. But let me at least add the preamble and
e NetworkManager configuration,
for example. But looking at the Netplan backends (NM, networkd, OVS), non of
them is built for non-linux architectures. So dependencies would need to be
worked out first.
-- Lukas
[systemd-generator]
https://www.freedesktop.org/software/systemd/man/latest/systemd.generator.html
On 16.07.24 11:24, Stephan Seitz wrote:
Am Di, Jul 16, 2024 at 10:54:47 +0200 schrieb Lukas Märdian:
* Netplan PLUS NetworkManager(desktop/laptop)
All my desktops have only LAN and are working very well with ifupdown since the
beginning.
My Laptops are mostly in a LAN either. So NM is onlay
On 16.07.24 11:06, tho...@goirand.fr wrote:
On Jul 16, 2024 4:55 PM, Lukas Märdian wrote:
> Netplan is integrated with [cloud-init] "v2" network configuration and the
"cloud-config"
> is adopted by many major public cloud providers (AWS, GCE, Azure, ...) as a
d
On 16.07.24 11:24, Jose Luis Tallon wrote:
On 16/7/24 10:54, Lukas Märdian wrote:
[snip]
But it's not just this.
Netplan's beauty starts to shine when we're talking about the full picture:
* Netplan PLUS sd-networkd (server/cloud/container)
* Netplan PLUS NetworkManager
On 16.07.24 08:00, Marc Haber wrote:
On Mon, 15 Jul 2024 15:35:32 +0200, Lukas Märdian
wrote:
I don't want people to think too much in terms of "sd-networkd VS Netplan",
but rather in terms of "sd-networkd PLUS Netplan". Contributors to Netplan
naturally build up know
On 15.07.24 16:06, Marvin Renich wrote:
* Lukas Märdian [240715 09:36]:
I don't want people to think too much in terms of "sd-networkd VS Netplan",
but rather in terms of "sd-networkd PLUS Netplan".
I'm a little confused. Much earlier in this thread it was st
overhead of ~5M, in cases where GLib is not
already installed and even less on systems with NetworkManager, as we'd
share some dependencies. 5M of additional storage shouldn't be a huge issue
in today's world, IMHO. For the benefit of gaining a common way do to
networking on Debian.
-- Lukas
n all Debian
systems
and is automatically translated to the corresponding backend for
server/desktop/cloud/embedded usecases.
All while giving sysadmins the flexibilty to fully utilize the underlying
network
daemon directly, if they feel like writing native configuration for it (or don't
like Netplan).
Cheers,
Lukas
On 13.07.24 17:40, Luca Boccassi wrote:
On Thu, 11 Jul 2024 at 12:12, Lukas Märdian wrote:
On 11.07.24 11:13, Marco d'Itri wrote:
On Jul 11, Philip Hands wrote:
I've only seen netplan mentioned in passing in this thread so far.
Because I believe that Netplan is the answer to
ody is free to write configuration for the
underlying backend directly.
Netplan will not interfere with that and go out of the way. Just don't write
Netplan configuration
for a specific interface (or all of them) that you want to handle differently.
-- Lukas
de for a
transitional period (Trixie at least), to keep backwards compatibility for
existing systems and give people some time in transitioning to new networking
tools.
Cheers,
Lukas
PS: If you happen to be at Debconf in Korea in a few weeks, please join my
[networking BoF].
[d-i/netcfg !9
tion to that, I'd propose to keep ifupdown in maintenance mode for a
transitional period (Trixie at least), to keep backwards compatibility for
existing systems and give people some time in transitioning to new networking
tools.
Cheers,
Lukas
PS: If you happen to be at Debconf in Korea i
On Fri, Jul 14, 2023 at 09:33:12AM -0400, Jeremy Bícha wrote:
> On Wed, Jul 12, 2023 at 8:32 AM Lukas Märdian wrote:
> > (We're also working on a bidirectional Netplan-NetworkManager integration,
> > that allows NM to feed back it's configuration into Netplan YAML forma
connection profiles into /run/NetworkManager/, while NM is
still free to choose which connection profile to use, or add additional
profiles in /etc/NetworkManager/ as usual.
(We're also working on a bidirectional Netplan-NetworkManager integration,
that allows NM to feed back it's configuration into Netplan YAML format. It is
a small patch for NetworkManager and is purely optional.)
-- Lukas
signature.asc
Description: PGP signature
On Tue, Jul 11, 2023 at 03:06:57PM -0600, Sam Hartman wrote:
> >>>>> "Lukas" == Lukas Märdian writes:
>
>
> Lukas> Therefore, I'd love to see Netplan to be used in combination
> Lukas> with this! It's a clean, declarative conf
ould also allow for d-i to install a single,
common default network configuration, independently of the underlying daemon.
The Netplan + systemd-networkd stack is already being used in Bookworm
cloud-images [1]. So going with that in d-i as well, would have the additonal
benefit of common network config
On Thu, Jun 22, 2023 at 01:39:02PM +0800, Paul Wise wrote:
> On Tue, 2023-06-20 at 11:19 +0200, Lukas Maerdian wrote:
>
> > Netplan allows to configure both of those tools and is already being
> > used across Ubuntu and in Debian cloud-images for this purpose. All
>
27;s usecases. We'd also get nice CLI tools to control this
stack for free, such as "networkctl", "nmcli" or "netplan status".
Cheers,
Lukas
[1] https://tracker.debian.org/pkg/netplan.io
[2]
https://hamburg-2023.mini.debconf.org/talks/5-network-configuration-on-debian-systems/
and of
course we're also open for contributions!
Cheers,
Lukas
[1] https://nm.debian.org/process/1180/
[2] https://tracker.debian.org/pkg/netplan.io
scussing some changes
that we landed in the recent netplan releases: Most of the integration
tests can nowadays be run inside containers and can thus be used as
autopkgtests inside the Debian infrastructure. I think it would be a
good first step for me to enable those tests.
Cheers,
Lukas
ler configuration files (in comparison to (networkd/NM), that can
be split up into multiple files if wanted or needed, can be overwritten
by the user or admin (via /{lib,etc,run}/netplan overrides) and other
packages can ship drop-in snippets that provide a certain piece of
network configuratio
switch between
sysvinit and systemd-udevd and get the same behavior without having to
change their hwclock configuration or experiencing unpleasant surprises.
On Tue, Feb 28, 2017 at 10:20:24PM +0100, Andreas Henriksson wrote:
> On Mon, Feb 27, 2017 at 02:34:34PM +0100, Lukas Wunner wrote:
>
veniently in git but also produce 3.0 (quilt) packages
where even if one doesn't use git (or the git repo vanishes) is still
possible to see what modifications has been done to the source
compared to the upstream release.
Regards,
Lukas
--
To UNSUBSCRIBE, email to debian-devel-requ...@li
initramfs-tools, dropbear, cryptsetup at least) and has
potential for great failure.
Regards,
Lukas
On Tue, Jan 14, 2014 at 2:24 PM, Gerrit Pape wrote:
> Hi, in 2008 initramfs support was contributed to the dropbear package.
> Unfortunately the contributor seems to be no longer active and quite
&
rc.d start" a NOP if run inside a chroot.
Regards,
Lukas
On Sun, Oct 6, 2013 at 3:54 PM, wrote:
> Dear fellows,
>
> This is a simple Makefile which generates ova[1] of customized debian,
> inpired by an ova build script of sagemath[2], and a guide from
> archlinux[5].
>
&g
Aquire Precsriptions and Medicaitons right now
www.addictartistry.bifreca.com
on armchairadulate
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Matthias Urlichs <[EMAIL PROTECTED]> writes:
> Hi, Lukas Geyer wrote:
>
> > As an
> > aside, I don't quite understand why Fortran is still so popular in the
> > numerical mathematics community... :)
>
> There still are a lot of Fortran libraries which
(maybe you?) sends Intel some patches to make
their compiler work on Debian systems, that can not be bad. As an
aside, I don't quite understand why Fortran is still so popular in the
numerical mathematics community... :)
Lukas
#x27;t) or is this all
just about a gut feeling that you don't like him? If you think that
James is not able to fulfill all his duties, it is up to us (or the
DPL) to propose others to help or replace him. However, I do not see
much basis in fact for your allegations of rudeness, so please either
substantiate it or stop spreading such accusations.
Lukas
ompatibility in fvwm). As you can see
> below, I have included as many of the features as I could.
>
can I simply update to the new packages by inserting the
deb-statements into my /etc/apt/sources.list ?
I'm running unstable.
Thanks for any help.
wbr,
Lukas
--
Lukas Ruf
time? Nice.
OK, the rest of your message is more ignorance and arrogance, I will
stop it here. Do you actually know what the project expects of its
package maintainers? You seem to have a rather shallow understanding
of all the issues involved with kernel packaging, and I strongly
object to this package being uploaded to sid. Experimental would be
fine with me for people to test it.
Lukas
ether Adamantix, otherwise I pity the poor souls who use it and
believe it is "Trusted"...
Lukas
P.S.: Why does everyone attack Russell these days? Seems to me like
the field of Linux security is populated by lots of trolls.
nethack
is only a game and num_pad is really something that can be changed in
a second by the user. It would be slightly more relevant to discuss
what compile-time options to turn on, but then I also leave that to
the discretion of the maintainer(s).
Lukas
already have a package
ready, I don't mind you hijacking it to get it in sarge. And for a
development version which is not actively maintained, well... kill
it. :)
Best regards,
Lukas
"Steve C. Lamb" <[EMAIL PROTECTED]> writes:
> On Sat, Oct 18, 2003 at 08:09:00AM -0400, Lukas Geyer wrote:
> > Right, that reminds me of a default option which I always change,
> > namely pickup_types. I don't know what the default is at the moment
> >
, but IMHO things to be auto-pickuped
are "$!?+/=, and some characters might even leave out the spellbooks,
though one can at least sell them for decent money. Making nethack
options debconf question seems a bit silly to me, but I don't see why
we should stick to upstream defaults when they are wrong...
Lukas
up somehow." (In the American
edition "peckers" was changed to "spirits".) Be aware that the current
administration and Fox News might view this as an act of war...
Lukas
n with some friends, I don't see how this
would violate anything.
Lukas
P.S.: I still would prefer lwn.net to be free. In fact, I would prefer
to get my NY Times without paying for it, but unfortunately my wishes
do not always come true...
like
#198449 a little more inconvenient.
Probably there are other possibilities which I might have missed. The
first question is, would other people find this useful?
Lukas
7589. I just filed for its removal.
Lukas
P.S.: Thanks for the commented junkya^Wlist, Marcelo. I found it very
useful.
--
Give a man an answer, and he's satisfied today. Teach him to program,
and he will be frustrated for the rest of his life.
us new debian users. So far I have discovered
> mawk, and mailx. So, out with it, what are the rest?
Why don't you look for them yourself? Some people have more important
things to do with their time, even if it is hard to imagine what would
be more important than this...
Lukas
ng
non-free packages is a hassle, it might be easier to write a free
replacement in the time saved by messing around with non-free packages
and getting special Debian redistribution permissions. (Remember,
there is no build daemon for non-free.)
Lukas
es. If this was a separate bug, I
would consider it "minor", and thus not worth Cc-ing to -devel.
Lukas
hat others have the same
impression. (Matt Zimmerman did not even mention the point about "anal
retentives"...)
So, please calm down and discuss technical merits of debconf usage,
not personal motivations of some imagined developer cabal,
Lukas
non-free. For those who have not followed the discussion and such,
the issue seems to be the fix of #152547. If we are not allowed to
remove a screenful of advertising from the output of a program, then
this unduly restricts the freedom to distribute modified versions.
Cheers,
Lukas
P.S.: Cc'ed
tely
different. Funny that you criticized Andrew Suffield for insulting
other people on the list. Should I start publicly pounding on you
because you have an open bug of severity "important" on which you have
not commented since April? I think that would be bad style, like
mentioning that the
).
Best regards,
Lukas
P.S.: Please Cc me on replies, I am not subscribed to this list.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
hough. If I remember correctly,
the problem is that flock/fcntl locking on NFS mounted filesystems can cause
complete lockup ( :-) ) of the process.
cheers,
Lukas
---
I just noticed that adduser 3.1 doesn't work together with NIS, a proper bug
report is submitted. I just mention this here again since it might be relevant
for the release of Debian 1.3.
Cheers,
terest in keeping the package alive.
Lukas
---
Dr. Lukas Nellen | Email: [EMAIL PROTECTED]
Depto. de Fisica Teorica, IFUNAM |
Apdo. Postal 20-364 | Tel.: +52
s -> ../../../X11R6/lib/X11/nls
Cheers,
Lukas
---
Dr. Lukas Nellen | Email: [EMAIL PROTECTED]
Depto. de Fisica Teorica, IFUNAM |
Apdo. Postal 20-364
nt it to. It keeps a
> cache of incoming mail message ID's and can be cofigured to do
The procmail package also allowes you to set up a message-id cache. Have a look
at formail(1) and at the `vacation' example in procmailex(5).
present in /etc/conf.modules
Feel free to use the patch if you like my solution and if my patch looks ok to
you.
Cheers,
Lukas
--- modules.origFri Aug 9 16:55:11 1996
+++ modules Fri Aug 9 16:55:33 1996
@@ -34,
Cheers,
Lukas
---
Dr. Lukas Nellen | Email: [EMAIL PROTECTED]
Depto. de Fisica Teorica, IFUNAM |
Apdo. Postal 20-364 | Tel.: +52 5 622 501
68 matches
Mail list logo
