be modified to use the multiboot
specification. I think that's possible.
Miltiboot does support passing modules. The actual linkage (like
symbol lookups etc) should be done in the kernel, because this is
kernel-dependent. But I think this is already the case, isn't it?
(Sorry, no time to
On Sun, Mar 17, 2002 at 01:07:36PM -0500, [EMAIL PROTECTED] wrote:
> On Sun, Mar 17, 2002 at 06:55:26PM +0100, Jeroen Dekkers wrote:
> > This is certainly true. It's a wishlist item, it would be nice if all
> > free kernels would use multiboot. I've heard that grub wi
On Sun, Mar 17, 2002 at 12:16:46PM -0500, [EMAIL PROTECTED] wrote:
> On Sun, Mar 17, 2002 at 05:25:12PM +0100, Jeroen Dekkers wrote:
> > I think the best way is to make multiboot BSD kernel images. The
> > multiboot standard is very flexible, it's included in the grub
> >
x27;t be all
> that hard - it's just one kernel and one primary filesystem (FFS) to make
> sure function, to support the vast majority of BSD-land.
I think the best way is to make multiboot BSD kernel images. The
multiboot standard is very flexible, it's included in the grub
d
erty in one package is wrong because they have a different
upstream. I think the right way is having a libc package which depends
on the libiberty package.
Jeroen Dekkers
--
Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED]
Debian GNU supporter - http://www.debian.org http
uild-Depend: foo [all-i386]
Build-Depend: bar [linux-all]
And then then the way to solve the X problems:
Build-Depend: kernel-headers-2.4 [linux-all]
Note that kernel-headers should be linux-headers actually. :))
Kernel-headers should be some meta package depending on the right
headers for the right pla
lled. A lot of kernel-specific things are already fixed
because we want them to compile on Debian GNU/Hurd. But the Hurd also
uses glibc, I expect really much trouble with that. Most people just
don't know how to write portable or don't care about it. I don't know
if I'm the
commended
(we've the translator interface for that). We have other ways of
handling network.
The ifconfig program comes from the GNU inetutils packages and is
written portable as far as you can write an ifconfig program
portable. IIRC it's able to emulate semantics of other if
tuff should still be uploaded to non-US. People
living in the US should not upload those files to a non-US server.
Jeroen Dekkers
--
Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED]
Debian GNU supporter - http://www.debian.org http://www.gnu.org
IRC: [EMAIL PROTECTED]
pgpD4O
> > dpkg-shlibdeps. If it works we could put more pressure on the dpkg
> > maintainers.
>
> I'll give it a try sometime after I get python working. However, unless it
> doesn't use ldd, it probably won't work either.
It uses objdump, so it should wo
ve problems with the current
dpkg-shlibdeps. If it works we could put more pressure on the dpkg
maintainers.
Jeroen Dekkers
--
Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED]
Debian GNU supporter - http://www.debian.org http://www.gnu.org
IRC: [EMAIL PROTECTED]
pgpIYo3LTQK54.pgp
Description: PGP signature
x27;t get it
right. They have to check it anyhow if you compile them on *BSD
instead of Debian GNU/*BSD. Most of the time portability is a better
thing than some dirty hacks.
Jeroen Dekkers
--
Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED]
Debian GNU supporter - http://www.debian.org http://www.gnu.org
IRC: [EMAIL PROTECTED]
pgpUvCjf6ENML.pgp
Description: PGP signature
<[EMAIL PROTECTED]>
>
> Gelezen in de Debian Packaging Manual:
Maybe you should change this to "Read in the Debian Packaging manual"
for all people who don't speak Dutch. :)
Jeroen Dekkers
--
Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED]
Debian GNU supporter - http://www.debian.org http://www.gnu.org
IRC: [EMAIL PROTECTED]
pgpFSgGXXMHtE.pgp
Description: PGP signature
e are doing here. We might as well say so.
>
> Please don't say "we". I personally feel like I am sometimes forced to use
> GPL'd projects. (This is getting off-topic for this list, but I'd be glad
> to expand on this.)
I think you use GPL'd software,
On Fri, Jan 18, 2002 at 11:52:58AM -0800, Jeremy C. Reed wrote:
> On Fri, 18 Jan 2002, Jeroen Dekkers wrote:
>
> > Apart from that a lot ofthings come from GNU and they they deserve
> > credit, there is also another reason. It's spreading the words of
> > freedom
On Fri, Jan 18, 2002 at 11:48:59AM -0800, Jeremy C. Reed wrote:
> On Fri, 18 Jan 2002, Jeroen Dekkers wrote:
>
> > On Thu, Jan 17, 2002 at 12:08:00AM +, Matthew Garrett wrote:
> > > I've now uploaded the web page to http://debian-bsd.sf.net and am
>
> >
be for GNU/NetBSD, but at the same
> time I have no desire whatsoever for us to end up alienated from the
> NetBSD people who have provided such useful advice so far. Comments?
Reading other mails on the list the NetBSD people don't have much
problems with it.
Jeroen Dekkers
--
Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED]
Debian GNU supporter - http://www.debian.org http://www.gnu.org
IRC: [EMAIL PROTECTED]
pgpxuOhz6xtUX.pgp
Description: PGP signature
get the *BSD folks
> screaming bloody murder due to further forking.
Forking looks useless to me. I don't know how incompatible the
different BSDs are, but if we can hide it in the C library I don't
think it will be a really big problem.
Jeroen Dekkers
--
Jabber supporter - http://www.jab
everyone else think?
I think we should do it the way it's currently done in Debian for
now. If we want to use CVS, we should set it up Debian-wide. I like
the idea of using CVS for Debian source packages.
Jeroen Dekkers
--
Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED]
Debi
27;t know what's going on at
sourceforgetit, I suggest you read:
http://www.fsfeurope.org/news/article2001-10-20-01.en.html
Jeroen Dekkers
--
Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED]
Debian GNU supporter - http://www.debian.org http://www.gnu.org
20 matches
Mail list logo
