Bug#394963: Don't install grub/lilo on MBR

2007-06-27 Thread Grzegorz Szyszło
Some servers don't accept strange MBR modifications. Sometimes it is 
compilations server+some systems (xp for example).


I suggest:
1. clear first disk sectors (boot some linux live, dd if=/dev/zero 
of=/dev/some_disk_device usually hda or sda)
2. install XP with this own partitions. DON'T USE DYNAMIC PARTITION! 
(feature in windows server systems that allow create software 
raidmirror for windows)
3. after installation, boot XP and create all partitions for linux. you 
shuldn't initiate or format ths partition.
4. begin installation. select EXPERT mode, help is on the screen. don't 
create partitions, only change partition types, assign to format and 
assign to mountpoints. make sure, linux boot partition is active, and 
windows is inactive. Change this attributes if nesessary.
4a. usually after partition modification  before reboot, i run fdisk 
(not cfdisk  other, only the simplest fdisk),  look to partition 
types. If it is nesessary, i correct it to properly partition types, 
this is usually linux  linux swap.
4b. you should't create swap partition. you can use swap as file over 
linux partition. t degrade a bit performance, but make partition table 
simpler. sometimes it is very recommended, specially when you use only 
one hard drive.
5. when you install grub or lilo, DON'T USE MBR that is default 
behavior. Use linux boot partition for grub or lilo. You can simply 
specify linux boot partition, /dev/hdaX  (X number partition) or 
(hd0,X). Be sure, (hd0,X) X begin from 0, but /dev/hdaX X begin from 1.
6. continue installation process. For time saving, use as simplest 
installation as possible. Select only base text install, without 
graphics, window enviroments (withiut gnome, kde  others) and without 
additional servers. You can install it later. In aptitute it is tasks, 
last directory in package menu.

7. after installation be sure, that linux boot properly.
8. add to lilo or grub windows boot menu. you have help in 
/etc/lilo.conf (other file system) or /boot/grub/ some file, but I don't 
remember what do exactly.

9. after grub config modification do nothing, after lilo.conf type lilo
10. try again boot linux.
11. try boot XP. This should boot, whithout active flag over his partition.
12. look out after active flag modification. when windows change this 
flag, under disk management tools (under windows) correct active flag to 
linux partition that should be presented as unknown  isn't assigned to 
any disk drive letter.


This method guard against geometry incompatibilities,  unsupported MBR 
modfications made by lilo, grub or other boot managers like this.


--
Grzegorz Szyszło
Departament Informatyki
NOBLE Bank S.A.
Lublin, tel. (81)532-77-20 w.240 , kom.607-940-478



Bug#417673: This is Microsoft problem

2007-06-21 Thread Grzegorz Szyszło

vfat was introduced by Microsoft, with buggy implementation.
I tryed to test this fs. When I have written 4GB file
(exactly 4GB minus 1 byte! because this FS support only this in 
directory structure - 4 bytes file length), this was okay.
next i booted winxp and run disk check. this cause, all 4GB files was 
reduced to 0 (zero) bytes. But blocks in FAT are not released. Then I 
run checkdisk under win98. this repair files and rewrite size to 4GB 
minus 1 byte.

I think this is problem with windowsNT vfat support and based on it.
linux kernel should support winNT or different older win9x behavior.
It is strange, but winxp allow writing and other operations with 4GB 
(minus 1 byte) on vfat fs. I think it is internal fsck problem, but 
microsoft as usual says this is not a bug, this is FEATURE.
For protection this bug, I prefer ext2/ext3 ofer XP usung, or NTFS-ng3 
on linux. I think vfat is usable only for files to 2GB length (minus 1 
byte). Larger files cause problems.


--
Grzegorz Szyszło
Departament Informatyki
NOBLE Bank S.A.
Lublin, tel. (81)532-77-20 w.240 , kom.607-940-478



Bug#394963: installation: Problems with dual booting Dell D600

2007-01-12 Thread Grzegorz Szyszło

I think its problem with compatibility with windows and linux partman.
don't forget, windows server can use dynamic disc, that is not 
compatible with anything. desktop versions of windows can use this type

of partitions, after bit modification in 4 system files.

Second think, this can be problem with geometry interpretation. I have 
bad experiences when I partition disk with different tools from 
different systems. I suggest rather to create all needed partitions 
under windows,
then under debian installer only change types and re-format that 
partitions, and assign to mountpoints. It allways works me.


I notice, microsoft has problems with this own products. There are some
incompatibilities between windowsXP and windows9x partitioning tools.

--
Grzegorz Szyszło



Bug#406483: After base install computer hang

2007-01-11 Thread Grzegorz Szyszło
Package: installation-reports
Version: etch
Severity: critical

This report is about current (see email date) floppy installation.
I make 4 installation etch diskettes. All processess after flopy boot works ok, 
hard drive is detected properly,
partitioning, detect network ok, getting packages from network ok, preparing 
filesystems
and base installs ok. When is time to reboot after base install, i do it.
After boot system properly boot kernel and initrd, and  hang. Last kernel 
message is detect IDE devices
and CD drive. Then system wait for nothing. I can do alt+ctrl+del to reboot, 
and situation repeat again.
I tryed install, removed all proposed IDE drivers. This not solve my problem.

Installation with sarge/floppy works ok. after reboot system properly continue 
booting and load
processess to finalize install. After minimal floppy/net install, i can 
properly upgrade sarge to eth and continue
installation other packages.

With eth/floppy install I have other problems. I cant select pc-style keyboard, 
this process fails.
Next, I cant select lilo as bootloader. Only grub is selectable. In 
sarge/floppy I don't have that problems.
I allways select i686 kernel without SMP, to prevent SMP problems.

System specification:
Server Compaq ML370  (without G1,2,3 signature)
Two processors PentiumIII FSB 133MHz, first 933MHz and second 633MHz (for 
tests, i removed second processor)
Memory, two modules 128MB (summary 256MB) 133MHz with ECC
Compaq Smart Array 3200 Controller with useable for cache 56MB RAM (8MB uses 
controller firmware)
6 scsi hard drives 9GB 10k RPM, configured as one logical volume, presented to 
system as one physical drive
/dev/ida/c0d0  , that has standard parition table with nodes
/dev/ida/c0d0p1
/dev/ida/c0d0p2 etc...  this is suported by kernel module cpqarray.
network card supported by kernel module e100 .

Now I'm getting first weekly cd image of etch.
I'll try do install with this medium.

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-3-686
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)


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