On Vi, 17 mai 19, 17:05:40, Francisco M Neto wrote:
> As the first in a series of (maybe 2) posts about Debian's release cycle,
> I'vecreated the following post.
>
> I would love to receive any feedback on it.
>
> http://fmneto.com.br/en/en/archives/2019/tracking-busters-release/
Disclaimer: b
Hi,
deloptes wrote:
> What does determine the DVD burning speed? Is it the DVD or the burner or
> both?
The drive decides according to its assessment of the medium and the
speed wish issued by the burn program.
The drive announces a list of possible speeds, depending on the medium.
E.g.:
$ xo
Quoting Rick Thomas (2019-06-25 03:32:41)
> > On Jun 23, 2019, at 2:24 AM, to...@tuxteam.de wrote:
> >
> > On Sat, Jun 22, 2019 at 05:45:39PM -0700, Rick Thomas wrote:
> >>
> >> Purely out of curiosity, I'd like to see what's involved in
> >> switching a Debian buster system from systemd to sysv
Jude DaShiell wrote:
> The speed in the burning command and the fs parameter. Needs the right
> amount of memory in it and that's a factor of machine resource
> availability.
but I do not have option 1x - it gives me minimum 3x. Why is this so
On 2019-06-25 at 09:28, Michael Stone wrote:
> On Tue, Jun 25, 2019 at 08:46:28AM -0400, The Wanderer wrote:
>
>> On 2019-06-25 at 08:11, Michael Stone wrote:
>>> It isn't because: 1) the new names are predictable but not
>>> constant, so you can't configure a single default across all
>>> syste
On Tue, 25 Jun 2019 19:35:03 -0400
The Wanderer wrote:
> On 2019-06-25 at 09:06, Celejar wrote:
...
> > certainly greater than mine - but tab completion works in this context,
> > so you can simply do 'ip addr show dev e', etc.
>
> Not in my environment, it doesn't. That's presumably because I
On 2019-06-25 at 09:06, Celejar wrote:
> On Tue, 25 Jun 2019 13:12:58 +0200
> wrote:
>
> ...
>
>> [1] Both are valid decisions, it's your machine, after all. I, for
>>example, went the "old ways", because I do much manual config
>>at the shell, and it's definitely more ergonomical to ty
On Tue, Jun 25, 2019 at 9:00 AM Dan Purgert wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> The "problem" with them was that they apparently weren't consistent
> across boots if you had multiples of the same "type" -- although I can't
> remember that ever happenening, even on crazy
The speed in the burning command and the fs parameter. Needs the right
amount of memory in it and that's a factor of machine resource
availability.
On Wed, 26 Jun 2019, deloptes wrote:
> Date: Tue, 25 Jun 2019 18:02:29
> From: deloptes
> To: debian-user@lists.debian.org
> Subject: DVD Burning s
What does determine the DVD burning speed? Is it the DVD or the burner or
both?
How can I write DL dvd at 1x speed?
thanks and regards
On Tue, 25 Jun 2019 13:12:58 +0200
wrote:
...
> [1] Both are valid decisions, it's your machine, after all. I, for
>example, went the "old ways", because I do much manual config
>at the shell, and it's definitely more ergonomical to type
>
> ip addr show dev eth0
>
>than
>
>
On Ma, 25 iun 19, 14:56:28, Steven Post wrote:
>
> Update, I noticed that it shows the same issue when entering a wi-fi
> password, or root password.
Such dialog boxes are kind of special, e.g. to prevent other programs
from stealing the focus.
This seems to suggest a bug/feature in Gnome/GTK l
On Tue, Jun 25, 2019 at 04:22:54PM -0400, Stefan Monnier wrote:
The one thing I can't understand is why we still don't have "network
interface aliases" (equivalent to symlinks), so that systemd can name my
interface enp2s0 *and* eth0 instead of having to choose between those
two, just like it has
>>The one thing I can't understand is why we still don't have "network
>>interface aliases" (equivalent to symlinks), so that systemd can name my
>>interface enp2s0 *and* eth0 instead of having to choose between those
>>two, just like it has no problem naming my SSD /dev/sda and
>>/dev/disk/by-id/a
On Tue, Jun 25, 2019 at 04:04:55PM -0400, Brian Cary wrote:
>Greetings!
>As the title says, I can't seem to install anything from backports.
>Example, lets say I need to upgrade Gimp from 2.8 (in stable) to 2.10 (in
>Testing).If I go to [1]https://backports.debian.org/Packages/ I ca
On Tue, Jun 25, 2019 at 04:04:55PM -0400, Brian Cary wrote:
> I run this:
> *apt -t stretch-backports install gimp*
> And my newly installed Debian 9.9 replies:
>
> *gimp is already the newest version (2.8.18-1+deb9u1).0 upgraded, 0 newly
> installed, 0 to remove and 153 not upgraded.*
> Which is
Greetings!
As the title says, I can't seem to install *any*thing from backports.
*Example*, lets say I need to upgrade *Gimp* from 2.8 (in stable) to 2.10
(in Testing).If I go to https://backports.debian.org/Packages/ I can
*verify* that 2.10 is indeed in testing.
I run this:
*apt -t stretch-back
Le 24/06/2019 à 01:40, Ross Boylan a écrit :
# update-initramfs -u -k 4.19.0-5-amd64
update-initramfs: Generating /boot/initrd.img-4.19.0-5-amd64
/usr/share/initramfs-tools/hooks/cryptroot: 64:
/usr/share/initramfs-tools/hooks/cryptroot: cannot open /proc/mounts:
No such file
cryptsetup: WARNING
On Tue, Jun 25, 2019 at 08:23:31PM +0200, Martin S. Weber wrote:
This is not true. I use USB OTGs of embedded devices behind an USB hub,
and the interface names vary between various power cycles of the embedded
devices.
Current default for USB ethernet (AFAIK) is to use enx
where t
On Tue, Jun 25, 2019 at 01:05:56PM -0500, David Wright wrote:
> However, if you upgraded to stretch, I think you'd have to show that
> you'd allowed the system to preserve the old names, rather than trying
> to circumvent Debian's methods for doing so. Isn't that what you've done?
Upgrades to stre
Hi!
To derail this discussion a bit more ...
On 2019-06-25 08:46:28, The Wanderer wrote:
> On 2019-06-25 at 08:11, Michael Stone wrote:
> > (...)
> > 1) the new names are predictable but not constant, so you can't
> > configure a single default across all systems
> (...)
> On a single computer wi
On Tue 25 Jun 2019 at 11:09:12 (+0200), Hans wrote:
> Hi Tomas,
>
> > The moniker for that is "predictable interface names". And you
> > seem to assume that there hasn't been a discussion.
> >
> > This being Debian, there sure has been one, you just didn't
> > notice :-)
> >
> Might be, but this
On Tue 25 Jun 2019 at 12:01:31 (-0400), Stefan Monnier wrote:
> > For good description of the problem (unpredictable names) and the logic
> > behind the chosen solution:
> >> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
>
> The one thing I can't understand is
On Tue, Jun 25, 2019 at 12:01:31PM -0400, Stefan Monnier wrote:
For good description of the problem (unpredictable names) and the logic
behind the chosen solution:
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
The one thing I can't understand is why we sti
> For good description of the problem (unpredictable names) and the logic
> behind the chosen solution:
>> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
The one thing I can't understand is why we still don't have "network
interface aliases" (equivalent to syml
* On 2019 25 Jun 09:00 -0500, Dan Purgert wrote:
> The "problem" with them was that they apparently weren't consistent
> across boots if you had multiples of the same "type" -- although I can't
> remember that ever happenening, even on crazy frankenboxes that had 3
> and 4 PCI NICs in them (barring
Thanks for explaining the limitation of the udev assignment mechanism
and why the present system was adopted.
- Nate
--
"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."
Web: https://www.n0nb.us GPG key: D55A8819 GitHub: N0NB
signa
On Tue, Jun 25, 2019 at 01:59:27PM -, Dan Purgert wrote:
Michael Stone wrote:
weren't constant, but people didn't seem to care as much about the
nuances because "that's the way it's always been". (Sometimes it was an
eth, sometimes it was a wlan, etc.) Why were those differences ok but
these
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Michael Stone wrote:
> On Tue, Jun 25, 2019 at 08:46:28AM -0400, The Wanderer wrote:
>>On 2019-06-25 at 08:11, Michael Stone wrote:
>>
>>> On Tue, Jun 25, 2019 at 11:09:12AM +0200, Hans wrote:
>>>
Might be, but this does not explain, why there a
On Tue, Jun 25, 2019 at 09:30:59AM -0400, Michael Stone wrote:
> On Tue, Jun 25, 2019 at 09:05:30AM -0400, Greg Wooledge wrote:
> > Debian's defaults are a bit baffling sometimes. They assumed a mobile
> > device when they decided to put "allow-hotplug" on your wired ethernet
> > interfaces, which
Rick Thomas wrote:
>
> In any case, the solution I came up with is
>
> apt-get --purge install -y sysvinit-core dbus- glib-networking-
> libgtk-3-0-
> apt-get --purge autoremove
>
> Note the trailing minus-signs on dbus- glib-networking- libgtk-3-0- These
> packages need to be delete
On Tue, Jun 25, 2019 at 09:05:30AM -0400, Greg Wooledge wrote:
Debian's defaults are a bit baffling sometimes. They assumed a mobile
device when they decided to put "allow-hotplug" on your wired ethernet
interfaces, which breaks everything under the sun on traditional
servers or workstations in
On Tue, Jun 25, 2019 at 08:46:28AM -0400, The Wanderer wrote:
On 2019-06-25 at 08:11, Michael Stone wrote:
On Tue, Jun 25, 2019 at 11:09:12AM +0200, Hans wrote:
Might be, but this does not explain, why there are still scripts
and configurations, which are still using the old names. And THAT
i
On Tue, Jun 25, 2019 at 08:46:28AM -0400, The Wanderer wrote:
> On a single computer with any number of interfaces of any type, the new
> names are 100% predictable from one boot to the next. (At least assuming
> you don't change which slot a given network device is connected to; IIRC
> that can ch
On Mon, 2019-06-24 at 22:15 +0200, Steven Post wrote:
> (Please keep me in CC, as I'm not subscribed to the mailing list)
>
> On Sun, 2019-06-23 at 19:16 +0300, andreimpope...@gmail.com wrote:
> > On Lu, 13 mai 19, 11:29:10, Steven Post wrote:
> > >
> > > Recently the numeric keypad stopped worki
Zdenek Kabelac wrote:
> Wow :) where you've been hiding for last ~15 years when format V2 exists ;)
> V1 is considered obsolete for very looong time and it's been even dropped
> from support from version 2.03.
That server has indeed been set up rougly 15 years ago. And until
now, we had no need
On Tue, Jun 25, 2019 at 10:38:10AM +0700, Bagas Sanjaya wrote:
> In this hypothetical scenario, the sudoers rule is applied to ALL systems,
> including production ones, and sysadmins doesn't have proper backups.
On Tue, Jun 25, 2019 at 08:45:13AM -, Curt wrote:
> I'd just get a better hypothet
On 2019-06-25 at 08:11, Michael Stone wrote:
> On Tue, Jun 25, 2019 at 11:09:12AM +0200, Hans wrote:
>
>> Might be, but this does not explain, why there are still scripts
>> and configurations, which are still using the old names. And THAT
>> is the problem.
>
> It isn't because:
> 1) the new na
On 2019-06-25, Hans wrote:
>
> When it was decided to use new names, then ALL related packages should be
> adapted to the new style. If it is not done, this is a bug. More over, IMO it
> is a critical release bug. For a new release I expect those things fixed. It
> is
> a thing of quality.
Ho
On Tue, Jun 25, 2019 at 11:09:12AM +0200, Hans wrote:
Might be, but this does not explain, why there are still scripts and
configurations, which are still using the old names. And THAT is the problem.
It isn't because:
1) the new names are predictable but not constant, so you can't
configure a
On Tue, Jun 25, 2019 at 01:36:23PM +0200, Hans wrote:
> > You mean *your* old files or those coming with *new* Debian packages?
> Here I mean *new* Debian packages. What I want to say is this: Upgrading to a
> new package version should not destroy the system or force the admin to edit
> many con
> You mean *your* old files or those coming with *new* Debian packages?
Here I mean *new* Debian packages. What I want to say is this: Upgrading to a
new package version should not destroy the system or force the admin to edit
many configurations manually.
When it was decided to use new names,
On Tue, Jun 25, 2019 at 12:56:45PM +0200, Hans wrote:
> Hi Richard and Tomas,
>
> maybe I was not clear enough. So I try to explain again:
[...]
> The point is: There are many OLD files from FORMER installations of times
> ago,
You mean *your* old files or those coming with *new* Debian packa
Hi Richard and Tomas,
maybe I was not clear enough. So I try to explain again:
When it is recommended to use the predictable names, then please explain me
(and all the other people), why the heck are configuration files and scripts
still using the old names.
I do not want to know, WHY these a
On Tue, Jun 25, 2019 at 05:07:07AM -0500, Richard Owlett wrote:
> On 06/25/2019 03:49 AM, to...@tuxteam.de wrote:
> >
> >[1]
> >https://wiki.debian.org/NewInStretch#If_you_install_fresh_instead_of_upgrading...
> >You do read the release notes, don't you? ;-)
>
> That reference leads to two pa
On 06/25/2019 03:49 AM, to...@tuxteam.de wrote:
[1]
https://wiki.debian.org/NewInStretch#If_you_install_fresh_instead_of_upgrading...
You do read the release notes, don't you? ;-)
That reference leads to two pages worth reading by fellow newbies.
For good description of the problem (unpr
Hi Tomas,
> The moniker for that is "predictable interface names". And you
> seem to assume that there hasn't been a discussion.
>
> This being Debian, there sure has been one, you just didn't
> notice :-)
>
Might be, but this does not explain, why there are still scripts and
configurations, wh
On Tue, Jun 25, 2019 at 10:03:48AM +0200, Hans wrote:
> Hi folks,
[...]
> The issue:
> Since some time the ethernet devices like wlan0 or eth0 got new names, like
> wlp2s0 or enp0s9 or similar.
>
> Whilst this is no problem to change these manually in
> /etc/network/interfaces,
> there are a
On 2019-06-25, Aidan Gauland wrote:
>>
>> In this hypothetical scenario, the sudoers rule is applied to ALL
>> systems, including production ones, and sysadmins doesn't have proper
>> backups.
> OK, not having a (good) backup system is definitely bad. You should
> always have that even if your se
Hi folks,
there is a little thing, we should either discuss or I should be pointed to
your solution.
The issue:
Since some time the ethernet devices like wlan0 or eth0 got new names, like
wlp2s0 or enp0s9 or similar.
Whilst this is no problem to change these manually in /etc/network/interfaces
On 25/06/19 3:38 PM, Bagas Sanjaya wrote:
> On 24/06/19 06.27, Aidan Gauland wrote:
>
>> I can't really offer an opinion on whether it is dangerous without a
>> more detailed hypothetical scenario, but I would say that is
>> overbroad, and this rule should be narrowed down to only allow
>> running
On 2019-06-25, rhkra...@gmail.com wrote:
> On Mon, Jun 24, 2019 at 12:42:37PM -, Curt wrote:
>> On 2019-06-22, Andy Smith wrote:
>> > I am not aware of any other compression tool that offers to do what
>> > gzip's --rsyncable option does, but I owuld be interested if there
>> > are some that
Hello,
I have a toshiba usb drive. With smartctl i can see some values, hddtemp
show nothing:
smartctl -i /dev/sdc; smartctl -a /dev/sdc | grep 194
smartctl 6.6 2016-05-31 r4324 [i686-linux-4.9.0-9-686-pae] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
On 2019-06-25 04:38, Bagas Sanjaya wrote:
On 24/06/19 06.27, Aidan Gauland wrote:
I can't really offer an opinion on whether it is dangerous without a
more detailed hypothetical scenario, but I would say that is
overbroad, and this rule should be narrowed down to only allow running
certain co
54 matches
Mail list logo
