Hello!
I tried to install current debian testing into Hyper-V (Windows 2012 R2)
virtual machine (generation 2, UEFI boot).
The virtual machine has booted successfully, the installer starts in text
mode, but the keyboard does not respond.
If I select "Graphical install" mouse works, but keyboard ju
On Mon, Apr 28, 2014 at 11:01:06PM +0200, Karsten Merker wrote:
> On Sun, Apr 27, 2014 at 07:35:35AM +0100, Ian Campbell wrote:
>
> > I think u-boot has some sh-style control loops you can use? (for x in
> > fstype1 fstype2; do ...). People keep saying one can just use "fsload"
> > too, but I've n
Le 28/04/2014 22:25, Sébastien Bernard a écrit :
Le 28/04/2014 22:01, Thomas Schmitt a écrit :
Hi,
Sebastien's machine now has a xorriso-1.3.7 (the current development
snapshot) with changed libburn/async.c.
The callers of add_worker() now declare:
union w_list_data o;
rather than
Le 28/04/2014 20:21, Patrick Baggett a écrit :
Seb,
Yes, I can reproduce this issue.
{ 1, 0 }
{ 1, 1 }
returns 0, when it should return -1.
Interestingly, if you use:
{ 1, 1, 1, 1, 0 } //i.e. 5 bytes
{ 1, 1, 1, 1, 1 } //i.e. 5 bytes
as the strings, it returns -1. So it clearly has a probl
Le 28/04/2014 22:01, Thomas Schmitt a écrit :
Hi,
Sebastien's machine now has a xorriso-1.3.7 (the current development
snapshot) with changed libburn/async.c.
The callers of add_worker() now declare:
union w_list_data o;
rather than
struct union_member o;
The type of the f
Hi,
Sebastien's machine now has a xorriso-1.3.7 (the current development
snapshot) with changed libburn/async.c.
The callers of add_worker() now declare:
union w_list_data o;
rather than
struct union_member o;
The type of the fourth parameter of add_worker has been changed
fro
Hi,
On 28/04/2014 18:25, Thomas Schmitt wrote:
has a struct on heap (#L102, #L138, #L146):
struct w_list{
...
union w_list_data
{
...
struct write_opts write;
...
} u;
}
...
struct w_list *a;
...
a = ca
Hi,
> No, it's plain wrong. Unions are fine, if used properly. You aren't
> using them properly.
Duh. You convinced me. The callers do it wrong, indeed.
They would have to use local union variables instead of their actual
structs. The parameter of add_worker() should be a pointer to the
union, no
> As a cherry on top of this cake, we would also be very happy to
> understand why a non crypted swap device on an hardware-encrypted
> disk is good enough while it is not for other partitions.
Every partition can potentially have different security requirements.
Software encryption is useful for
On Mon, Apr 28, 2014 at 1:20 PM, Thomas Schmitt wrote:
> Hi,
>
> > I really need a disassembly and to be able to probe the runtime
> It's the job of a C union to provide a common hull around objects
> of different size. One may dispute whether using union is a good
> idea (like overloading in the
Seb,
Yes, I can reproduce this issue.
{ 1, 0 }
{ 1, 1 }
returns 0, when it should return -1.
Interestingly, if you use:
{ 1, 1, 1, 1, 0 } //i.e. 5 bytes
{ 1, 1, 1, 1, 1 } //i.e. 5 bytes
as the strings, it returns -1. So it clearly has a problem if the string is
exceptionally short. That got
Hi,
> I really need a disassembly and to be able to probe the runtime
> stack a bit, so that really means that I need to build the code. :)
The current example would be a bit too opulent, i guess:
-rwxr-xr-x 1 thomas thomas 3753398 avril 28 17:49 xorriso/xorriso
(wget http://www.gnu.org/softw
On Mon, Apr 28, 2014 at 12:25 PM, Thomas Schmitt wrote:
> Hi,
>
> Patrick Baggett:
> > Could you explain the context around this code? Perhaps the source is
> > not really "alignment safe" and could use some patching upstream? I'd
> > be happy to provide advice or code samples.
>
> The context wa
Hi,
i wrote:
> struct write_opts write;
> ...
> add_worker(Burnworker_type_writE, d,
> (WorkerFunc) write_disc_worker_func, &o);
Urgh. I copied the wrong struct definition. Line 592 bears of course:
struct write_opts o;
which is used in the call of add_worker().
Ha
Hi,
Patrick Baggett:
> Could you explain the context around this code? Perhaps the source is
> not really "alignment safe" and could use some patching upstream? I'd
> be happy to provide advice or code samples.
The context was misposted to bug report 731806 as message #87:
https://bugs.debian.o
On Mon, Apr 28, 2014 at 11:39 AM, Thomas Schmitt wrote:
> Hi,
>
> sorry for mis-posting the first reply for bug 746254 to this bug 731806.
>
> Meanwhile it turned out that the SIGBUS vanishes if i do not
> compile with -O2 or if i replace "a->u =" by memcpy().
>
> Could you explain the context ar
Hi,
sorry for mis-posting the first reply for bug 746254 to this bug 731806.
Meanwhile it turned out that the SIGBUS vanishes if i do not
compile with -O2 or if i replace "a->u =" by memcpy().
So it seems worth to check whether genisoimage resp. strcmp() work
properly if not compiled with -O2.
On Mon, Apr 28, 2014 at 11:25 AM, Sébastien Bernard wrote:
> Le 28/04/2014 16:05, Patrick Baggett a écrit :
>
> strcmp() may well be implemented by word comparisons. But then it
>
>> is the duty of the implementation to properly handle the ends of
>>> the strings even if those are not word alig
Le 28/04/2014 16:05, Patrick Baggett a écrit :
strcmp() may well be implemented by word comparisons. But then it
is the duty of the implementation to properly handle the ends of
the strings even if those are not word aligned.
Indeed, the correct fix is using strcmp. Meanwhil
Hi,
> Program received signal SIGBUS, Bus error.
> add_worker (w_type=3, d=0x161128 , f=0xd1b20
> 149 a->u = *(union w_list_data *)data;
Other than expected from the first report in bug 731806,
the problem does not sit in libisofs but in libburn/async.c.
(Other predecessor developer
On Mon, Apr 28, 2014 at 8:17 AM, Sébastien Bernard wrote:
> Le 28/04/2014 14:15, Thomas Schmitt a écrit :
>
> Hi,
>>
>> Sébastien Bernard:
>>
>>> result from strcmp('\','\0001' is 0)
>>> result from strcmp('\','\0001' is -1)
>>> Typicaly, an endianness error.
>>>
>> But one in strcmp(), n
Le 28/04/2014 14:15, Thomas Schmitt a écrit :
Hi,
Sébastien Bernard:
result from strcmp('\','\0001' is 0)
result from strcmp('\','\0001' is -1)
Typicaly, an endianness error.
But one in strcmp(), not in your code or the one of genisoimage.
You compare an empty string with a string that
Package: installation-reports
Hi,
As briefly mentioned in IRC, trying to install from
debian-testing-amd64-netinst.iso[1] on an SD card in an UEFI-hybrid
laptop the installer won't even appear. A series of "syntax error"
scroll down the screen very fast and after about one or two seconds
the grub
Hi,
Sébastien Bernard:
> result from strcmp('\','\0001' is 0)
> result from strcmp('\','\0001' is -1)
> Typicaly, an endianness error.
But one in strcmp(), not in your code or the one of genisoimage.
You compare an empty string with a string that contains one
character 0x01.
This is under
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 28 Apr 2014 13:10:14 +0200
Source: cdebconf
Binary: cdebconf cdebconf-gtk libdebconfclient0 libdebconfclient0-dev
cdebconf-udeb cdebconf-priority libdebconfclient0-udeb cdebconf-text-udeb
cdebconf-slang-udeb cdebco
cdebconf_0.190_amd64.changes uploaded successfully to localhost
along with the files:
cdebconf-priority_0.190_all.udeb
cdebconf_0.190_amd64.deb
cdebconf-gtk_0.190_amd64.deb
libdebconfclient0_0.190_amd64.deb
libdebconfclient0-dev_0.190_amd64.deb
cdebconf-udeb_0.190_amd64.udeb
libdebcon
Le 28/04/2014 13:20, Thomas Schmitt a écrit :
[genisoimage]
(gdb) x rpnt
0x1ea7f9:0x
(gdb) x lpnt
0x1e9dc1:0x0100
(gdb) n
659if (strcmp(rpnt, lpnt) == 0) {
Both values match the prescribed names for "." and ".." in ECMA-119
(aka ISO 9660), 6.8.2.2 Identification of
On Mon, Apr 28, 2014 at 01:20:20PM +0200, Thomas Schmitt wrote:
>Hi,
>
>> I may provide you access to a shell account on my machines if needed.
>
>Yes, please.
>
>Plus a directory tree
> ./tmp/miniiso/cd_tree
>which can cause the xorriso crash.
>
>
>> Sparc architecture is extremely picky about al
Your message dated Mon, 28 Apr 2014 11:33:51 +
with message-id
and subject line Bug#745359: fixed in cdebconf 0.190
has caused the Debian Bug report #745359,
regarding cdebconf-gtk-udeb: fails to extend banner when needed
to be marked as done.
This means that you claim that the problem has be
Morning,
I have several servers that block regularly is very random, some were stuck
4 times in one month, another 2 times and only one time. The space between
the blocks is truly random.
I noticed that information was common in these blocks, and allowed me the
grace logs Kelvin González l
Hi,
> I may provide you access to a shell account on my machines if needed.
Yes, please.
Plus a directory tree
./tmp/miniiso/cd_tree
which can cause the xorriso crash.
> Sparc architecture is extremely picky about alignement. Bad alignement,
> yields SIGSEGV whereas intel only do it in the l
Le 28/04/2014 12:09, Thomas Schmitt a écrit :
Hi,
I tried with the xorriso -as mkisofs command, with no luck.
This command terminates with a SIGBUS no matter of the options I pass on
the command line.
Ouch.
I have no Debian of arch "sparc" in reach.
I may provide you access to a shell account
On Fri, 2014-04-25 at 19:06 +0200, Karsten Merker wrote:
> On Fri, Apr 25, 2014 at 08:42:23AM +0100, Ian Campbell wrote:
>
> > Aside: "EfikaMX" is listed in 2.1.2.4 as no longer supported, but we do
> > supply a specific image for it using the armmp kernel:
> > http://d-i.debian.org/daily-images/a
Hi,
> I tried with the xorriso -as mkisofs command, with no luck.
> This command terminates with a SIGBUS no matter of the options I pass on
> the command line.
Ouch.
I have no Debian of arch "sparc" in reach.
> xorriso -as mkisofs -r -J -o ./tmp/miniiso/mini.iso -G /boot/isofs.b -B
> ... ./t
I've been looking through this problem.
genisoimage is reporting a problem with . and .. aliased to the same ''
name.
logs of the problem:
-
genisoimage -r -J -o ./tmp/miniiso/mini.iso -G /boot/isofs.b -B ...
./tmp/miniiso/cd_tree
I: -input-charset not specified, using utf-8 (dete
35 matches
Mail list logo
