* Jari Ruusu wrote:
> loop-AES changes since previous release:
> - Worked around kernel interface changes on 4.13 kernels.
> - Added second util-linux patch to work around gpg 2 pinentry-mode bug.
Thank you!
* Greg KH wrote:
> I'm announcing the release of the 3.10.54 kernel.
These days I don't follow this list that closely anymore but I wonder
why the following patch has not been included:
md/raid6: avoid data corruption during recovery of double-degraded RAID6
http://git.kernel.org/cgit/linux/ker
* Greg Kroah-Hartman <[EMAIL PROTECTED]> wrote:
> It contains a single fix for a problem that could cause a local
> user to cause file system corruption on some types of filesystems.
Some types of filesystems? Which ones?
--
left blank, right bald
pgpDjfZ3kpyxn.pgp
Description: PGP signature
* Gianluca Alberici <[EMAIL PROTECTED]> wrote:
> If i cd into it and ls it is like doing a refresh: everything works
> again for a certain amount of time, then, again. It reminds me an
> old version of CFS which used to claim: 'stale NFS file handle'.
"there are no fish in my pond"
# CONFIG_NFS
Hi,
I noticed the following line in dmesg output with 23-rcX kernels
ACPI Warning (tbutils-0217): Incorrect checksum in table [OEMB] -
5E, should be 31 [20070126]
Before I start investigating the issue I wonder: Is this something
serious or just a minor issue? My system works just fine so far
Hi,
2.6.23-rc1 (as well as 2.6.22.x) produces some section mismatch
warnings during compile on slackware 11 (gcc-3.4.6, glibc-2.3.6):
LD vmlinux.o
MODPOST vmlinux.o
WARNING: vmlinux.o(.text+0x139c1): Section mismatch: reference to
.init.data:trampoline_end (between 'setup_trampoline' and
* "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Does -ck1 patches for 2.6.22 and 2.6.20 make the same job? Or it's
> better to backport -ck1 for 2.6.22 to 2.6.20?
fyi, http://article.gmane.org/gmane.linux.kernel.ck/7850
--
left blank, right bald
pgpZWtSASam7s.pgp
Description: PGP signature
* Paolo Ornati <[EMAIL PROTECTED]> wrote:
> So with this patch "max_loop=32" will create 32 loop devices... but
> then it doesn't allow more of them.
Well, that's what a max_ parameter implies ;p
A manually set limit of loop devices is ok with me. (32 was just an
example -- After all, I could ha
* Matthew <[EMAIL PROTECTED]> wrote:
> I read that now loop devices are being created on demand, which
> obviously (still) not works
yes, someone thought this was a good idea :(
> Is there a way to trigger such creation?
does modprobe loop max_loop=32 work?
--
left blank, right bald
pgp1Dm
* Jari Ruusu <[EMAIL PROTECTED]> wrote:
> loop-AES changes since previous release:
> - loop_twofish.c loop_serpent.c loop_blowfish.c modules included.
> They are not built by default. Add EXTRA_CIPHERS=y make parameter
> to build them.
Just curious, will the ciphers package also be continued/
Hi,
I need to create a moderate amount of v3 keys for loop-aes and wonder
how/if the "openssl rand" implementation differs significantly from
/dev/random concerning entropy.
In case /dev/random and "openssl rand" are somewhat comparable, I
would just use the latter to create the keys.
However, I
Hi,
I'm encountered the following scenario:
Several encrypted external USB HDDs were mounted (via a hub) when
Something Bad happened: Accidentially the cable connecting the hub to
the laptop was disconnected. The devices used at that time were
/dev/sda and /dev/sdb.
Logfiles showed the usual USB
* "Jan C. Nordholz" <[EMAIL PROTECTED]> wrote:
> I'm seeing this for quite a while now (since 2.6.16 at least), but
> without any obvious indicator to what might be causing it... where
> should I continue debugging this?
I bet folks at [EMAIL PROTECTED] would love to hear about this.
--
left bl
* Tomas M <[EMAIL PROTECTED]> wrote:
> I hope you will like it and you will include it in kernel.
> Or, if not, maybe this patch will start some debate regarding
> the current insufficient limit of 255 loop devices.
255 loop devices are insufficient? What kind of scenario do you have
in mind?
-
* emin ak <[EMAIL PROTECTED]> wrote:
> I need to encrypt a jffs2/mtd formatted flash filesystem for an
> embedded device, Normally using a loopback interface (cryptoloop,
> DM-crypt or loop-aes) solves this problem but they are not well
> known on journalling file systems (like jffs2) because of c
* Takashi Iwai <[EMAIL PROTECTED]> wrote:
> At Tue, 12 Dec 2006 17:01:35 +0100,
> markus reichelt wrote:
> >
> > Hi,
> >
> > I'm still having this prob at boot. please advise.
>
> It's the place trying to create OSS audio entry.
> What
Hi,
I'm still having this prob at boot. please advise.
Advanced Linux Sound Architecture Driver Version 1.0.13 (Tue Nov 28
14:07:24 2006 UTC).
ACPI: PCI Interrupt :02:0a.1[A] -> Link [LNKA] -> GSI 19 (level,
low) -> IRQ 16
ACPI: PCI Interrupt Link [LAUI] enabled at IRQ 21
ACPI: PCI Interrupt
Hi,
I still have got the same problem during boot with monolithic vanilla
kernels 2.6.18.x & 2.6.19 when it comes to init of the sound
hardware. Please advise.
Linux tatooine 2.6.19 #1 PREEMPT Sun Dec 3 13:01:23 CET 2006 i686
athlon-4 i386 GNU/Linux
lspci
00:00.0 Host bridge: nVidia Corporation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fruhwirth Clemens <[EMAIL PROTECTED]> wrote:
> On Mon, 2005-01-17 at 22:26 +0100, markus reichelt wrote:
>
> > Fruhwirth Clemens <[EMAIL PROTECTED]> wrote:
> > > This is FUD. To get serious in-depth information ab
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fruhwirth Clemens <[EMAIL PROTECTED]> wrote:
> This is FUD. To get serious in-depth information about the problems
> associated with dm-crypt and loop-aes read,
>
> http://clemens.endorphin.org/LinuxHDEncSettings
excuse me, but that's just too academ
20 matches
Mail list logo
