My boot partition is 1.5 gb
Id like to resize it to 512mb…Though can it be done in yast partitioner ?
Yes you can configure the Linux filesystem anyway you like. When you discuss boot size are you really talking the root system or just a boot partition. Typically, you only need a 50 - 100MB boot partition, but to do anything serious with Linux you need 1GB minimum as root which includes: (/bin /etc /home /root /usr /tmp /var /boot). /home and /usr need quite a lot of space as these are your user programs and your data. If you try and limit Linux to 512MB total, a special build will be needed and you will lose any hope of a GUI, or even running apps to do more than a quick test of operation.
Adding to techwiz03’s post. You mean you have a separate /boot partition? You might give better information about your setup by posting the output of
fdisk -l
and
cat /etc/fstab
**Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000aaec1
Device Boot Start End Blocks Id System
/dev/sda1 1 262 2104483+ 82 Linux swap / Solaris
/dev/sda2 263 2873 20972857+ 83 Linux
/dev/sda3 2874 9531 53480385 83 Linux
/dev/sda4 * 9532 9729 1590435 83 Linux
Disk /dev/hdc: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000dfac4
Device Boot Start End Blocks Id System
/dev/hdc1 1 12162 97691233+ 83 Linux
/dev/hdc2 12163 24321 97667167+ 83 Linux
/dev/disk/by-id/ata-ST380817AS_5MR2YDPP-part1 swap swap defaults 0 0
/dev/disk/by-id/ata-ST380817AS_5MR2YDPP-part2 / reiserfs acl,user_xattr 1 1
/dev/disk/by-id/ata-ST380817AS_5MR2YDPP-part4 /boot reiserfs acl,user_xattr 1 2
/dev/disk/by-id/ata-ST380817AS_5MR2YDPP-part3 /home reiserfs acl,user_xattr 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
/dev/disk/by-id/ata-WDC_WD2000JB-00GVA0_WD-WCAL81765163-part1 /data1 reiserfs acl,user_xattr 1 2
/dev/disk/by-id/ata-WDC_WD2000JB-00GVA0_WD-WCAL81765163-part2 /data2 reiserfs acl,user_xattr 1 2
**
** And from yast
Device: /dev/sda1
Size: 2.01 GB
Encrypted: No
Device Path: pci-0000:00:1f.2-scsi-0:0:0:0-part1
Device ID 1: ata-ST380817AS_5MR2YDPP-part1
Device ID 2: scsi-SATA_ST380817AS_5MR2YDPP-part1
FS Id: 0x82 Linux swap
File System:
File System: Swap
Mount Point: swap
Label:
Device: /dev/sda2
Size: 20.00 GB
Encrypted: No
Device Path: pci-0000:00:1f.2-scsi-0:0:0:0-part2
Device ID 1: ata-ST380817AS_5MR2YDPP-part2
Device ID 2: scsi-SATA_ST380817AS_5MR2YDPP-part2
FS Id: 0x83 Linux native
File System:
File System: Reiser
Mount Point: /
Label:
Device: /dev/sda3
Size: 51.00 GB
Encrypted: No
Device Path: pci-0000:00:1f.2-scsi-0:0:0:0-part3
Device ID 1: ata-ST380817AS_5MR2YDPP-part3
Device ID 2: scsi-SATA_ST380817AS_5MR2YDPP-part3
FS Id: 0x83 Linux native
File System:
File System: Reiser
Mount Point: /home
Label:
Device: /dev/sda4
Size: 1.52 GB
Encrypted: No
Device Path: pci-0000:00:1f.2-scsi-0:0:0:0-part4
Device ID 1: ata-ST380817AS_5MR2YDPP-part4
Device ID 2: scsi-SATA_ST380817AS_5MR2YDPP-part4
FS Id: 0x83 Linux native
File System:
File System: Reiser
Mount Point: /boot
Label: **
As you see Id like to resize it to more proper boot that is. But inside yast it wont resize it unless its unmounted and it prevents that. I know I could with a gparted BUT I dont wanna muck the boot. First with out finding out how etc
ventiman wrote:
> As you see Id like to resize it to more proper boot that is. But inside
> yast it wont resize it unless its unmounted and it prevents that. I know
> I could with a gparted BUT I dont wanna muck the boot. First with out
> finding out how etc
right, it is unsafe and unwise to attempt to resize a mounted and
therefore in use partition…(because, for examplem what would you
think would happen if in the midst of a resize process the system
decided it had to write new system data to the partition being resized?)
which means you MUST resize it without booting from it…which means
boot another way (like say a live cd) and use a capable resizing tool
(say gparted) resident on the active system’s source (the live cd)…
thinking out loud only: i’m not at all sure if it is overly wise to
take the chance of murdering your system (and loosing data) in order
to move only 1 GB of disk space to somewhere else (/home maybe)…
if it were me i’d investigate other options…(like maybe a new,
larger drive…external maybe…)
to begin with i would NOT run gparted on any disk with data (music,
photos, movies, emails, school work, etc etc etc) i wanted to keep
unless i had a full backup of all that data stored safely on a
different machine/medium…and, had tested the archived copy to ensure
it was readable and intact…anything else is just begging for disaster…
anyway, most folks have moved on from Reiser
ymmv
–
DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio
Thanks for the output. Please next time use CODE instead of B. Bold does notr make it better readable where CODE retains the lay-out of the computer output.
I support DenverD’s advice. Personaly I would even go further and aim for a complete redesign (sometimes a good cleaning is needed):
. no separete /boot;
. all file systems to ext4 (when you are on 11.2, I think you did not tell us);
Most easy way to do this (without going into detail, but we could help you with your planning) is backup of your personal data (/home), make a copy of all inside /etc (lways handy when you reconfigure your new system to check what it was earlier) and then do a reinstall. A Swap partition about the same you have now (you may want to reconsider the size, but then we need to know what you have now and the memory size). A root (/) partition about 20 GB (again look at what you have now and how far it is fiilled,* df -h *helps here). The rest for /home.
When the system is running to satid=sfaction again you can convert the two partitions on hdc by copying them, recreating an ext4 on the partition and copy back.
It looks like a day of hard work, but then your are again fixed for a few years 
This is fairly a fresh install.
The auto yast made the boot that size. I guess I didnt catch it when installing suse. Ive used gparted many a times on systems at work n never a issue. Though granted those where windowz systems. I didnt pick ext4 on the advice of linux geek robb tracy he tended to prefer Reiser.
The HDD is bout 80gig with a couple of other 100gb drives.
Ram is a gig.
A separate boot is not a normal option, you must select it. Nor is it needed. Boot normally resides in the root partition.
True how you don’t need a separate boot partition in normal use, older hardware under older Linux required a boot below cylinder 1023 for the bios to be able to boot Linux. Reiser standard also states to always define a separate boot partition. Personally, I have found the best performance of using multi-OS’s to have a separate boot with 50MB available for each OS’s boot code files. Thusly, 1 /boot mounted in root / as /boot in each OS may have the boot images for openSUSE 11.1 32bit, 11.1 64bit, 11.2 32bit, 11.2 64bit, 11.3 32bit, and 11.3 64bit == 6*50MB = 300MB.
ventiman wrote:
> I didnt pick ext4 on the advice of linux geek robb tracy he tended
> to prefer Reiser.
i wonder if Robb’s 2007 study guide was written in 2005/6 when
Reiserfs was the “new big thing” or this week when ext4 beats the
pants off of Reiserfs (which is not getting a lot of work these days
as developer Mr Reiser is in prison for murdering his wife)…
as i said, most folks have moved on from Reiser…
–
DenverD (Linux Counter 282315)
CAVEAT: http://is.gd/bpoMD
posted via NNTP w/TBird 2.0.0.23 | KDE 3.5.7 | openSUSE 10.3
2.6.22.19-0.4-default SMP i686
AMD Athlon 1 GB RAM | GeForce FX 5500 | ASRock K8Upgrade-760GX |
CMedia 9761 AC’97 Audio