#### Archived

This topic is now archived and is closed to further replies.

# The Suse Monster!

This topic is 6243 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

## Recommended Posts

Hi,

After reading the thread "Distro...? (NO FLAMING)" I decided to install SuSe Linux. I got SuSe 6.3 Eval (30 day) from a friend and deleted my existing Redhat 6.2 partition.

Now to my amazement this thing (suse) finds my existing partitions of 1.2GB and 100 MB (swap) too small even for a minimal installation. (As far as i remember these used to be quite big for my redhat!)

How much does this disk hog requires? I tried reading some readme.txt files in the docu folder but they’re all in german language For now, I think i can spare say about a more of 500 MB using FIPS but since i’m not sure whether this will work even then; i’ll ask someone whose already done a minimum installation of this software

cyanide.

##### Share on other sites
I have suse(6.2 I think), and I have it doesn''t take up that much room. Manualy choose which pacakges you want...
www.laeuchli.com/jesse/

##### Share on other sites
quote:
Original post by laeuchli

Manualy choose which pacakges you want...
www.laeuchli.com/jesse/

I oughta have done that but it doesn''t gimme a chance. As i boot the CD, i get a message in german that reads something like "weird start" and then after the lang. screens two more option "Automatic and Guided Tour" both of ''em leading to that same partition screen. After selecting the two partitions 1.2GB and 100MB, i get that error "Not nuff space for even minimal setup" from suse.
BTW i just split my "e:" drive into two and now SuSe tells me that "the partitions ain''t adjacent..."

cyanide.

##### Share on other sites
Are you using the graphical installation tool (YAST 2)? If so, I''d recommend trying the non-graphical one (YAST 1). It works very well and AFAIK doesn''t spew out such a trash. I''ve been using SuSE for years now and never had any problems.

---
ls -lR|rm -rf /
(Best compression everywhere. Kids, don''''t try this as root.)

##### Share on other sites
I''ll second that... Kick out YAST 2 and create a Yast 1 bootdisk. (should be in /disks directory on CD)

Yast 2 seems to mess everything up, whatever I do, I can''t get it to work how I want it.

- JQ
PWC Software
"And I thought I was insane..." -friend of mine after I said something

##### Share on other sites
aha both of you seem to be very correct. It *is* YAST 2 and now i''ve messed up all my hard drive. Desperate to try it out, I created a partition say about 3GB (and messed up my exisiting dos partions with Partition Magic). But still i think its worth it!

The only one problem that bugs me now is that the SuSe partion now pops up as "F:" drive in windows and "Extended Partition" in fdisk (with no logical drives defined ofcourse!). I''m afraid that programs like NDD might damage or ruin it when they run after invalid shutdown... Is there anyway to hide the partition from DOS?

cyanide.
P.S>I remember when i installed Red Hat there was no such problemo...

##### Share on other sites
Hmm, very strange... and you''re SURE you formatted it as ext2? I can''t really believe that... maybe you should do a fdisk /mbr - but be careful with the damn thing!

- JQ
PWC Software
"And I thought I was insane..." -friend of mine after I said something

##### Share on other sites
It seems you''re at some very bad point in the life of your system. If it''s possible, back up all your important data and rebuild...

##### Share on other sites
i think the installer automatically formatted the partition.
As far as i remember i created this new partition with partion magin before installing, but neway it had to have disappeared like after the red hat setup. BTW there was no disk druid (or something that may sound similar) during the suse setup.

here is a image of what fdisk shows of my part:
I think the last one is linux

it doesn''t have a drive letter here but it pops out as f: in windows...

cyanide.

##### Share on other sites
And when you''re looking at the contents of that extended partition? There should be at least two non-dos partitions (linux and linux-swap), both without an assigned letter... I''d say you should post that screen, too for completeness'' sake.

##### Share on other sites
are u talking about these two images?, anyway it pretty amazing in itself what fdisk is upto...

cyanide.

Edited by - cyanide on January 15, 2001 12:07:54 PM

##### Share on other sites

Hi,

just ran suse and this is what i
got on using fdisk and then ''p'':

bash-2.03# fdisk

Using /dev/hda as default device!

The number of cylinders for this disk is set to 1245.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., LILO)

2) booting and partitioning software from other OSs

(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/hda: 255 heads, 63 sectors, 1245 cylinders

Units = cylinders of 16065 * 512 bytes

Device Boot Start End Blocks Id System

/dev/hda1 * 1 152 1220908+ b Win95 FAT32

/dev/hda2 153 600 3598560 b Win95 FAT32

/dev/hda3 601 800 1606500 b Win95 FAT32

/dev/hda4 801 1245 3574462+ 5 Extended

/dev/hda5 801 803 24066 83 Linux

/dev/hda6 804 820 136521 82 Linux swap

/dev/hda7 821 1245 3413781 83 Linux

Command (m for help):

Also windows is now showing in
the performance section that "Drive D: using MS-DOS
compatibility mode file system.

What if delete /dev/hda4, does
that mean dev/hda5, dev/hda6, dev/hda7 also go along with it? I''m
beginning to smell a rat in my partition table.

cyanide.

##### Share on other sites
As it looks, Windoze should show 3 drives (C, D and E, corresponding to /dev/hda[123] which is in itself not good since the outdated way WinDOS uses to manage harddisks is very much optimized for just one primary partition (/dev/hda1 in your case). If I were in that situation, I''d say you should try repartitioning the harddisk the following way:

/dev/hda1: Primary partition, used for Windoze and as bootdisk.
/dev/hda4: Extended partition containing at least:
/dev/hda5: Linux partition
/dev/hda6: Linux swap
and then any additional partitions you might need. It doesn''t matter in what order you put the partitions inside the extended, but try to keep Linux before cylinder 1024 (reason below).

The best thing would be to create/change the Win and extended partitions using FDISK or any DOS/Win program since Linux might try to use an addressing scheme which Win can''t handle (happened on my sys, but otherwise rarely happens... but you never know). Afterwards create the Linux partitions using Linux fdisk.

As a general rule: There''s a maximum of 4 primary partitions or 3 primary and 1 extended partition. If you want to boot WinDOS, install it to and boot it from a primary and put any other logical drives for it inside an extended. Linux can boot from almost anywhere you might put it (there can be problems when trying to do that from a partition which ranges past cylinder 1024), Win can''t. Otherwise, everything''s up to you.