Bug#464938: d-i on i386 with 16 MiB RAM (using swap)

[trosos]

Using bzip2 doesn't save RAM, but it saves space on the root floppy.
(If you add all three ide modules on it, you would normally (using gzip)
end up with image bigger than 1.44 MB).

Therefore I suggest to compress initrd on the root floppy with bzip2,
which claims for using a bzip2 decompressor on the boot floppy,
insted of the gzip one.


Best regards,
Tomas Tintera

  Original message 
 From: Joey Hess [EMAIL PROTECTED]
 Date: 10.2.2008 03:20:01

 Tomas Tintera wrote:
  1. We need
   ide/ide-core.ko,
   ide/ide-disk.ko and
   ide/ide-generic.ko
  modules on 2nd (root) floppy (in initrd) in order to get
  HDDs work. The space for it can be made by bzipping 2nd
  floppy's initrd instead of gzipping it. Also the following
  lines must be added to modules.dep in initrd on the 2nd
  floppy:
 
 This, and adding a swapon option make sense (in the limited situations
 where the system can be preconfigured with a swap partition).
 
  2. We need to use a bzip2 decompressor on 1st (boot) floppy
  instead of zcat. We can use micro-bunzip
  (http://www.landley.net/code/micro-bunzip.c (version 3.0,
  which is smaller than 4.1)), with the patch in
  the attachment, statically linked with klibc.
 
 You lost me here. How does using bzip2 save memory? The floppy image
 is decompressed into a ramdisk.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#451773: xatitv doesn't hide window manager decorations when in fullscreen mode

[trosos]

Package: gatos
Version: 0.0.5-16

If I switch xatitv into the fullscreen mode (pressing '*'), it only maximizes 
the window, without hiding the window manager decorations.

---
xatitv(1) says:
 Keypad * or Double-Click - Toggle fullscreen Mode.

-- 
Tomas trosos Tintera



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#413648: console-screen.sh doesn't update console 6, updates only 1-5

[trosos]

Hi,

since its report on 6 March 2007, there have been no
progress on the bug. So I think it may got forgotten.

Could the patch be applied, please - or could I do
something to get it applied?


Regards,
Tomas Trosos Tintera



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#414789: 'Switch Page Direction' wrongly automatically selected when right-click on right of page

[trosos]

Hi, I also encountered that bug in iceweasel 2.0.0.6-0etch1.

The described behavior occures to me only if the click is
right enough on the screen, so that the cursor will not be
on the place of the bottom left corner of the context menu,
but on the right from it.

Tomas Trosos Tintera


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#439846: framebuffer script badly interprets modedb boot parameter

[trosos]

Package: initramfs-tools
Version: 0.85h

The init-top/framebuffer script should use mode_option (according
to the documentation) as a fb module parameter for setting the video
mode, instead of mode.

The Linux documentation uses mode_option argument:

 $ zcat /usr/share/doc/linux-doc-2.6.18/Documentation/fb/modedb.txt.gz
 ...
 Valid mode specifiers (mode_option argument):
 
 xresxyres[M][R][-bpp][@refresh][i][m]
 name[-bpp][@refresh]
 ...

But the framebuffer script uses mode argument:

 $ cat /usr/share/initramfs-tools/scripts/init-top/framebuffer
 ...
 # When the options are used with modules, they need to be space-separated
 ...
 #   modevalue   - mode=modevalue
 ...

As a consequence, if I specify eg. video=aty128fb:1024x768-16 as
a kernel boot parameter, the framebuffer script uses a mode module
parameter (instead of mode_option), which will not be understood by
the module.

I tried aty128fb and nvidiafb modules, and both accept video_mode
option, and don't accept mode option. With other fb modules I would
expect similar behavior.

One can use video=foofb:mode_option=1024x768... as a workaround,
but the documented behavior will not work.

If no fb driver uses the mode parameter, I suggest to change the
init-top/framebuffer script in order to use the mode_option
parameter.

---

$ uname -r
2.6.18


Tomas trosos Tintera


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]