summaryrefslogtreecommitdiffstats
path: root/lib/libdisk/rules.c
Commit message (Collapse)AuthorAgeFilesLines
* Make libdisk WARNS=4 clean.kuriyama2004-03-301-4/+4
| | | | Glanced by: jhb
* Change libdisk and sysinstall to use d_addr_t rather than u_long for diskjhb2004-03-161-19/+20
| | | | | | | | | | | | | | | | addresses. For arch's with 64-bit longs, this is a nop, but for i386 this allows sysinstall to properly handle disks and filesystems > 1 TB. Changes from the original patch include: - Use d_addr_t rather than inventing a blkcnt type based on int64_t. - Use strtoimax() rather than strtoull() to parse d_addr_t's from config files. - Use intmax_t casts and %jd rather than %llu to printf d_addr_t values. Tested on: i386 Tested by: kuriyama Submitted by: julian MFC after: 1 month
* Turn Track_Aligned(), Prev_Track_Aligned(), Next_Track_Aligned(),marcel2003-11-021-7/+22
| | | | | | Cyl_Aligned(), Prev_Cyl_Aligned() and Next_Cyl_Aligned() into tautologies on ia64. GPT removes all notion of tracks, heads and sectors per track, so there are no alignment considerations.
* Teach libdisk that AMD64 works just like i386peter2003-04-301-0/+1
|
* Fix a compiler warning.phk2003-04-231-0/+2
| | | | Submitted by: David Leimbach <leimy2k@mac.com>
* Libdisk does not need to include <sys/diskslice.h> any more.phk2003-04-041-1/+0
| | | | | | | | | Move the remaining bits of <sys/diskslice.h> to <i386/include/bootinfo.h> Move i386/pc98 specific bits from <sys/reboot.h> to <i386/include/bootinfo.h> as well. Adjust includes in sys/boot accordingly.
* Fixed style(9)nyan2002-11-151-16/+27
|
* Restore to pc98 support.nyan2002-10-311-5/+12
|
* Since make release is toast anyway, add wood to the pyre:phk2002-10-291-9/+12
| | | | | | | | | | | | | | This significantly rewamps libdisks discovery of existing disk layout. Please send me reports if this does not work as expected on i386 or sparc64 platforms. I need to sort out alpha, pc98 and ia64 (in that order) before testing on those platforms make a lot of sense. Belived to work for: i386 sparc64 Unknown state: pc98 alpha ia64
* Swing the weed-whacker around libdisk:phk2002-10-221-57/+21
| | | | | | | | | Constify some things. Staticize some things. Remove some unused things. Prototype some things. Don't install a gazillion man-pages links. Drop support for ON-TRACK disk-manager.
* Fix to support pc98.nyan2002-10-081-0/+4
|
* Split MBR and PC98 on-disk sliceformats out from disklabel.h, step 1:phk2002-10-011-0/+1
| | | | | | | | | | | | | | | | Peter had repocopied sys/disklabel.h to sys/diskpc98.h and sys/diskmbr.h. These two new copies are still intact copies of disklabel.h and therefore protected by #ifndef _SYS_DISKLABEL_H_ so #including them in programs which already include <sys.disklabel.h> is currently a no-op. This commit adds a number of such #includes. Once I have verified that I have fixed all the places which need fixing, I will commit the updated versions of the three #include files. Sponsored by: DARPA & NAI Labs.
* Modernize my email address.phk2002-03-251-1/+1
|
* Add __FBSDID()s to libdiskdillon2001-09-301-3/+3
|
* Add spaces around operators.obrien2001-04-011-29/+29
| | | | | It's OK, the Project and afford them now -- they aren't as expensive as they used to be.
* Libraries should _never_ call exit() themselves (or its alternate spellingobrien2001-03-181-1/+0
| | | | | | | | | | | `err()'). libdisk does! and additionally libdisk gets confused on Alpha disks with foreign disklabels, throws up its hands and exits. This is the cause of the "going no where without my init" install bug on the Alpha. So now on the Alpha, rather than call err(), we print the error string and continue processing. Submitted by: jkh
* - Allow support for MBR boot loaders that are longer than one sector. Asjhb2000-07-121-25/+1
| | | | | | with fdisk, ensure that they are a multiple of the sector size in length. - Axe all the 1024 cylinder checks as they are no longer relevant with the fixed bootstrap.
* Changes for PC-98.kato2000-03-291-0/+28
|
* Catch up to the fact that block devices are toast.jkh1999-12-151-1/+0
| | | | | | | | Teach about the afd driver. Teach new char dev for ad driver. Make ownerships correct. Submitted by: jhb
* Remove BAD144 supportphk1999-11-271-30/+0
|
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* Revert $FreeBSD$ to $Id$peter1997-02-221-1/+1
|
* Make the long-awaited change from $Id$ to $FreeBSD$jkh1997-01-141-1/+1
| | | | | | | | This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long. Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
* Merge RELENG_2_0_5 into HEADrgrimes1995-06-111-11/+78
|
* Remove trailing whitespace.rgrimes1995-05-301-5/+5
|
* Add check for rootfs > cyl 1024.phk1995-05-081-2/+6
|
* General sanitation and cleanup. Killed the "reserved" type, it wasn't.phk1995-05-061-6/+2
|
* If in Create_Chunk we (type==freebsd && (flags&CHUNK_ALIGN)), then we willphk1995-05-051-3/+3
| | | | align this chunk properly. Have at it Jordan...
* Make the partitions names even more sensiblephk1995-05-041-16/+29
| | | | CheckRules sets the CHUNK_ALIGN & CHUNK_PAST_1024 flags.
* Make the target for tst01 more sensible.phk1995-05-031-4/+16
| | | | | | | | | | | | | Remove bogus targets. Allocate partition letters as follows: lowest offset "flags & CHUNK_IS_ROOT" gets 'a', lowest offset "subtype==FS_SWAP" gets 'b' the rest is allocated in offset order from this sequence "defghab". This will generally make sense. Added rules to complain if more than one CHUNK_IS_ROOT or more than one FS_SWAP per FreeBSD chunk. Set CHUNK_IS_ROOT on the 'a' partition in Open_Disk. Run Fixup_Names in Open_Disk.
* Now we do writes too.phk1995-04-301-11/+65
|
* Names are assigned when chunks are created.phk1995-04-291-1/+49
| | | | Rules for only one fat & one extended in MBR.
* Next Iteration, getting better.phk1995-04-291-3/+30
| | | | | | | | Made an All_FreeBSD() function. Added a cmd-line interface (lowest rank) to the tst01 program. The tst01 program is harmless (worst it can do is coredump), but it is instructive to run, you can see what the slice-code things of your disk...
* Sanitize and explain a little bit... Implement the first rules...phk1995-04-291-0/+95
OpenPOWER on IntegriCloud