Simon Richter writes:
> their questionable choices in buying hardware that ships with non-free
> firmware
Is there hardware that ships with free firmware? Seriously.
Bjørn
The Wanderer writes:
> To be fair, while I *am* against the proposal, I'm also not a Debian
> Developer - just an interested observer of, and occasional participant
> in, discussions on Debian mailing lists (including this one).
+1
and to clarify my view on format=flowed:
This should not be ma
Wookey writes:
> Which entry in which release notes will warn that this time
> (presumably - was this an upgrade to unstable K.C. or to bookworm, or
> something else?) the (pretty old now) eth0 -> 'annoying, unmemorable,
> but ordered and unique', renaming will/might actually break your
> config?
Matthias Urlichs writes:
> On 05.03.25 17:16, Bjørn Mork wrote:
>> apt install apt-listchanges
>
> To be fair, apt-listchanges lists a whole lot of changes, esp. when
> you do a dist-upgrade.
>
> Noticing the one change among the umpteen more-or-less-major NEWS
> entrie
Michael Banck writes:
> On Wed, Mar 05, 2025 at 04:06:56PM +0100, Marc Haber wrote:
>> On Tue, 4 Mar 2025 20:39:43 -0500, "Helmut K. C. Tessarek"
>> wrote:
>> >Both network "outages" could have been prevented by adding a note at the
>> >end of the dist-upgrade output.
>> >
>> >e.g. something lik
Wookey writes:
but I think I need to know the equivalent to
au FileType mail setlocal formatoptions+=w
for emacs particularly, but also zile, jed and mcedit (all of
which get used from time to time). Anyone know?
Set `use-hard-newlines' for emacs, according to
https://debbugs.gnu.org/cg
Chris Hofstaedtler writes:
> No. I see and type my username hundreds times a day, people use it
> to address me in written and spoken conversations with it, etc.
This is confusing the subject even more.
Are you sure you are talking about usernames? Or is this email local
parts, chat nicknames
Marc Haber writes:
>> On the other hand, as long as this is admin-controlled, it doesn't
>> matter much. I could see that viewpoint, but I wonder how much latent
>> breakage would be introduced that will take years to fix in all tooling
>> and all packages.
>
> Yes. Fixing breakage makes software
Johannes Schauer Marin Rodrigues writes:
> But my 2 cents on the topic are: Lets please allow more than ascii in
> usernames. I find it very uncomfortable every time I have to tell my students
> that sorry, you somehow have to manage writing your name using American
> letters
> because that's al
Geert Stappers writes:
> Chesters fence
Chesterton's?
Bjørn
Lukas Märdian writes:
> On 23.09.24 12:27, Ansgar 🙀 wrote:
>
>> So on desktop installations including NetworkManager, netplan will
>> be
>> configured to do nothing? Why install netplan at all on desktop systems
>> then?
>
> Because it allows to add configuration in a way that is common with serve
Lukas Märdian writes:
> But in the end we don't want to bloat our base-installation with
> NetworkManager and systemd-networkd is not fit to cover the desktop/laptop
> usecase. So why not put some glue around it, to make it all feel coherent,
> without limiting anybody in their decision to choose
Matthias Urlichs writes:
> On 09.07.24 12:27, Bjørn Mork wrote:
>> Run user scripts on up/down events. That's a huge blank spot in
>> systemd-networkd. And by design, so it's really not fixable.
>
> Well, I've been apt-purging ifupdown for almost a decade by
Matthias Urlichs writes:
>> Agreed: either it's drop-in compatible or we may as well switch the
>> default to NM and/or systemd-networkd.
>
> Well, here's a heretical thought: why don't we do that anyway, at
> least for new installations?
>
> Somebody could even write a converter. Shouldn't be th
Luca Boccassi writes:
> If we want to start nitpicking, then let's be exact: 0.61% of popcon.
> Whether that qualifies as "plenty" we'll leave as an exercise for the
> readers.
I wonder if this sort of arrogant "don't care about minorities" attitude
will ever stop? Was sort of hoping that thing
"Theodore Ts'o" writes:
> I was curious about this, since I rely on snapshots.debian.org in
> order to create repeatable builds for a file system test appliance, so
> I started digging a bit. Looking at the debian-bugs pseudo-package
> "snapshot.debian.org":
>
> https://bugs.debian.org/cgi-bin/p
nick black writes:
> what
> does NetworkManager offer that makes it superior to
> systemd-networkd on the desktop
I don't know what systemd-networkd has to offer in this regard, but for
laptop usage I'm personally fond of the ModemManager integration along
with multihoming policies (eth0 preferr
Steve McIntyre writes:
> Raphaël Hertzog wrote:
>>
>>In the same spirit, I'd like to throw an idea... could we decide that
>>base-files is the first package to be configured as part of the bootstrap
>>protocol and change base-files maintainer's scripts into statically linked
>>executables so that
Marco d'Itri writes:
> as we all know every Debian maintainer can veto any systemic changes
> that they do not like.
I don't think qusr-merge would not have happened if this was true. And
I believe you know that very well.
I find your remark disrespectful. And I'm trying hard to assume good
f
Ansgar writes:
> On Fri, 2023-05-19 at 20:57 +0200, Bjørn Mork wrote:
>> Hmm. I find the netboot installer archives very useful for rescue
>> purposes. This sometimes involves PC hardware too old for amd64. I PXE
>> booted a 20+ year old laptop with no DVD/CD drive (
Steve McIntyre writes:
> I had been thinking about doing similar for installer images too, but
> with other work going on too I think it got too late in the cycle to
> make that change. My plan is therefore to ship i386 installer images
> for bookworm as normal (including bookworm point releases
Luca Boccassi writes:
> Nothing was ignored.
In the spirit of good faith I'll assume you meant "Nothing new was
ignored".
It's a fact that you are ignoring a few issues caused by usrmerge. This
is thoroughly documented in the BTS.
Arrogance is not on the bug list, but maybe it should be? It'
Philipp Kern writes:
> On 25.07.22 08:46, Bjørn Mork wrote:
>> Matt Barry writes:
>>>> - why has a change been made
>>>
>>> I think this is explained in excruciating detail. The short version
>>> (from NEWS):
>>>
>>> "mode 0
Matt Barry writes:
>> - why has a change been made
>
> I think this is explained in excruciating detail. The short version
> (from NEWS):
>
> "mode 0700 provides both the most secure, unsurprising default"
This is a self-referencing explanation. It provides no value. It's
only good if you alr
Andrey Rahmatullin writes:
> On Wed, Apr 06, 2022 at 04:02:23PM +0200, Bjørn Mork wrote:
>> > Sorry, blame the dpkg maintainer.
>>
>> Is that how we discuss technical issues around here?
> This is not a technical issue.
Ah, sorry. I mistook this for the "Discus
Marco d'Itri writes:
> Sorry, blame the dpkg maintainer.
Is that how we discuss technical issues around here?
Bjørn
"LeJacq, Jean Pierre" writes:
> There are standard best practices for forwarding support in SPF.
>
> http://www.open-spf.org/Best_Practices/Forwarding/
Well, if it only was that simple.
There is NO working SRS software/example config for sendmail in Debian
or anywhere else AFAICS.
The only thi
Bernhard Schmidt writes:
> - Since NTS leverages X.509, how does it work with a broken clock on
> boot that is ticking outside of the certificate validity period?
I don't know how it is intended to work, but it seems pretty obvious
that NTS certificate validation must ignore the validity perio
Scott Kitterman writes:
> I believe I can solve this problem by adding Recommends: resolvconf if that's
> the only way. I had hoped there would be some "modern" way to do it from
> within Debian's default package set.
Funny. That seems to have been the solution to this bug almost 20 years
ag
Michael Biebl writes:
> Am 17.11.2021 um 19:57 schrieb Sam Hartman:
>> The question is whether we ever get to a place where people can update
>> files in a package currently installed to /bin/foo and instead install
>> them to /usr/bin/foo.
>> We have a consensus that dpkg bugs make that a bad ide
Jeremy Stanley writes:
> While this does complicate it, a snooping party can still know the
> site they're connecting to via SNI happening unencrypted,
I believe this can be fixed with TLS 1.3?
> and packet sizes/pacing likely give away which pages or files are
> being retrieved based on their
Adam Borowski writes:
> On Wed, Feb 10, 2021 at 12:21:36PM +, Holger Levsen wrote:
>> On Wed, Feb 10, 2021 at 01:05:04PM +0100, Bjørn Mork wrote:
>> > I happen to disagree. To me this is yet another step away from being a
>> > proper Unix system - to something el
Marvin Renich writes:
> * Steinar H. Gunderson [210209 14:27]:
>> On Tue, Feb 09, 2021 at 08:53:10PM +0200, Adrian Bunk wrote:
>> > And there are now also many non-technical Linux users who have never
>> > used a shell.
>>
>> Well, why do we include netcat, telnet or hdparm? lsof? pciutils?
>> t
John Paul Adrian Glaubitz writes:
> If the packages in question are essential, then these packages should get a
> proper
> maintainer with a maintenance release first before the freeze kicks in.
How does that happen?
Bjørn
There is no one proposing that non-free should be mandatory.
The original topic was whether it should be possible to install Debian
at all, noting that there are situations where this now is so difficult
that it will be percevied as "impossible" by some users.
I believe it is an undisputed fact t
Steve McIntyre writes:
> However, in the latter case Debian has shipped non-free stuff. That is
> a big shift in our position. Don't get me wrong: I'm not saying this
> is an impossible place for us to go to. But before we do that we
> should have an open and honest debate about it.
I absolutely
Steve McIntyre writes:
> Marc Haber wrote:
>>
>>I was not aware of that feature. It is good to have that, but I would
>>be embarrassed to seriously suggest this way because we can't manage
>>to get WLAN working in the installer for political reasons.
>
> Are we seriously just going to describe ou
Marc Haber writes:
> My workaround is to plug in a network cable for installation. But
> alas, I have up to now been able to avoid hardware without built-in
> Ethernet. I guess that many USB Ethernet interfaces will work out of
> the box without non-free, right?
Yes, even integrated LTE/5G modem
Jonas Smedegaard writes:
> I would consider it highly unlikely that (Disney would claim and a court
> would agree with them, that) Pixar customers could confuse some Pixar
> products with a Debian release.
I believe Disney lawyers are world famous for their ability to construct
a legal problem
Zlatan Todorić writes:
> In that regard, if DDs find Nitrokey interesting, I have contact with
> their founder and we could negotiate discount(s) on their products and
> also pursue similar effect as with Peertube - we (potentially) get
> what some (all?) DDs need while we help them grow as indep
"Theodore Y. Ts'o" writes:
> I've always considered /bin/ed the most basic system administration
> tool, since it doesn't require a working terminal or termcap entry.
> It works even if you are using an ASR-33 teletype. :-)
>
> And at least for me, I find /bin/ed much more user friendly than vi,
Thomas Goirand writes:
> without a pager installed.
Is that really possible? AFAICS, /bin/more is part of util-linux which
is essential. So you will always have at least one pager installed.
But something might have messed up the alternatives symlinks. Falling
back to /bin/more is better han
Robert Edmonds writes:
> The entire DNS root zone is only 1 MB compressed and is updated about
> once a day. It would be even better for privacy if the whole root zone
> were distributed via HTTPS, as the initiator would not reveal to the
> server any information about what TLD is being looked up
Ondřej Surý writes:
> On the privacy topic...
>
> Slides: https://irtf.org/anrw/2019/slides-anrw19-final44.pdf
> Paper: https://dl.acm.org/authorize.cfm?key=N687437
And also section 8 of
https://tools.ietf.org/html/draft-reid-doh-operator-00
> And you can get to the video recording from the AN
Bernd Zeimetz writes:
> On 8/11/19 12:01 PM, Adam Borowski wrote:
>> restart|force-reload)
>> log_daemon_msg "Restarting $DESC"
>> do_stop
>> sleep 1
>> do_start
>> log_end_msg $?
>> ;;
>>
>> Yes, this particular case might fail on a pathologicall
Julian Gilbey writes:
> On Wed, Jul 10, 2019 at 12:31:51PM +0100, Julian Gilbey wrote:
>> Hooray, buster's released! Congrats to all!
>>
>> So I tried upgrading my machine to bullseye today, and
>> aptitude/apt-get update don't like this, giving me errors such as:
>>
>> E: Repository 'http://ft
Adam Borowski writes:
> => Install gtk3-nocsd by default in all desktop tasks but Gnome. It's not
> perfect but it helps.
That's nice. Thanks for the tip. I enjoy nice tools like eog and
evince, but have always been annoyed by the missing window title and
associated window manager cont
Daniel Lange writes:
> We have more people registered for DebConf ("the Debian Developers'
> conference") with @gmail.com than @debian.org addresses.
You can't fix @gmail.com. It is deliberately broken for commercial
reasons, and that won't stop with SPF and DKIM. Anti-spam is just the
current
Marco d'Itri writes:
> On Nov 26, Didier 'OdyX' Raboud wrote:
>
>> Sorry to be blunt about this, but have you reported these? Sniping at (any)
>
> No, they have not. There is a lot of handwaving in this thread but very
> few results of actual tests.
"Migration is not (easily) reversible" was r
Paul Wise writes:
> On Mon, Dec 4, 2017 at 6:43 AM, Bjørn Mork wrote:
>
>> But how would a user without any previous knowledge of modemmanager or
>> Linux networking be able to figure this out?
>
> It sounds like you are looking for isenkram to be integrated into the
tl;dr: Desktop tasks have unexpected (from the user point of view) side
effects due to dependencies. This can be considered harmful since the
installer task selection can easily can trick a user into installing a
"substandard" system.
Yesterday I did something I rarely do: I installed Debian from
Enrico Zini writes:
> On Tue, Sep 05, 2017 at 11:37:01AM +0200, Enrico Zini wrote:
>
>> I refactored the certificate generation code for sso.debian.org, and the
>> certificates it generates now still work in Firefox but not in Chrome.
>
> I found the reason: python-cryptography writes the certifi
Abou Al Montacir writes:
> On Fri, 2017-08-18 at 08:24 -0500, Matt Zagrabelny wrote:
> ...
>> > If someone hypothetically joins, are they allowed to rename the FTP team
>> >
>> > to something that doesn't include "FTP"?
>>
>> Archive Team. Or the A-Team for short. The only Debian team with a the
Guus Sliepen writes:
> Ok, it should be clear now that the new way of naming interfaces is not
> ideal, but the older ways weren't either. Let's have a look at what we
> want:
>
> - A simple name for systems with a single Ethernet and/or Wireless
> interface (the simple desktop/laptop scenario)
Samuel Thibault writes:
> Vincent Bernat, on lun. 10 juil. 2017 20:55:29 +0200, wrote:
>
>> Other major distributions are using this new scheme (notably Ubuntu
>> which has no reason to have users smarter than ours)
>
> The reasoning is the converse: non-techy users will just not be exposed
> to i
m...@linux.it (Marco d'Itri) writes:
> On Jul 10, Adam Borowski wrote:
>
>> Predictability is important, thus let's actually have _predictable_
>> interface names. The kernel default, eth0 and wlan0, is good enough for
>> most users, why not keep that? Even just ignoring the issue completely
> B
Adam Borowski writes:
> On Tue, Feb 28, 2017 at 10:15:23AM +0100, Daniel Pocock wrote:
>> > But ntpd is also known to have a large amount of code written
>> > without as much regard for security as one would hope. It seems
>> > like an unnecessary risk for most systems.
>>
>>
>> Thanks for tha
Andreas Tille writes:
>> Since this is still an open discussion in #846002, I would have
>> preferred if you would not try to force your own preference here before
>> the CTTE made its decision.
>
> While I'm not sure whether its a personal preference or whether some
> discussion I might have mis
Russell Stuart writes:
> On Thu, 2016-12-29 at 11:38 -0800, Russ Allbery wrote:
>> It certainly doesn't provide a man page that doesn't start with a BNF
>> syntax description. The iproute2 documentation is awful.
>>
>> Also, this is not at all easy to parse:
>>
>> # ip -o address
>> 1: loine
Russ Allbery writes:
> Christian Seiler writes:
>> On 12/29/2016 08:38 PM, Russ Allbery wrote:
>
>>> ip address also has one of the worst output UI decisions I've ever seen,
>>> namely this line:
>>>
>>> inet 192.168.0.195/24 brd 192.168.0.255 scope global dynamic wlan0
>>>
>>> specifically
Emilio Pozuelo Monfort writes:
> On 09/07/16 22:31, Franciscarlos Santos Soares wrote:
>> Hi Emilio!
>>
>> Thank you for contacting us. In fact, like independent application of any
>> DE,
>> but they were compatible with the traditional look of windows and based on
>> the
>> GTK library. So w
Bjørn Mork writes:
> "/usr/lib/sysctl.d/" is systemd specific. Dropping files there won't do
> anything unless you run the systemd-sysctl service.
Sorry, should have researched this better first. sysctl WILL use
"/usr/lib/sysctl.d/" if it exists. procps won&#
Tom H writes:
> systemd isn't the first package to allow/promote shipping distro
> settings in "/lib" or "/usr/lib" and overriding them via "/etc"; udev
> and polkit/policykit have behaved like this for a long time. There's
> also "/usr/lib/sysctl.d/" where a distro ship settings that can be
> ov
Nikolaus Rath writes:
>> How dare you write ... instead of the proper … :-P
>
> I'm curious, how do you type that in conviently? I hope it's not copying
> and pasting from a template file, and remembering (and/or finding out)
> the X11 Compose sequence seems cumbersome too.
I see that you have g
Josselin Mouette writes:
> Bjørn Mork wrote:
> > We support non-systemd-as-pid-1 configurations, but they still run
> > logind through systemd-shim.
>
> systemd-shim is not essential. You can still install jessie without
> sy
Josselin Mouette writes:
> We don’t support non-logind configurations.
You might not. AFAICS, Debian does.
> We support non-systemd-as-pid-1 configurations, but they still run
> logind through systemd-shim.
systemd-shim is not essential. You can still install jessie without
systemd, and hen
Dmitriy Fitisov writes:
> we have a small device of our own, which communicates through serial USB on
> Windows.
> Now we need it to work on Raspberry (yes, I know this is Debian, which is
> Raspberry based on).
> USB descriptors configured as a modem, so, when I connect it to Linux,
> cdc-acm
Marc Haber writes:
> Indeed. Do we really have to pull that from a video or presentation
> slides? Is this part of the official systemd docs anywhere?
I don't know of any collection of all security related directives, but
you can find an index of all unit file directives in
systemd.directives(7)
m...@linux.it (Marco d'Itri) writes:
> On Nov 17, Steve Langasek wrote:
>
>> > This is what many still (retorically) wonder about: we the systemd
>> > maintainers did not reject that change,
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;bug=746578
> Please try to be less selective in
Brian May writes:
> On 14 November 2014 04:20, Carlos Alberto Lopez Perez
> wrote:
>
>> The last one that I read is that udev is going to stop working on
>> non-systemd systems:
>>
>> http://lists.freedesktop.org/archives/systemd-devel/2014-May/019657.html
>>
>>
> I don't read anything in that po
Tollef Fog Heen writes:
> ]] Norbert Preining
>
>> > systemd needs cgroups, that's pretty well established. Arguably, it
>> > should die with a clearer message.
>>
>> No, NO NOO
>>
>> *IT*SHOULD*NOT*DIE*!!! It is in PID 1. Please digest that.
>
> Am I understanding you cor
John Paul Adrian Glaubitz writes:
> On 02/17/2014 01:37 PM, Norbert Preining wrote:
>> Why can you not simply say something like: "Well yes, there seem
>> to be some problems and we will try to fix them if we can get hold
>> of enough input. You DDs should be able to provide decent information
>>
"Iain R. Learmonth" writes:
> Things I'd like to see are:
>
> * A systemd primer (like what is a service file?)
> * Packaging documentation for systemd (some has been started [1])
> * How to hack together a service (this is something I did quite a lot
> for homebrew scripts on servers)
>
> The
Ansgar Burchardt writes:
> Bjørn Mork writes:
>
>> Care to provide a pointer to an example?
>
> RFC 5230, sections 4.2, 4.5, 4.6 and 8.
Thanks for the pointer. Are there any implementations of RFC 5230 in
Debian?
Both "apt-cache search 5230" and "apt-cache s
Ansgar Burchardt writes:
> Bjørn Mork writes:
>> Is there such a beast with feature parity? vacation has a few nice
>> defaults, like ignoring list mails and only sending one message per week
>> to each receiver. Having every end user implement similar behaviour in
>
m...@linux.it (Marco d'Itri) writes:
> On Jan 12, Stefano Zacchiroli wrote:
>
>> It still seems to have a fair number of loyal users though. I see your
> popcon says 1867 have it installed, but only 222 "voted".
>
>> If we do have such a
>> replacement (I just don't know) please mention it in the
Uoti Urpala writes:
> Russ Allbery wrote:
>>Kay Sievers writes:
>> > Hmm, why would upgrades break?
>>
>> > The old file would still be there, rename the devices (if you keep the
>> > patch to swap names, which upstream does not support any more), and take
>> > precedence over tht new names; the
Michael Biebl writes:
> The persistent network interface naming rules are already skipped if
> udev is run within a virtual machine.
Which made me look closer at
/lib/udev/rules.d/75-persistent-net-generator.rules
I find it a bit strange that it has lots of logic involving different
OUIs, but
Michael Stapelberg writes:
> since some people might not read planet debian, here is a link to my
> first blog post in a series of posts dealing with the results of the
> Debian systemd survey:
>
> http://people.debian.org/~stapelberg/2013/06/09/systemd-bloat.html
I was hoping you would cover my
Jean-Christophe Dubacq writes:
> And in my experience, email tends to be much more fragile than dbus.
The warm fuzzy feeling you get when you don't know there is a
problem...
> How many times have I suddenly looked
> at the queue of a computer that has been mis-configured and that
> accumulate
Marc Haber writes:
> On Thu, 30 May 2013 06:46:46 -0400, Scott Kitterman
> wrote:
>>Even if they are using a system
>>that allows them to go back and review their notification history when they
>>return to their system,
>
> It just occurred to me that you are describing a mail client.
Let's ad
Ben Hutchings writes:
> On Wed, May 29, 2013 at 09:06:59PM +0200, Adam Borowski wrote:
>> On Wed, May 29, 2013 at 05:11:35PM +0200, Josselin Mouette wrote:
>> > Le mercredi 29 mai 2013 à 16:31 +0200, Javier Fernandez-Sanguino a
>> > écrit :
>> > > Take for example, smartmoontools [1]. Currently,
Russ Allbery writes:
> Bjørn Mork writes:
>
>> The local MTA serves as a common configuration for the external SMTP
>> server, with a well known interface supported by every single package
>> which wants to send mail.
>
> And which requires storing passwords or ot
Josselin Mouette writes:
> Le mardi 28 mai 2013 à 13:07 +0200, Bjørn Mork a écrit :
>> The local MTA serves as a common configuration for the external SMTP
>> server, with a well known interface supported by every single package
>> which wants to send mail.
>
> Whi
Josselin Mouette writes:
> Le mardi 28 mai 2013 à 10:34 +0100, Jonathan Dowland a écrit :
>> There is an impedence mismatch between packages which consider an MTA and the
>> sendmail interface to be standard and those desktop components that make no
>> such assumption. If we are going to keep ens
Russ Allbery writes:
> Bjørn Mork writes:
>
>> IANAL, but I believe you are wrong there. You give them much wider
>> rights than this by assigning the copyright to the FSF. The copyright
>> owner is free to relicense the work in any way they want.
>
> Have yo
Ian Jackson writes:
> Barry Warsaw writes ("Re: Contributor agreements and copyright assignment
> (was Re: Really, about udev, not init sytsems)"):
>> FTR: http://www.canonical.com/contributors
>
> That allows Canonical to make proprietary forks of the code (eg, to
> engage in the dual licensing
Tollef Fog Heen writes:
> ]] Bjørn Mork
>
>> "The default 'configure' install locations have changed. Packages for
>>systems with the historic / vs. /usr split need to be adapted,
>>otherwise udev will be installed in /usr and not work
>>
Cyril Brulebois writes:
> Thomas Goirand (28/11/2012):
>> That's not truth anymore, since AFAIK rules of udev moved to /usr.
>
> May I suggest some fact checking? Try “dpkg -L udev” for a start.
Yes, the Debian package is OK and I assume it will continue to be. But
I believe Thomas was referrin
Thomas Goirand writes:
> The solution to this is very simple. Have the
> mailing list manager to add a Reply-To: header
> on each messages.
>
> I've done this on few of the lists I manage, and since
> then, nobody sends double-messages.
>
> But, probably, mailman is too stupid to have such
> kind
Serge writes:
> 2012/8/30 Wouter Verhelst wrote:
>
>>> How do you suppose it's possible to undo arbitrary network
>>> configuration done by arbitrary set of tools when there's no central
>>> place to hold such information (and can't possibly be)?
>>
>> Actually, the kernel holds that information.
Stephan Seitz writes:
> On Mon, Aug 20, 2012 at 01:08:53PM +0200, Bjørn Mork wrote:
>>Never mind wireless lan where you've got a well defined kernel API. Try
>>to configure a modern 3G/LTE modem using ifupdown, and you will see the
>
> Is this something different from a
Christoph Anton Mitterer writes:
> On Sun, 2012-08-19 at 19:41 +0200, Marco d'Itri wrote:
>> NM, as a design goal, is not supposed to be able to manage every
>> possible configuration.
> Well but then it shouldn't be kind of a default package.
No it shouldn't. And it isn't either. gnome-core i
Jean-Christophe Dubacq writes:
> On 11/07/2012 11:12, Andrei POPESCU wrote:
>> On Mi, 11 iul 12, 10:55:16, Jonas Smedegaard wrote:
>>>
>>> The feature of _allowing a subset of packages to be removed that was
>>> _ensured_ to be installed: Impossible without defeating the feature of
>>> _ensuring
Serge writes:
> Since tmpfs+swap is mostly slower than regular filesystem
And the world is flat.
Bjørn
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/874nqfn0af..
Aneurin Price writes:
> In anything resembling a 'normal' system (ie. the kind where one might
> be using the defaults) I would say that the tmpfs correlation is so
> strong as to be very nearly 1:1, and this seems like the crux of the
> matter; that is after all the reason that these application
Aneurin Price writes:
> (Note that we are talking about applications which fail gracefully
> when confronted with ENOSPC,
Are we? What's the problem then?
> but which are likely to do so more often when the size of /tmp is
> restricted.)
Yes, but the tmpfs correlation is weak. There is absol
Serge writes:
> 2012/6/10 Adam Borowski wrote:
>
>>> Some people asked for a thread summary. So here it is.
>> Seriously, can't you even read what's written to you?
>
> Yes, I know it was a biased summary.
I think you might start to piss off a few people now...
Look at what you are quoting above
Petter Reinholdtsen writes:
> [Bjørn Mork]
>> I'd like to add another one:
>>
>> - a tmpfs is always easy to grow without requiring any special
>> preparations. Just add more swap. The swap could be on different
>> disks, and could even be files hosted
Petter Reinholdtsen writes:
> I've happily been using tmpfs on /tmp/ for probably ten years now, and
> can list some more benefits:
>
> - It allow diskless setups like LTSP to work the same way the default
>installation in Debian work. They use read-only NFS-mounted file
>systems and a
1 - 100 of 195 matches
Mail list logo
