Felix Miata wrote:
> If the filesystem is being written to less than 5 minutes per year, what
> do you suppose the odds are that power could be lost during any portion of
> that less than 5 minutes of writing? Given my PCs are all running on
> backup power, the odds are virtual zero. I want my boo
Hi folks.
I have Debian 9. I configured my wlan interface to auto connect on startup.
But, networking service does not startup:
> ● networking.service - Raise network interfaces
> Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor
> preset: enabled)
> Active: failed
deloptes composed on 2018-09-12 08:02 (UTC+0200):
> Felix Miata wrote:
>> How often does /boot get written to, as much as 5 minutes per year? All my
>> /boot partitions are EXT2, (in part) /because/ it has no journaling.
> I had the same for years, but recently I upgraded the boot partition to
>
On Tuesday 11 September 2018 23:01:43 Felix Miata wrote:
> Gene Heskett composed on 2018-09-11 22:29 (UTC-0400):
> > On Tuesday 11 September 2018 21:34:27 Felix Miata wrote:
> >> IMO, red because it's red is less likely than red because red was
> >> the
>
>
Felix Miata wrote:
> How often does /boot get written to, as much as 5 minutes per year? All my
> /boot partitions are EXT2, (in part) /because/ it has no journaling.
I had the same for years, but recently I upgraded the boot partition to
ext3 - it is more reliable in case for example when power
On 11.09.2018 15:48, Matthew Crews wrote:
My recommendation is to use a separate /boot partition and make it EXT2.
I'm planning on using ZFS as software raid on which I'll create vols. So it
might be ext2, ext3, ext4.
I've had root / and /boot on same partition ext4 with other directories, except /var, /home, /srv so system will boot even if those directories fill
up. As most data will be at same disks (separated using MD in mirrors), failing both disks at same time will break the system any way. Some solution
On 9/11/18, Felix Miata wrote:
> Andrew McGlashan composed on 2018-09-12 04:01 (UTC+1000):
>
>> Matthew Crews wrote:
>
>>> My recommendation is to use a separate /boot partition and make it EXT2.
>
>> Why not at least ext3? I don't baulk at ext4 btw for /boot -- I can
>> never understand why ext2
Gene Heskett composed on 2018-09-11 22:29 (UTC-0400):
> On Tuesday 11 September 2018 21:34:27 Felix Miata wrote:
>> IMO, red because it's red is less likely than red because red was the
^^^
*Less* likely, not unlikely. IOW, both happen, but red dye cancer l
On Tue, Sep 11, 2018 at 1:16 PM Patrick Bartek wrote:
> On Tue, 11 Sep 2018 00:56:03 -0400
> Default User wrote:
>
> > On Mon, Sep 10, 2018, 23:42 Patrick Bartek
> > wrote:
> >
> > [big snip]
> > >
> > > Well, it is Unstable. So, problems are expected. It's the nature
> > > of the beast. Let
I recently upgraded the sid installation on an i386 machine. With
udev upgraded to 239-8, many devices are no longer detected during
boot, e.g. usb, network card, video, audio. I also have a
not-upgraded buster partition on the same machine -- a large
portion of its dmesg output is simply missing
On Tuesday 11 September 2018 21:34:27 Felix Miata wrote:
> Gene Heskett composed on 2018-09-11 21:21 (UTC-0400):
> > Ben Caradoc-Davies wrote:
> >> I would first identify the *cause* and replace all unreliable
> >> hardware before bothering to restore from backup. If you have
> >> noticed some cor
libssl1.1 version 1.1.1~~pre9-1 is breaking something xfreerdp. I had
to downgrade to
libssl version 1.1.0f-3+deb9u2, and xfreerdp worked again just fine.
Kind of looks like there is a new version coming out, but I wasn't
sure if this problem was addressed. Unfortunately I don't have much
time debu
E: The value 'stable-updates' is invalid for APT::Default-Release as
such a release is not available in the sources
E: _cache->open() failed, please report.
Gene Heskett composed on 2018-09-11 21:21 (UTC-0400):
> Ben Caradoc-Davies wrote:
>> I would first identify the *cause* and replace all unreliable hardware
>> before bothering to restore from backup. If you have noticed some
>> corruption, you likely also have some unnoticed corruption. Continuin
On Tue, 11 Sep 2018 at 17:22, Igor Cicimov wrote:
>
>
> On Tue, 11 Sep 2018 11:45 am Joel Brunetti wrote:
>
>> Hey Team,
>>
>> I'm having trouble booting a previously bootable system.
>> This system has been in use since very shortly before the Stretch release
>> and has always been Stretch.
>>
On 09/10/2018 08:27 AM, Brad Rogers wrote:
On Mon, 10 Sep 2018 11:53:01 + (UTC)
Curt wrote:
Hello Curt,
So uninstall it then in that unfortunate case--with extreme prejudice
Time.
Oh, and I can't be arsed to try PA in the first place. :-)
Or are we dealing with the supernatural her
On Tuesday 11 September 2018 19:13:58 Ben Caradoc-Davies wrote:
> On 12/09/2018 00:59, Greg Wooledge wrote:
> > On Tue, Sep 11, 2018 at 01:52:15PM +0200, Pétùr wrote:
> >> I have some files, with weird permissions:
> >> # ls -la
> >> d-wS--S--T 2 1061270772 2605320832 4096 oct. 7 2412 index.ht
On Tuesday 11 September 2018 15:28:30 Martin McCormick wrote:
[...]
> Any constructive ideas are appreciated. If I left the
> drives mounted all the time, there would be no spew but since
> these are backup drives, having them mounted all the time is
> quite risky.
>
> Martin McCormick WB
On 09/11/2018 01:42 AM, Mimiko wrote:
Hello.
Currently I use ZFS for making a pool of disks, but the system itself is
installed on 2 SSD disks using MD to mirror.
How is now ZFS on handling booting from ZFS mirror. Can I start use ZFS
as root filesystem on latest Debian? Is it stable on upda
Pétùr composed on 2018-09-11 19:45 (UTC+0200):
> Martin composed:
>> don't get crazy about FS corruption. There is no sign this is the case so
>> far. Date and UID's are odd, but valid within ext4. Remove the immutable
>> flag (chattr -i), you will be able to alter the files as you like.
>> One
Andrew McGlashan composed on 2018-09-12 04:01 (UTC+1000):
> Matthew Crews wrote:
>> My recommendation is to use a separate /boot partition and make it EXT2.
> Why not at least ext3? I don't baulk at ext4 btw for /boot -- I can
> never understand why ext2 is recommended when ext4 gives no troubl
On Tue, 11 Sep 2018 11:45 am Joel Brunetti wrote:
> Hey Team,
>
> I'm having trouble booting a previously bootable system.
> This system has been in use since very shortly before the Stretch release
> and has always been Stretch.
> I'm using Grub to boot a fully encrypted system. Each drive is pa
On 12/09/2018 00:59, Greg Wooledge wrote:
On Tue, Sep 11, 2018 at 01:52:15PM +0200, Pétùr wrote:
I have some files, with weird permissions:
# ls -la
d-wS--S--T 2 1061270772 2605320832 4096 oct. 7 2412 index.html
Obvious file system corruption. Unmount, fsck, re-mount, and then
be prepared
On Tue 11 Sep 2018 at 19:34:53 (+0200), Martin wrote:
> Pétùr,
>
> don't get crazy about FS corruption. There is no sign this is the case so
> far. Date and UID's are odd, but valid within ext4. Remove the immutable flag
> (chattr -i), you will be able to alter the files as you like.
>
> One hi
=?UTF-8?Q?=c3=89tienne_Mollier?= writes:
>
> Good Day,
>
> Not sure if that is the kind of answer you would wish to
> expect, but have you considered doing umounts sequentially?
> (optionally after synchronizing file systems)
>
> sync
> umount /var/cache/rsnapshot
> umou
On 9/11/18 9:28 PM, Martin McCormick wrote:
> #Combine 2 256-GB drives in to 1 512 GB drive.
>
> mount /rsnapshot1
> mount /rsnapshot2
> mhddfs /rsnapshot1,/rsnapshot2 /var/cache/rsnapshot -o mlimit=100M
>
-8<8<
> I have actually tried
>
> umount /rsnaps
This has all the earmarks of a race condition because it is
totally intermittent. It succeeds maybe 80% of the time.
I am using rsync to backup a Linux system to a pair of
thumb drives which both appear to be healthy. The mounting
process goes as follows:
#Combine 2 256-GB drives in to
Pétùr writes:
> Le 11/09/2018 à 19:34, Martin a écrit :
>>
>> don't get crazy about FS corruption. There is no sign this is the
>> case so far. Date and UID's are odd, but valid within ext4. Remove
>> the immutable flag (chattr -i), you will be able to alter the files
>> as you like.
>>
>> One hi
On Tue, Sep 11, 2018 at 3:28 AM, Joel Brunetti wrote:
> I'm having trouble booting a previously bootable system.
> This system has been in use since very shortly before the Stretch release
> and has always been Stretch.
> I'm using Grub to boot a fully encrypted system. Each drive is partitioned
>
On Wed, Sep 12, 2018 at 04:01:10AM +1000, Andrew McGlashan wrote:
On 11/09/18 22:48, Matthew Crews wrote:
My recommendation is to use a separate /boot partition and make it EXT2.
Why not at least ext3? I don't baulk at ext4 btw for /boot -- I can
never understand why ext2 is recommended when
On 2018-09-11 18:45, Pétùr wrote:
Le 11/09/2018 à 19:34, Martin a écrit :
don't get crazy about FS corruption. There is no sign this is the case
so far. Date and UID's are odd, but valid within ext4. Remove the
immutable flag (chattr -i), you will be able to alter the files as you
like.
On
On Tue, Sep 11, 2018 at 07:34:53PM +0200, Martin wrote:
don't get crazy about FS corruption. There is no sign this is the case
so far.
umm, yeah, this is pretty classic. it's more likely than not that random
bits will result in file attributes that can be interpreted but are
completely bogus.
My thought process is that there's no reason for any advanced features in /boot
since it should rarely change (aside from the occasional kernel or driver
update).
That said, theres no real harm in using a different filesystem for /boot, such
as ext3, ext4, btrfs, etc., so long as your bootloade
On Tue, Sep 11, 2018 at 07:12:19PM +0200, Pétùr wrote:
> Gimp does not start on debian sid and shows the message:
>
> ---
> BABL version too old!
>
> GIMP requires BABL version 0.1.56 or later.
> Installed BABL version is 0.1.44.
>
> Somehow you or your software packager managed
> to install GIM
Hi,
On 11/09/18 22:48, Matthew Crews wrote:
> My recommendation is to use a separate /boot partition and make it EXT2.
Why not at least ext3? I don't baulk at ext4 btw for /boot -- I can
never understand why ext2 is recommended when ext4 gives no trouble and
has other advantages, even ext3 has j
Le 11/09/2018 à 19:34, Martin a écrit :
don't get crazy about FS corruption. There is no sign this is the case so far.
Date and UID's are odd, but valid within ext4. Remove the immutable flag
(chattr -i), you will be able to alter the files as you like.
One hint will be, check if your system
Pétùr,
don't get crazy about FS corruption. There is no sign this is the case so far.
Date and UID's are odd, but valid within ext4. Remove the immutable flag
(chattr -i), you will be able to alter the files as you like.
One hint will be, check if your system time is ok (both, date and hwclock!
On Tue, 11 Sep 2018 00:56:03 -0400
Default User wrote:
> On Mon, Sep 10, 2018, 23:42 Patrick Bartek
> wrote:
>
> [big snip]
> >
> > Well, it is Unstable. So, problems are expected. It's the nature
> > of the beast. Let us know how it goes. At worst, since .17 works,
> > stick with it until
Gimp does not start on debian sid and shows the message:
---
BABL version too old!
GIMP requires BABL version 0.1.56 or later.
Installed BABL version is 0.1.44.
Somehow you or your software packager managed
to install GIMP with an older BABL version.
Please upgrade to BABL version 0.1.56 or la
On Tue, Sep 11, 2018 at 09:49:32AM -0600, Joe Pfeiffer wrote:
"Thomas Schmitt" writes:
Something trampled the parent directory or its attached data structures.
It appears to be the two inodes, not the parent directory, that got
trampled.
The problem is that it's fairly unlikely that two ino
"Thomas Schmitt" writes:
>
> Something trampled the parent directory or its attached data structures.
It appears to be the two inodes, not the parent directory, that got
trampled.
Le 11/09/2018 à 16:44, Michael Stone a écrit :
On Tue, Sep 11, 2018 at 08:59:56AM -0400, Greg Wooledge wrote:
On Tue, Sep 11, 2018 at 01:52:15PM +0200, Pétùr wrote:
I have some files, with weird permissions:
# ls -la
d-wS--S--T 2 1061270772 2605320832 4096 oct. 7 2412 index.html
Obvious
Hi,
i wrote:
> > What do you get from command stat index.html
Pétùr wrote:
> File: .cache/shotwell/thumbs/thumbs360/thumb0c5c.jpg
> Size: 24576 Blocks: 32 IO Block: 4096 regular file
> Device: 802h/2050d Inode: 4744568 Links: 1
> Access: (5222/--wS-w--w
On Tue, Sep 11, 2018 at 08:59:56AM -0400, Greg Wooledge wrote:
On Tue, Sep 11, 2018 at 01:52:15PM +0200, Pétùr wrote:
I have some files, with weird permissions:
# ls -la
d-wS--S--T 2 1061270772 2605320832 4096 oct. 7 2412 index.html
Obvious file system corruption. Unmount, fsck, re-mount
On Tue 11 Sep 2018 at 14:48:45 (+0200), Pétùr wrote:
> I have two files with this problem.
>
> The first one (index.html) which is considered as directory is in
> .local/share/Trash/expunged
>
> and the second one is a thumb of shotwell:
>
> $ ls -la .cache/shotwell/thumbs/thumbs360/thumb000
Am 11.09.2018 um 14:48 schrieb Pétùr:
> I have two files with this problem.
>
> The first one (index.html) which is considered as directory is in
> .local/share/Trash/expunged
>
> and the second one is a thumb of shotwell:
>
> $ ls -la .cache/shotwell/thumbs/thumbs360/thumb0c5c.jpg
>
On Tue, Sep 11, 2018 at 01:52:15PM +0200, Pétùr wrote:
> I have some files, with weird permissions:
>
> # ls -la
> d-wS--S--T 2 1061270772 2605320832 4096 oct. 7 2412 index.html
Obvious file system corruption. Unmount, fsck, re-mount, and then
be prepared to restore the data from your last g
On 11.09.18 13:52, Pétùr wrote:
> I have some files, with weird permissions:
>
> # ls -la
> d-wS--S--T 2 1061270772 2605320832 4096 oct. 7 2412 index.html
OK, you have the suid, sgid, and sticky bits set, and it's a directory.
Execute (directory navigate) permission is off.
> Cannot delete,
> > does the command alsa-info give a clue?
>
> I didn't know about that one. It gives pages of stuff that look like
> what I used to find in /proc/asound, it certainly knows all about the
> USB device. No error messages, no suggestion as to what might be
> missing.
Since it's USB, the obvious ne
On 9/11/18 5:17 AM, Mimiko wrote:
> My question is more about if I should use ZFS as boot, or stick with old MD
> raid. Would not ZFS booting break if an update to zfs will be applied?
If you intend on using ZFS RAID, do a ZFS RAIDZ pool and not MDADM. ZFS
handles all of the functions of RAID man
I have two files with this problem.
The first one (index.html) which is considered as directory is in
.local/share/Trash/expunged
and the second one is a thumb of shotwell:
$ ls -la .cache/shotwell/thumbs/thumbs360/thumb0c5c.jpg
--wS-w--wT 1 680132648 44094674 24576 mars 27 2211
.c
On 9/11/18 2:04 AM, to...@tuxteam.de wrote:
> On Tue, Sep 11, 2018 at 11:42:43AM +0300, Mimiko wrote:
>> Hello.
>>
>> Currently I use ZFS for making a pool of disks, but the system itself is
>> installed on 2 SSD disks using MD to mirror.
>>
>> How is now ZFS on handling booting from ZFS mirror. C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Sep 11, 2018 at 03:17:11PM +0300, Mimiko wrote:
> On 11.09.2018 12:04, to...@tuxteam.de wrote:
> >>Hello.
> >>
> >>Currently I use ZFS for making a pool of disks, but the system itself is
> >>installed on 2 SSD disks using MD to mirror.
[...]
What file system?
What does 'lsattr' say?
Am 11.09.2018 um 13:52 schrieb Pétùr:
> I have some files, with weird permissions:
>
> # ls -la
> d-wS--S--T 2 1061270772 2605320832 4096 oct. 7 2412 index.html
>
> Cannot delete, cannot change owner or group (what is this user
> 1061270772 and grou
On 11.09.2018 12:04, to...@tuxteam.de wrote:
Hello.
Currently I use ZFS for making a pool of disks, but the system itself is
installed on 2 SSD disks using MD to mirror.
How is now ZFS on handling booting from ZFS mirror. Can I start use ZFS as root
filesystem on latest Debian? Is it stable o
Hi,
Pétùr wrote:
> > d-wS--S--T 2 1061270772 2605320832 4096 oct. 7 2412 index.html
to...@tuxteam.de wrote:
> Whoa. 'S' is a setuid file which is not executable. Exotic, to say
> the least.
Not to speak of the year 2412, and "index.html" being a directory.
> Perhaps you are dealing with fi
On Tuesday 11 September 2018 07:52:15 Pétùr wrote:
> I have some files, with weird permissions:
>
> # ls -la
> d-wS--S--T 2 1061270772 2605320832 4096 oct. 7 2412 index.html
>
> Cannot delete, cannot change owner or group (what is this user
> 1061270772 and group 2605320832 by the way?) even f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Sep 11, 2018 at 01:52:15PM +0200, Pétùr wrote:
> I have some files, with weird permissions:
>
> # ls -la
> d-wS--S--T 2 1061270772 2605320832 4096 oct. 7 2412 index.html
Whoa. 'S' is a setuid file which is not executable. Exotic, to say
t
I have some files, with weird permissions:
# ls -la
d-wS--S--T 2 1061270772 2605320832 4096 oct. 7 2412 index.html
Cannot delete, cannot change owner or group (what is this user
1061270772 and group 2605320832 by the way?) even for root.
How can I get rid of these?
Pétùr
Curt wrote:
> curty@einstein:~$ /usr/sbin/alsa
> alsabat-test alsactl alsa-info
thanks - i didn't look in sbin
regards
Joe wrote:
> Is there conceivably an issue in Stretch of having USB sound but no
> on-board sound? Is that causing the boot process not to build the sound
> infrastructure properly? There is a spare PCIe slot, but it's tiny, and
> I'm not sure I can get a cheap card that will physically fit.
I do
Thanks Brain
On 11.09.2018 09:50, Brian wrote:
On Tue 11 Sep 2018 at 09:36:05 +0200, basti wrote:
Hello,
how can I suggest new Software to Debian?
https://wiki.debian.org/RFP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Sep 11, 2018 at 11:42:43AM +0300, Mimiko wrote:
> Hello.
>
> Currently I use ZFS for making a pool of disks, but the system itself is
> installed on 2 SSD disks using MD to mirror.
>
> How is now ZFS on handling booting from ZFS mirror. Can
On Tue, 11 Sep 2018 08:23:58 +0200
deloptes wrote:
> Joe wrote:
>
> > On Mon, 10 Sep 2018 22:54:26 +0200
>
> >
> > OK, aplay -l as root sees my USB device as card 1.
>
> why as root - are you in the audio group?
No users in audio yet apart from the original installation user. The
ssh use
Hello.
Currently I use ZFS for making a pool of disks, but the system itself is
installed on 2 SSD disks using MD to mirror.
How is now ZFS on handling booting from ZFS mirror. Can I start use ZFS as root
filesystem on latest Debian? Is it stable on updates?
Thanks for suggestions.
On Tue 11 Sep 2018 at 09:36:05 +0200, basti wrote:
> Hello,
> how can I suggest new Software to Debian?
https://wiki.debian.org/RFP
--
Brian.
On Tue 11 Sep 2018 at 08:23:58 +0200, deloptes wrote:
> Joe wrote:
>
> > On Mon, 10 Sep 2018 22:54:26 +0200
>
> >
> > OK, aplay -l as root sees my USB device as card 1.
>
> why as root - are you in the audio group?
Having a user in the audio group is unnecessary. ACLs on the devices are
used.
On Tue 11 Sep 2018 at 08:27:02 +0200, deloptes wrote:
> Brian wrote:
>
> > alsa-base
>
> in stretch there is no alsa-base
That isn't in dispute.
--
Brian.
Hello,
how can I suggest new Software to Debian?
On 2018-09-11, deloptes wrote:
> arne wrote:
>
>> does the command alsa-info give a clue?
>
> what is alsa-info?
>
> $ alsa
> alsabatalsa_inalsaloop alsamixer alsa_out alsatplg alsaucm
>
> regards
>
>
>
curty@einstein:~$ /usr/sbin/alsa
alsabat-test alsactl alsa-info
Y
71 matches
Mail list logo
