After a reboot of a Debian/unstable machine, I got:
/dev/cdrw -> sr1
while it was
/dev/cdrw -> sr0
before the reboot. More precisely, the change in the lshw output:
*-scsi:0
physical id: 8c
logical name: scsi2
capabilities: emulated
*-cdrom
Hi
Am 25.04.2017 um 10:53 schrieb Vincent Lefevre:
> After a reboot of a Debian/unstable machine, I got:
>
> /dev/cdrw -> sr1
>
> while it was
>
> /dev/cdrw -> sr0
[..]
> Is it normal that the device names are not stable?
>
> In particular, it is strange that all the symlinks point to sr
For a desktop install from a thumbdrive of testing RC3, there were three
drives plugged in to the motherboard. One drive was the installation
target. The other two had old installs, RC3 and Wheezy.
Bizarrely, the resulting fstab has two swap partitions. One from the
target drive, and a second
On Mon 24 Apr 2017 at 15:10:16 -0500, David Wright wrote:
> On Mon 24 Apr 2017 at 19:37:22 (+0100), Brian wrote:
> >
> > A modicum of reassurance and help is never wasted, particularly for
> > those users who come to this thread in the future.
> >
> > My laptop has a single slotted reader on the
On 04/24/2017 04:12 PM, Ben Caradoc-Davies wrote:
On 24/04/17 22:58, Richard Owlett wrote:
If there were user accessible registers with a running total of
uploaded/downloaded data since device power on would be almost ideal
granularity.
Is ifconfig available on a console during installation?
On 04/23/2017 09:33 PM, songbird wrote:
when my computer is turned off the clock
runs slow.
when my computer is turned on the clock
runs fast.
so any single adjustment in /etc/adjtime
doesn't work (as my number of hours off or
on the computer each day may change).
You may have reached l
Hi,
On 2017-04-25 12:14:30 +0200, Michael Biebl wrote:
> Am 25.04.2017 um 10:53 schrieb Vincent Lefevre:
[...]
> > In particular, it is strange that all the symlinks point to sr0
> > except cdrw, which now points to sr1.
>
> The udev rules responsible for creating those symlinks is
> /lib/udev/ru
I'm running Debian Wheeze on a P3 1/2M memory. Mostly CL.
Mutt 1.5.21 is the culprit ( or am I? )
I subscribe to mailing lists in digest form.
Mutt recognizes the fact when I'm viewing a Debian User digest but not
when I'm reading a 'help-bash' digest from gnu.org. The difference
that's got me
On 2017-04-24 15:57:17 -0700, Mike McClain wrote:
> I'm running Debian Wheeze on a P3 1/2M memory. Mostly CL.
> Mutt 1.5.21 is the culprit ( or am I? )
> I subscribe to mailing lists in digest form.
> Mutt recognizes the fact when I'm viewing a Debian User digest but not
> when I'm reading a 'h
On 04/24/2017 11:19 AM, Cindy-Sue Causey wrote:
Mine will occasionally do something like this. In my case, it gives
the appearance it's switching back and forth between entire cursor
themes. Is there a chance that's actually what's going on here rather
than it "just" being about pixel size?
Min
Am 25.04.2017 um 16:09 schrieb Vincent Lefevre:
> Hi,
>
> On 2017-04-25 12:14:30 +0200, Michael Biebl wrote:
>> Am 25.04.2017 um 10:53 schrieb Vincent Lefevre:
> [...]
>>> In particular, it is strange that all the symlinks point to sr0
>>> except cdrw, which now points to sr1.
>>
>> The udev rules
On Tue 25 Apr 2017 at 17:22:28 (+0200), Vincent Lefevre wrote:
> On 2017-04-24 15:57:17 -0700, Mike McClain wrote:
> > I'm running Debian Wheeze on a P3 1/2M memory. Mostly CL.
> > Mutt 1.5.21 is the culprit ( or am I? )
> > I subscribe to mailing lists in digest form.
> > Mutt recognizes the f
craigswin composed on 2017-04-25 04:41 (UTC-0700):
> For a desktop install from a thumbdrive of testing RC3, there were three
> drives plugged in to the motherboard. One drive was the installation
> target. The other two had old installs, RC3 and Wheezy.
>
> Bizarrely, the resulting fstab has
Ric Moore wrote:
> On 04/23/2017 09:33 PM, songbird wrote:
>> when my computer is turned off the clock
>> runs slow.
>>
>> when my computer is turned on the clock
>> runs fast.
>>
>> so any single adjustment in /etc/adjtime
>> doesn't work (as my number of hours off or
>> on the computer each
Looking through bugs in the Mnemosyne package I noticed a couple of
old and stale reports that could have already been closed. E.g. the
discussion in report #783929 ends with the upstream developer saying that
Mnemosyne is working as intended and in the last message he simply
writes "Done." – yet,
15 matches
Mail list logo