Hello Christoph,
thank you for your fast reply.
> So, my recommendation would be to try:
> > $SERVER["socket"] == ":80" { include "ssl-redirect.conf" }
> > $SERVER["socket"] == ":443" { include "ssl.conf" }
> > $SERVER["socket"] == "[::]:80" { }
> > $SERVER["socket"] == "[::]:443"{ }
I
Package: lighttpd
Version: 1.4.45-1
Severity: normal
Tags: ipv6
Dear Maintainer,
I am trying to have my lighttpd listen on port 80 and 443 for both ipv6 and
ipv4. Please see attached config for how I am trying to achieve this.
It ends up listening on 80 and 443 for ipv4, but only on port 80 for
Package: bind9
Version: 1:9.8.4.dfsg.P1-6+nmu2+deb7u3
Severity: important
Dear Maintainer,
I can not upgrade bind9 on my system.
sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0
07, 2014 at 10:42:53PM +0200, Hilmar Preusse wrote:
On 14.05.06 Johannes Schlumberger (paso.a...@uni.de) wrote:
Hi,
when using Warsaw Theme like this:
\usetheme{Warsaw}
\setbeamertemplate{background canvas}[vertical shading]
[bottom=red!10,top=blue
maintainers or who else you see fit to
work on this bug, provided they also keep it private.
thank you,
Johannes
package sasl2-bin
tags 716723 + moreinfo
thanks
On Thu, Jul 11, 2013 at 10:36:40PM +0200, Johannes Schlumberger wrote:
Configuring sasl2-bin
Hi Roberto,
good work on this issue. I think you are correct, the file was originally
created on an ultrasparc 10 which is big endian, and has later been moved to an
x86 machine.
the bug can be closed.
thanks,
Johannes
Hi Roberto,
thank you for looking into this. I will send you a
Package: mdadm
Version: 3.2.5-5
Severity: important
One of my raid arrays (md2) failed and I removed the faulty disk (sdf1) from it
using mdadm /dev/md2 -r /dev/sdf1. Trying to readd the disk using mdadm /dev/md2
-a /dev/sdf1 resulted in a seemingly successful run without an error message.
Package: sasl2-bin
Version: 2.1.25.dfsg1-6+deb7u1
Severity: important
Dear Maintainer,
this one has been going on for a while (2 years+ I would say) during a
dist-upgrade I saw this message box for the first time:
Configuring sasl2-bin
Failed to upgrade /etc/sasldb2
The
Package: boxbackup-client
Version: 0.11.1~r2837-1
Severity: normal
Tags: upstream
Dear Maintainer,
I have the following backup location specified on my client
spjsschl-home
{
Path = //home//spjsschl
ExcludeDir = //home/spjsschl/data-scratch/data
ExcludeDir =
Package: astyle
Version: 1.24-1
Severity: normal
Tags: upstream
Hi,
for functions returning an int * it works correctly:
$ cat server.c
int *
f(void) {
return a;
}
$ astyle server.c
formatted /tmp/server.c
$ cat server.c
int *
f(void)
{
return a;
}
however, functions returning
The problem is not in wireless-tools, but most likely in the driver, or if you
are using WPA/WPA2, perhaps in wicd (you might want to try network-manager and
see if that improves anything).
I see, thank you. The networks I have tried are all plain unencrypted networks,
networkmanager has
Package: wireless-tools
Version: 30~pre9-5
Severity: important
When setting the ap for my wlan device I need to set it *twice* in order for
the essid to become visible. This renders wicd unusable since it only sets the
ap once and then fails to connect. Spamming manual iwconfig set ap commands in
--
Johannes Schlumberger Department of Computer Science IV
Martensstrasse 1 D-91058 Erlangen Germany University of Erlangen-Nuremberg
http://wwwcip.informatik.uni-erlangen.de/~spjsschl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
PROTECTED]:/tmp/vortrag]$
==
the vortrag.tex* files are attached.
mfg,
Johannes
--
Johannes Schlumberger Department of Computer Science IV
Martensstrasse 1 D-91058 Erlangen Germany University of Erlangen-Nuremberg
http
Hi,
I don't know where the error lies, but I created two loop devices loop0
and loop1, added them to a new RAID 1 md0 device, and ran cryptsetup on
the resulting md0 successfully.
Ditto. I've succesfully setup a crypto mapping on a raid1 device under
qemu, which leads me to believe
Hi,
Could you build a new kernel which includes the patch attached to bug
report #304507 and try again?
http://bugs.debian.org/cgi-bin/bugreport.cgi/2.6-bd-claim.patch?bug=304507;msg=5;att=1
It sems the same to me. This is kernel -asso-50 (I attached the config to the
inital bugreport mail)
Hi,
I just want to point out, so far after each test I brought the system back
into the beginning state (kernel, dmsetup-package, etc).
regards,
Johannes
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi,
I just want to point out, so far after each test I brought the system back
into the beginning state (kernel, dmsetup-package, etc).
Yes, that's good.
I just wanted to make shure, we are stil talking about the same setup :)
Could you please try a new compile, this time, skip the
Hi,
Meanwhile, could you add the following to the above mentioned debugging
output:
printk(dumping stack for %s:\n, current-comm);
dump_stack();
(right after the above printk in bd_claim())
And then send another dmesg this way...this should tell us which
process/kernel thread it is
Hi,
Thanks, this looks mighty suspicious...it looks like /dev/md0 is mounted
as your root partition by the initramfs? Please provide me with ls -al
/dev/root and cat /proc/cmdline as well as the contents of your grub
or lilo config file.
I am so sorry for stealing yours and other persons
Hi,
[22:28:[EMAIL PROTECTED]:/tmp]# echo '0 1 crypt aes-cbc-essiv:sha256 \
0123456789abcdef0123456789abcdef 0 /dev/md0 0' map
[22:28:[EMAIL PROTECTED]:/tmp]# dmsetup create root map
device-mapper: reload ioctl failed: Invalid argument
Command failed
Could you try this again with
Hi,
Ok, could you create a file called e.g. map containing the following line:
0 1 crypt aes-cbc-essiv:sha256 0123456789abcdef0123456789abcdef 0
/dev/md0 0
shure.
[22:28:[EMAIL PROTECTED]:/tmp]# echo '0 1 crypt aes-cbc-essiv:sha256 \
0123456789abcdef0123456789abcdef 0 /dev/md0 0' map
Hi,
This would suggest that the problem is not with cryptsetup at least.
Something seems wonky with device-mapper in general.
Whom should I be talking to about this?
Just to make sure, do you think you could install the Debian packaged
kernel, boot it and try to setup the mapping with
Hi,
Also...which device is / on? I.e. /dev/root is an alias of
/dev/hdwhat?
It is hdd6 at the moment, i am going to copy it back to md0 once i got the
cryptlayer on it working.
regards,
Johannes
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Hi,
[23:24:[EMAIL PROTECTED]:/home/spjsschl]# dmsetup table
swap2: 0 995967 crypt aes-cbc-plain
8fd07cf5cecac858cdd2c0ce673449b4c1734cecbe8a24e5be629d542c975cf1 0 22:5 0
swap1: 0 6458067 crypt aes-cbc-plain
dde5fec1ee7146100bc83af997171ce196c2d1c453134d21e574f85ccc296588 0 22:65 0
Which
Hi,
And while we're at it, cat /proc/partitions to make sure that the
kernel and fdisk agree on partition sizes.
[01:53:[EMAIL PROTECTED]:/home/spjsschl]# cat /proc/partitions
major minor #blocks name
22 0 160086528 hdc
22 1 19543041 hdc1
22 29775552 hdc2
22
Hi,
Ok, one more test...could you deallocate both swap mappings and then try
to setup your root mapping?
[01:49:[EMAIL PROTECTED]:/home/spjsschl]# swapoff -a cryptsetup remove swap1
cryptsetup remove swap2 cryptsetup -c aes -s 256 -d /dev/stdin create root
/dev/md0 /key
Command failed:
Hi,
after catching a little sleep I made a stacktrace of the cryptsetup call in my
initial mail. It is attached.
I think the Problem is in line 105 of the trace, since I do not have much
knowledge about devicemapper internas I am not able to see what is going wrong
exactly.
regards,
Johannes
Hi,
and thanks for the trace, the problem is indeed here:
ioctl(3, DM_TABLE_LOAD, 0x80a2040) = -1 EINVAL (Invalid argument)
that means that crypt is not a valid device-mapper target.
That in turn means that dm-crypt was not loaded and could not be
dynamically loaded by the kernel.
Hi,
Unfortunately I am not able to reproduce this. Using a qemu machine with
two virtual disks in a RAID set, the crypt mapping is setup correctly.
If I do make sure that the dm-crypt.ko module is not available, the
error messages and strace exactly match yours.
What output do you get
Package: cryptsetup
Version: 2:1.0.4+svn26-1
Severity: important
Hi,
when trying to create a mapping for /dev/md0 cryptsetup fails to do so.
[04:11:[EMAIL PROTECTED]:/home/spjsschl]# cryptsetup -c aes -s 256 -d /dev/stdin
create root /dev/md0 /key
Command failed: device-mapper: reload ioctl
Package: e2fsprogs
Version: 1.39-1
Severity: minor
Tags: l10n
Hi,
There is a minor mistake in the German Translation of tune2fs -c
tune2fs -c 250 $device
prints:
Setze maximale Mount-Anzahl zu auf 250
while it shuold be:
Setze maximale Mount-Anzahl auf 250
best regards,
Johannes
-- System
Package: latex-beamer
Version: 3.06-1
Severity: minor
Hi,
when using Warsaw Theme like this:
\usetheme{Warsaw}
\setbeamertemplate{background canvas}[vertical shading]
[bottom=red!10,top=blue!10]
there is a white vertical rim at the right frameside. The rim
Package: mdadm
Version: 1.12.0-1
Severity: wishlist
Hi,
could you please include the possibility to add a disk to an existing RAID5
device in order to expand the usable space on the device?
regards,
Johannes
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT
Package: aqmoney
Version: 0.6.3-2
Severity: normal
Hi,
since about two Weeks aqmoney does no longer work for me.
Every time I use the commands balance or turnover aqmoney dies as follows:
ERROR: nothing received (113) at API::_handleMessageQueue()
(Full Output below)
best regards,
Johannes
35 matches
Mail list logo
