summaryrefslogtreecommitdiffstats
path: root/results/classifier/zero-shot/118/graphic/1024275
blob: b3bfd435fc4d36dffeeff9d78e756dc62157bea3 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
graphic: 0.865
device: 0.712
socket: 0.643
ppc: 0.626
network: 0.620
semantic: 0.577
performance: 0.572
kernel: 0.532
architecture: 0.520
mistranslation: 0.513
debug: 0.439
user-level: 0.410
TCG: 0.410
files: 0.410
arm: 0.406
register: 0.405
vnc: 0.392
i386: 0.381
risc-v: 0.369
boot: 0.362
PID: 0.336
x86: 0.321
permissions: 0.301
VMM: 0.290
hypervisor: 0.268
peripherals: 0.267
virtual: 0.221
KVM: 0.196
assembly: 0.109

bad iteraction between -daemonize and -nographic

 $ qemu -daemonize -nographic
 $ _

After this, the terminal is switched to some weird mode, not processing cr/lf, and not showing the characters being typed (it is fixable by using `stty sane').

Something is seriously wrong here: When -daemonize is given, qemu not touch tty parameters at all.

Thanks,

/mjt

FWIW, it has been present at least since version 0.10 of qemu, and still present in current 1.1 version.

According to the Debian bug tracker, this has been fixed with this upstream commit:
http://git.qemu.org/?p=qemu.git;a=commit;h=ab51b1d568e02c80b1abf9016bda3a86dc1db389
... so let's close this now.