Re: [patch] installer ufs initrd support (how to create a ufs filesystem as a normal user?)
Luca Favatella dixit: >This patch adds ufs initrd support. 4.2FFS, UFS2, or both? I would very much like to be able to install Debian GNU/kFreeBSD on 4.2FFS (aka UFS1) filesystems, not just UFS2. bye, //mirabilos -- “It is inappropriate to require that a time represented as seconds since the Epoch precisely represent the number of seconds between the referenced time and the Epoch.” -- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2 -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [patch] installer ufs initrd support (how to create a ufs filesystem as a normal user?)
On 07/07/2009, Thorsten Glaser wrote:
> Luca Favatella dixit:
>
>>This patch adds ufs initrd support.
>
> 4.2FFS, UFS2, or both?
In the attached second version of the patch, I explicated UFS2.
UFS1 works too, but I chose to introduce only UFS2.
(I'll use UFS2 in kfreebsd-i386 commit in next days/weeks.
I think it is not good to add a feature and not use it.)
See http://svn.debian.org/viewsvn/d-i?view=rev&revision=59261
> I would very much like to be able to install Debian GNU/kFreeBSD on
> 4.2FFS (aka UFS1) filesystems, not just UFS2.
This patch is only about initrd (a.k.a. mfsroot).
I think (I didn't test) you can already install Debian GNU/kFreeBSD on
UFS1 with current hacked sysinstall
(http://glibc-bsd.alioth.debian.org/doc/installing.html).
> bye,
> //mirabilos
Thanks,
Luca Favatella
Index: build/Makefile
===
--- build/Makefile (.../trunk/installer) (revision 59247)
+++ build/Makefile (.../branches/d-i/kfreebsd/installer) (revision 59256)
@@ -119,6 +119,18 @@
(cd $(TREE) && find . | cpio --quiet -o -H newc) >
endef
+define mkfs.ufs2
+ fs=`mktemp` ; \
+ dd if=/dev/zero of=$${fs} bs=1M count=16 ; \
+ md=`mdconfig -a -t vnode -f $${fs}` ; \
+ mkfs.ufs -O2 /dev/$${md} ; \
+ mnt=`mktemp -d` ; mount /dev/$${md} $${mnt} ; \
+ cp -a $(TREE)/* $${mnt}/ ; \
+ umount $${mnt} ; rmdir $${mnt} ; \
+ mdconfig -d -u $${md} ; \
+ mv $${fs}
+endef
+
define e2fsck
e2fsck -fy
endef
@@ -610,6 +622,10 @@
jffs2) \
$(mkjffs2) $(TEMP_INITRD); \
;; \
+ ufs2) \
+ $(mkfs.ufs2) $(TEMP)/initrd; \
+ gzip -v9f $(TEMP)/initrd; \
+ ;; \
*) \
echo "Unsupported filesystem type"; \
exit 1 ;; \
Index: debian/changelog
===
--- debian/changelog (.../trunk/installer) (revision 59247)
+++ debian/changelog (.../branches/d-i/kfreebsd/installer) (revision 59256)
@@ -76,6 +76,7 @@
[ Luca Favatella ]
* Handle libc0.1 (GNU/kFreeBSD) and libc0.3 (GNU/Hurd) as libc6/libc6.1.
+ * Add ufs2 initrd support. Thanks to Robert Millan.
-- Frans Pop Sat, 13 Jun 2009 16:35:46 +0200
KDE / GNOME status
Heya, so, once hal is fixed (which should hopefully happen soon), one should get xorg-server. Once qt4-x11 (fixed package is in NEW), one can consider kde4libs. There's still avahi on the way, as you can see one the attached picture, showing Build-Depends (B-D:), Depends (D:), and binary/source relationships (from:). A possible way of getting rid of the cycle is to do a manual build of pygtk by installing gnome-icon-theme without its librsvg2-common dependency (so that has to be a manual build so that the dependency can be broken). Once that done, avahi, gnome-vfs, libgsf, and librsvg build properly one after each other. I also rebuilt pygtk after having installed librsvg2-common, and no differences showed up when comparing against the previously built binaries. That should help get kde4libs (build is currently running), thus some parts of KDE. ISTR (but that's still to be verified) that librsvg was on the list of the blockers for libgnome* packages, so some bits of GNOME should become available too as a consequence. That's it for now. Mraw, KiBi. <>
Bug#535243: marked as done (kfreebsd-kernel-headers: Wrong type in ?)
Your message dated Tue, 7 Jul 2009 21:44:53 +0200 (CEST)
with message-id
and subject line fixed
has caused the Debian Bug report #535243,
regarding kfreebsd-kernel-headers: Wrong type in ?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
535243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kfreebsd-kernel-headers
Version: 0.34
Severity: important
Tags: patch
Heya,
while working on hal on kfreebsd-i386, I've stumbled upon the following:
./hald/freebsd/hf-pci.c includes , but the latter uses
uint64_t for the pci_bar_io structure, instead of u_intNN_t for other
structures, and the compiler fails on that token.
Maybe a -D (I tried __USE_BSD) or another include is missing? Or one
could just use the attached patch (I copied the path from the
000_bruno_haible.diff patch, I didn't install the whole sources)?
Mraw,
KiBi.
--- src/sys/sys/pciio.h
+++ src/sys/sys/pciio.h
@@ -113,8 +113,8 @@
struct pcisel pbi_sel; /* device to operate on */
int pbi_reg; /* starting address of BAR */
int pbi_enabled; /* decoding enabled */
- uint64_t pbi_base; /* current value of BAR */
- uint64_t pbi_length; /* length of BAR */
+ u_int64_t pbi_base; /* current value of BAR */
+ u_int64_t pbi_length; /* length of BAR */
};
#define PCIOCGETCONF _IOWR('p', 5, struct pci_conf_io)
--- End Message ---
--- Begin Message ---
There should be "Closes: #535243" instead of "Closes #535243"
kfreebsd-kernel-headers (0.35) unstable; urgency=low
.
[ Petr Salinger ]
* add #include into
Closes #535243.
.
[ Cyril Brulebois ]
* Add myself to Uploaders.
* Bump Standards-Version to 3.8.2 (no changes).
--- End Message ---
needs for GNU/kFreeBSD
Hi all, it looks like we are currently waiting for hal. What will be the next blocker besides [1-3] ? I believe that reschedule of all failed packages will give us some more successful builds. Would be possible to put somewhere files like used to be http://unstable.buildd.net/buildd/kfreebsd-i386-all.txt http://unstable.buildd.net/buildd/kfreebsd-amd64-all.txt Cheers Petr [1] http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=kfreebsd;users=glibc-bsd-de...@lists.alioth.debian.org;pri0=pending:pending,forwarded,pending-fixed,fixed;ttl0=Outstanding,Forwarded,Pending%20Upload,Fixed%20in%20NMU;pri1=pending%3dpending%2btag%3dwontfix,pending%3dpending%2btag%3dmoreinfo,pending%3dpending%2btag%3dpatch,pending%3dpending%2btag%3dconfirmed,pending%3dpending;ttl1=Will%20Not%20Fix,More%20information%20needed,Patch%20Available,Confirmed,Unclassified;ord1=2,3,4,1,0,5 [2] http://bugs.debian.org/cgi-bin/pkgreport.cgi?submitter=dschep...@gmail.com [3] http://bugs.debian.org/cgi-bin/pkgreport.cgi?submitter=lu...@lucas-nussbaum.net -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
