cvsup, installer and booting

George Georgalis george at
Thu Aug 5 22:05:28 PDT 2004

On Wed, Aug 04, 2004 at 11:35:01AM -0400, Justin Sherrill wrote:
>On Tue, 3 Aug 2004 23:51:47 -0400, George Georgalis <george at xxxxxxxxx> wrote:
>> >
>> >
>> Thanks Sascha,
>> contrary to the doc, that file doesn't exist, but I am using
>> DragonFly-supfile
>> FreeBSD-doc-supfile
>> FreeBSD-ports-supfile
>> FreeBSD-standard-supfile
>> from /usr/share/examples/cvsup/ -- though it is not clear to me whether
>> I need FreeBSD-standard-supfile since I use DragonFly-supfile?
>'DragonFly-src-supfile' was only committed some 6 days ago, so if you
>haven't updated lately, it won't be there.  It's just like
>'DragonFly-supfile', except that the commented-out lines aren't
>commented out.  It'll get the most recent version of the source files,
>like "traditional" cvsup config files from FreeBSD.

oh, so DragonFly-supfile was and will remain the cvsup file for binary
packages? I was able to get a through a make worldinstall the other day,
will check next time I'm on that box if I have a DragonFly-src-supfile.

Just getting the basic install, I've got a number of problems I wouldn't
have expected:

I'm not sure exactly how the partition table below was created, I'm
running linux on hdbX; and w2000 on hda1

the installer could not use hda3 not enough space (???) but there was no
problem with hda2, how much overhead does UFS require?

Disk /dev/hda: 16 heads, 63 sectors, 38792 cylinders
Units = cylinders of 1008 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1             1     13181   6642846    b  Win95 FAT32
Partition 1 does not end on cylinder boundary:
     phys=(826, 254, 63) should be (826, 15, 63)
/dev/hda2         13181     27094   7012372+  a5  FreeBSD
Partition 2 does not end on cylinder boundary:
     phys=(675, 254, 63) should be (675, 15, 63)
/dev/hda3         27094     38792   5895855   a5  FreeBSD
Partition 3 does not end on cylinder boundary:
     phys=(385, 254, 63) should be (385, 15, 63)

running from hda2 I can't access my mail spool (via ssh) because
TERM=cons25 completely breaks mutt, that would appear a debian/mutt
issue because I did get a termcap in place with cons25 and mention
of FreeBSD; however if there is a way to fix it things would be much

My third problem today is I cannot build xorg (or anything else I
guess); due to running out of inodes.  Makes no sense to me, all I've
done is cvsup by the README, build bash3, and attempt to build xorg, I
ran script on the second attempt. there's nothing there but a
inodes problem...


// George

George Georgalis, Architect and administrator, Linux services. IXOYE  cell:646-331-2027  mailto:george at xxxxxxxxx
Key fingerprint = 5415 2738 61CF 6AE1 E9A7  9EF0 0186 503B 9831 1631

More information about the Kernel mailing list