On Tue, May 14, 2019 at 10:56:18PM +, Riccardo Paolo Bestetti wrote:
> >>Hello,
> >>
> >>Bug #868015 has been open since Jul 2017 [...]
> >Hi Riccardo, I'll take a chance at answering your question [...]
[good points]
> Your input is much appreciated and you made some valid and interesting p
On Tue 14 May 2019 at 16:12:29 (-0500), Dennis Wicks wrote:
> Greetings;
>
> First off, I am running Debian Buster/Sid (that's what it says!) and
> the kernel is 4.19.0-4-686-pae. 32 bit system,
> 4 Gig of memory (3.xx usable!), IDE disks.
>
> My boots are getting slower and slower. I'll start fr
I have a new buster system with a bind setup based on (much) older*
systems, on which it worked fine. On buster, it doesn't.
In two different places in my configuration I referred to files or
directories that were outside of bind proper, and in both cases this
failed with permission problems.
I'm
On Sun 12 May 2019 at 23:35:11 (+1000), Erik Christiansen wrote:
> On 12.05.19 13:45, Eric S Fraga wrote:
> > On Sunday, 12 May 2019 at 17:52, Erik Christiansen wrote:
> > > On 11.05.19 14:38, Eric S Fraga wrote:
> > >> This is nice; is there an equivalent for FAT file systems? Most of the
> > >>
>>Hello,
>>
>>Bug #868015 has been open since Jul 2017 and the fix consists in 3
>>lines added to the system unit file. I.e. knockd.service lacks the
>>[Install] section and thus the service can't be made to auto-start after a
>>reboot.
>>Since the maintainer doesn't seem interested in fixing it
Greetings;
During the boot process there are several mount "jobs"
started, and they all finish/fail with two messages;
Dependency failed for ...
Timeout waiting for ...
that is except for root.
I removed all the mounts for user partitions from fstab and
just left the mounts
Greetings;
First off, I am running Debian Buster/Sid (that's what it
says!) and the kernel is 4.19.0-4-686-pae. 32 bit system,
4 Gig of memory (3.xx usable!), IDE disks.
My boots are getting slower and slower. I'll start from the top.
The first thing that happens is I get a message
R
On Tue, May 14, 2019 at 12:11:17PM -0700, David Christensen wrote:
On 5/14/19 4:23 AM, Michael Stone wrote:
On Thu, May 09, 2019 at 10:48:31PM -0700, David Christensen wrote:
2019-05-09 22:00:27 root@po /mnt/scratch
# time dd if=/dev/urandom of=foo bs=1M count=1K conv=fsync
don't bother doing
On 5/14/19 4:23 AM, Michael Stone wrote:
On Thu, May 09, 2019 at 10:48:31PM -0700, David Christensen wrote:
2019-05-09 22:00:27 root@po /mnt/scratch
# time dd if=/dev/urandom of=foo bs=1M count=1K conv=fsync
don't bother doing this, urandom will be the bottleneck and it will just
confuse thin
On Tue, 14 May 2019 16:57:34 +0200
Kaj Persson <70147pers...@telia.com> wrote:
> Den 2019-05-12 kl. 13:59, skrev arne:
> > On Sun, 12 May 2019 13:08:33 +0200 (CEST)
> > "70147pers...@telia.com" <70147pers...@telia.com> wrote:
> >
> >> I have no sound at all. By starting e.g. VLC or Audacity with
Hi.
On Tue, May 14, 2019 at 10:20:47AM -0700, Ross Boylan wrote:
> Noticing the "write on read-only" error, and remembering it should be
> read-only, I added that to the mount options. Which still failed, but
> differently:
> root@barley:~/tempserver-check# date; strace -f mount -r
> /dev
On Tue, May 14, 2019 at 10:20 AM Ross Boylan
wrote:
>
> Noticing the "write on read-only" error, and remembering it should be
> read-only, I added that to the mount options. Which still failed, but
> differently:
Well, it failed differently in the sense that it succeeded :) Yay!
I was fooled by t
Noticing the "write on read-only" error, and remembering it should be
read-only, I added that to the mount options. Which still failed, but
differently:
root@barley:~/tempserver-check# date; strace -f mount -r
/dev/stretch-vg/boot stretch_boot
Tue 14 May 2019 10:07:05 AM PDT
execve("/usr/bin/mount
Hi.
On Tue, May 14, 2019 at 09:52:10AM -0700, Ross Boylan wrote:
> Here's the info:
Nothing interesting in the strace output, short of:
:
...
mount("/dev/mapper/stretch--vg-boot",
"/root/tempserver-check/stretch_boot", "ext4", 0, NULL) = -1 EIO
(Input/output error)
...
The reason being
Here's the info:
root@barley:~/tempserver-check# date; strace -f mount
/dev/stretch-vg/boot stretch_boot
Tue 14 May 2019 09:33:01 AM PDT
execve("/usr/bin/mount", ["mount", "/dev/stretch-vg/boot",
"stretch_boot"], 0x7ffed2c87238 /* 26 vars */) = 0
brk(NULL) = 0x5575487e
On Tue 14 May 2019 at 16:09:23 (-), Curt wrote:
> On 2019-05-12, 70147pers...@telia.com <70147pers...@telia.com> wrote:
> >
> > I have no sound at all. By starting e.g. VLC or Audacity with a
> > *.wav file I can see this executed, in Audacity also the wave form, but
> > nothing from the loud
On 5/14/19 12:34 AM, Lothar Schilling wrote:
Thanks for your help, David. But to boot the machine from a live CD I
will have to pay a visit to the computing centre in Frankfurt anyway. So
instead of running a diagnostic tool I am going to install the system
from scratch, this time using a 64bit v
On 2019-05-12, 70147pers...@telia.com <70147pers...@telia.com> wrote:
>
> I have no sound at all. By starting e.g. VLC or Audacity with a
> *.wav file I can see this executed, in Audacity also the wave form, but
> nothing from the loudspeaker.
Since July, 2018?
https://lists.debian.org/debian-u
Den 2019-05-12 kl. 19:30, skrev David Wright:
On Sun 12 May 2019 at 13:08:33 (+0200), 70147pers...@telia.com wrote:
Inxi is telling that the sound card, Device-1, is Intel 82801I HD Audio, and
the driver: snd_hda_intel.
This raises the question of what device 0 is, and whether the sound
is
Den 2019-05-12 kl. 17:28, skrev Jonas Smedegaard:
Quoting Hans (2019-05-12 17:12:13)
Got in the same problem half a year ago. Some program was blocking the
sounddevice.
I remeber, there was a command. which shows, which application is just
accessing the sound device (dev/snd). Maybe someone
Den 2019-05-12 kl. 13:59, skrev arne:
On Sun, 12 May 2019 13:08:33 +0200 (CEST)
"70147pers...@telia.com" <70147pers...@telia.com> wrote:
I have no sound at all. By starting e.g. VLC or Audacity with a
*.wav file I can see this executed, in Audacity also the wave form,
but nothing from the louds
On Tue 14 May 2019 at 13:30:12 (+0200), Albretch Mueller wrote:
> My question may not have been clear enough on my previous post about
> reinstalling debian, but I think I have a better idea about how to
> solve many of my problems.
>
> I have an installation based on:
>
> $ uname -a
> Linux ni
Hi.
On Tue, May 14, 2019 at 01:28:47PM -, Curt wrote:
> On 2019-05-14, Reco wrote:
> > Hi.
> >
> >> I am trying to read some files off of a virtual disk without running
> >> the entire virtual machine.
> >
> > Can you post the output of (in that order):
> >
> > strace -f mount /de
On 2019-05-14, Reco wrote:
> Hi.
>
>> I am trying to read some files off of a virtual disk without running
>> the entire virtual machine.
>
> Can you post the output of (in that order):
>
> strace -f mount /dev/stretch-vg/boot stretch_boot
> dmesg | trail
I looked for trail (it's not in my
On Tue, May 14, 2019 at 01:30:12PM +0200, Albretch Mueller wrote:
> As if I had installed Debian afresh.
My suggestion for this, since you are in "paranoid mode", is to do
exactly that, but without the "as if" part :-)
I install Debian by using debian-installer and installing only the
base syste
On 2019-05-14, Albretch Mueller wrote:
> My question may not have been clear enough on my previous post about
> reinstalling debian, but I think I have a better idea about how to
> solve many of my problems.
>
> I have an installation based on:
>
> $ uname -a
> Linux niggahme 4.9.0-6-amd64 #1 SM
On Mon, May 13, 2019 at 10:58:45AM +0200, Lothar Schilling wrote:
Am 13.05.2019 um 10:51 schrieb Tixy:
On Mon, 2019-05-13 at 10:30 +0200, Lothar Schilling wrote:
[...]
# uname -a
Linux [my.server.com] 4.9.0-9-686-pae #1 SMP Debian 4.9.168-1
(2019-04-12) i686 GNU/Linux
So you're running a 32-bi
My question may not have been clear enough on my previous post about
reinstalling debian, but I think I have a better idea about how to
solve many of my problems.
I have an installation based on:
$ uname -a
Linux niggahme 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1
(2018-05-07) x86_64 GNU/Linux
On Thu, May 09, 2019 at 10:48:31PM -0700, David Christensen wrote:
2019-05-09 22:00:27 root@po /mnt/scratch
# time dd if=/dev/urandom of=foo bs=1M count=1K conv=fsync
don't bother doing this, urandom will be the bottleneck and it will just
confuse things
Hi.
> I am trying to read some files off of a virtual disk without running
> the entire virtual machine.
Can you post the output of (in that order):
strace -f mount /dev/stretch-vg/boot stretch_boot
dmesg | trail
e2fsck -fn /dev/stretch-vg/boot
Reco
[Sorry: original sent before complete; ignore earlier message]
I am trying to read some files off of a virtual disk without running
the entire virtual machine.
(Running a VM would involve at least using a later version of the
VirtualBox, or a switch to KVM,
and I already have enough complexity).
Thanks for your help, David. But to boot the machine from a live CD I
will have to pay a visit to the computing centre in Frankfurt anyway. So
instead of running a diagnostic tool I am going to install the system
from scratch, this time using a 64bit version.
When I attempt to mount a block device, I get the error:
-
root@barley:~/tempserver-check# date; mount /dev/stretch-vg/boot stretch_boot
Mon 13 May 2019 11:42:15 PM PDT
mount: /root/tempserver-check/stretch_boot: can't read superblock on
/dev/mapper/stretch--vg-boot.
33 matches
Mail list logo
