7;m interested in info about this bug.
>
I can see the link, but it also points to an other page with more info:
http://article.gmane.org/gmane.network.freeswan.user/7627
Regards,
Eric
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integ
Hello Cedric,
Thanks for your fix! I will commit it to CVS and also update the current
ipsec package in CVS.
Regards,
Eric
>
>
> Issuing the command "ipsec auto --status" while there is no tunnel will
> trigger a uclibc only bug in openswan (it blindly mallocs 0 bytes)
&
he correct subdirectories) and do (from within
the created directory):
tar -c * | gzip -9 > example.lwp
> Regards,
> Andrea Fino
>
Regards,
Eric
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make
the headers are updated. Just to be sure.
There are probably quicker methods.
Eric
___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
tle, you could go ahead and try without
rebuilding buildenv. I usely take the save road and rebuild buildenv.
Eric
___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
gt;Does this imply I have to rebuild the buildenv if the kernel version
>changes?
>
It's the savest thing todo, but the headers don't change that often.
Eric
___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
Hello Erich,
>How are the dependencies handled by buildtool? Is this done by flag files?
>
In sources.cfg. If some source depends on an other source, it's
listed in sources.cfg as a dependency.
Eric
___
leaf-devel mailing list
Hello Erich,
>> This is the latest patch known to me and has support for ppp-2.4.2+
>
>What about the patches at http://mppe-mppc.alphacron.de/
AFAIK the MPPE part is the same and the MPPC part could give legal
problems if we packa
kernel with the strongswan source tools itself,
build the buildenv and after that build strongswan.
Eric
___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
ter code to the kernel.
The rationale behind this is grouping of functionality so individual
patches can be updated without creating a complete new patch. They are
also included in different moments in time.
> Thanks for your patience
>
>
> Erich
>
Eric
__
p of "linux" and "kernel" is unlike other packages split in two
different setups because the linux source/headers are needed for buildenv
and buildenv is needed for building the kernel.
Eric
___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
oot to replace buildtool, converting
>apps makefiles to buildroot is quite straight forward
>
Buildtool is based on buildroot, with some changes needed for package
creation and some other things which are practical for us. I don't
see a real need to replace it, it's
ckup.
When you use something like a .local file you can list the etc/
hostapd directory and all files will be taken into account.
How do you handle this?
Eric
___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
b
>
> where the target needs to exist in /etc/fstab and be mounted in /media/*.
> If no target is specifide, lbu will try to use $LBU_MEDIA.
>
That is also possible in the config system from Bering-uClibc, it's not
that difficult to parse LRPKGPATH and ask which device to backup to
elf.
>
Good suggestion didn't thought about that, but PKGPATH can be a list and
the first entry can still be a CDROM. I'm not sure if it's obvious if
backup fails that the above entry can be the fault, if a note is added in
the leaf.cfg file that the first entry is the backup devi
is now).
>
> Why not having a separate variable? What if first device in PKGPATH is a
> cdrom?
>
In most cases (HD/Flash/Floppy) the first device is the backup device,
having a seperate variable would only introduce redundancy. But I was
thinking about adding a menu entry where an user c
guess the
> only sane thing would be to write a C app for that. Maybe later...
>
> --
> Natanael Copa
>
>
Eric
>
>
>
> ___
> leaf-devel mailing list leaf-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/l
he
config file. I was more thinking about something that updates the new
config file with changes from the old one, which is probably almost
impossible ;)
> --
> Natanael Copa
>
Eric
>
>
>
>
> ___
> leaf-devel mailing list leaf-de
y config files should live
>>> in /etc.
>>>
>> Agree, but see my comments above. Ofcourse having a .local file in the
>> package doesn't "hurt". It's a question of the configtools to use it or
>> not.
>
> I actually think I have it myself. I think apk_add will look if there is
> a CONFFILES listing, which is exactly the same thing as .local in lrp. If
> its there, use it, if its not look up APK_LBUDIRS. So you can override it.
>
It's not exactly the same, but close. Some files like ssh-keys, password
and group shadow files and so on are not config files and not listed in a
conf entry but should be backupped.
>
> After a second thought, its probably not working. when comparing against
> "current", the files outside etc/ will show up as deleted. I can remove
> that code. Need to think mor on that.
>
> [ a few lines cutted ]
>
>
>> Thanks for your comments and pointers! Looking forward for more
>> cooperation.
>
> Thanks to you too! ;-)
>
>
> --
> Natanael Copa
>
>
Eric
>
___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
or "patch" when a
config file is changed a bit upstream. For example placement of config
items in a different order or added optional items in a config file can
break the "patch".
> Regards,
> Cedric
>
Regards,
Eric
___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
el.org/alpine/v1.1/iso/alpine-1.1.3_beta3-060610-i386.iso
> http://tanael.org/alpine/v1.1/iso/alpine-1.1.3_beta3-060610-i386.iso.sha1
>
>
> (warning! it's 137 MB on a 2Mbit shdsl line)
>
>
> You can also try run it from USB:
>
>
> http://tanael.org/alpine/v1.1/usbdrive/
>
>
> Since the documetation is not so good, here are the basics to get
> started:
>
>
> To list available packages:
> apk_fetch -lv
>
> To install a package:
> apk_add
>
> To configure the basics (incl networking):
> setup-alpine
>
> Try add/delete/modify anything in /etc, then run:
> lbu -h lbu status lbu commit -h lbu commit -n floppy
>
Thanks for your comments and pointers! Looking forward for more cooperation.
>
> --
> Natanael Copa
>
Eric
>
>
___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
ore
improvents can be made in the "userspace" configtools and the packages
itself don't need to be touched anymore.
It's also possible to create some sort of offline config/update tool
instead of doing it all on the host itself.
>
> Regards,
> Cedric
>
Reagrds,
Eric
___
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
but my wife's PC was crapping out.
>
>
> When hostapd attempts to configure the atheros card to do CCMP, we get a
> bad ioctl error. The CM9 should support this:
>
Did you load the aes kernel module? According to the madwifi page an error
like this can o
Hello Cedric,
> Hi Eric,
>
> That sounds great.
> Is there already something we can test/hack ?
I have an image I can send you this evening (UTC) when I'm home. If there
is more demand, maybe it can be placed somewhere on the LEAF site.
> Any idea on the timeline, espe
Hello Paul,
> Hi Eric and friends,
>
>
> I stumbled across a couple of problems today while playing with hostapd.
>
>
> It looks like WPA2 (psk) is not working properly with my Atheros CM9
> card. I did a cursory visual inspection of the source and it looks like
> th
removed
Because this system creates some package incompatibility (no more .list
files) we plan to do this with an uClibc upgrade (which isn't backwards
compatible also). The changes are not very drastic and relative easy
implemented in buildtool
Hello Cedric,
Ok, I wil fix it and also create the necessary changes for linux (nat and
klips patch).
P.s.1
I have added the ifenslave package to sources.cfg
P.s.2
Did you test the ifupdown "manual" patch? If it works ok I will commit it.
Thanks,
Eric
> Hi Eric,
>
>
> It
Hello Cedric,
Looks good.
A small note:
I see a small difference in "manual.in":
current patch:
+awk ' /ipsec[0-9]+:/ {
your pach:
+ awk ' /^ipsec[0-9]+:/ {
I guess it's a typo in the original patch, but I'm not sure.
Regards,
Eric
Hello Cedric,
Thanks! I will take a look.
Regards,
Eric
>Hi,
>
>
>openswan 2.4.4 has a bug preventing ipsec module from being removed
>after some traffic flowed in a tunnel (module refcount decreasing for
>each packet !)
>
>I have an update package (2.4.5) working
tyle/place to add mknod of devices?
>
Most common devices are defined in the initrd package, but devices
specific to a package can be defined in an init.d script.
>Regards,
>Andrea Fino
>
Regards,
Eric
___
leaf-devel mailing list
leaf-devel@lists
olution would be to make a separate sources.cfg for contrib packages
which is sourced in the 'master' sources.cfg and which is writable by
contributors. But that isn't implemented yet.
>
>Regards,
>Cedric
>
Regards,
Eric
___
m to lib/modules/2.4.xx/net ?
>
lib/modules/2.4.xx/extra should be fine, The key to add them to the
modules tarball is to add it to sources.cfg (the "kmodules" entry). I will
take care of that and also add your xl2tpd package to that fi
er, because there would be some educational
> effect also.
>
Agree with that, an other advantage of describing it and providing a
system is that you don't have to maintain a seperate image.
> cheers
>
> Erich
>
Eric
>
>
>
>
> ___
Hi Mike,
>> The Bering-uClibc team will make a snapshot of the current tree and put
>> the sources in a tarball in the File release area.
>
> Eric,
> Please reconsider this decision. Tagging the release in cvs is easier.
>
> http://ximbiot.com/cvs/manual/cvs-1.11.21/cv
tly 2.4.1, so if you build buildenv you would have version
2.4.1.
The Bering-uClibc team will make a snapshot of the current tree and put
the sources in a tarball in the File release area.
> thanks
>
> Erich
>
Eric
---
Using Tomc
>
You are right, what I meant is that the initrd(_*) is installed with /
var/lib/lrpkg/initrd.* names at early bootstage.
>cheers
>
>Erich
Eric
---
Using Tomcat but need to do more? Need to support web services, security?
Get stu
be added.
Note that the initrd is installed by linuxrc, not lrpkg -I.
Eric
>Hi folks
>
>I have multiple LEAF systems on the same hardware booting from the same
>medium. This requires the use of different initrd files, I call the
>secondary file initrd2.lrp. In the backup menu th
What can cause such a thing?
>
I don't know... buildpacket should fail if some files aren't found. Usualy
I just do a "buildpacket.pl --package=initrd" and it works fine. Did you
also try without the "-all"?
Any warning in the buildtoollog or on the screen?
>
> Re
Hello Mike,
>> It looks like the "bash" problem is the only corruption in the
>> Bering-uClibc CVS space. Can you ask SF to remove the bogus file, I have
>> a copy of the file.
>
> Eric,
> The SF staff just removed the corrupted file. You're free to impor
src/config/webconf/
ok
leaf/bin/packages/uclibc-0.9/20
this one is also ok
Eric
>
> On Tue, 2006-04-11 at 13:17, Mike Noyes wrote:
>
>> The following is a list of directories that differ:
>>
>>
>> leaf/bin/bering-uclibc/ leaf/bin/config/webconf/ leaf/bin/lince/
&
archive is available.
Eric
>> Mike Noyes wrote:
>>
>>> It seems our cvs repository is in a corrupt state. I had a
>>> conversation with SF staff member burley this morning:
>>
>> The file giving the error is bogus. It is a 1 byte long *DIRECTORY*
>>
>> device
>>
>> Can you report this to the sourceforge team?
>>
>
> Eric,
> I brought this issue to their attention, and they are looking into it.
> I'll keep you informed on their progress. Thank you for reporting the
> problem.
>
ch
>> device
>>
>> Can you report this to the sourceforge team?
>>
>
> Eric,
> I brought this issue to their attention, and they are looking into it.
> I'll keep you informed on their progress. Thank you for reporting the
> problem.
>
Thanks for your effor
Hello Jorn,
> Hello all;
>
>
>
>>> We currently have three ideas how to provide an USB image:
>>> 1) a complete image which can be dd'ed to /dev/sda and is ready to
>>> boot; this is what Jorn, Eric and Andrea tried to build and provided
>>> f
The image will show up in a few hours (when viewCVS is updated) at:
http://cvs.sourceforge.net/viewcvs.py/leaf/devel/espakman/
Eric
> To answer Eric's question, here's Andrea's tips "adjusted" slightly:
>
>
> Andrea Fino wrote:
>
>> I did a working usb
Hello David,
Thanks for the help! I will try your suggestion and also create an image.
Eric
> To answer Eric's question, here's Andrea's tips "adjusted" slightly:
>
>
> Andrea Fino wrote:
>
>> I did a working usb this way:
>>
>>
>&g
r.
>
> and you could add "Easier usb handling" to your
> why-upgrade-to-2.6-kernel-list.
>
> ;)
>
:)))
Eric
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications in
ck with that, the user only has to change
syslinux.cfg/leaf.cfg if the device is something else than sda. Some
smarter option can always be added later.
> Jorn
Eric
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of N
B which still contains
all packages without the individual modules and redundant packages. The
image scripts can take care of that.
I think we can focus on putting all packages on the stick, they can easy
be "enabled" by setting them in leaf.cfg or removed by the user when not
needed. An
and/or ask someway as
> parameter.
>
I think something like 64Mbyte should do, it's more than enough for all
packages.
> Regards,
> Andrea Fino
>
>
> --
> Andrea Fino 8-) - "Sistemi su misura di qualita' industriale"
> "
Hello Jorn,
The same question to you, do you know a way to create an image without
using a physical USB stick?
Eric
> Mike & All,
>
>
> Here's the URL
> http://www.ccl-network.com/leaf/
>
>
> Best regards
> Jørn
>
>
> -Original Message---
sdos"
syst_size=12M
log_size=4M
Also a question, is it possible to create an image without using a
physical device? This way it's easier to use the image create scripts the
Bering-uClibc team uses to create floppy and CD images to also be used for
USB images.
Eric
> Hi,
>
>
Hello Jorn,
> Eric & All,
>
>
>>> I don't know what happens if you backup
>>> initrd (if initrd_usb.lrp or initrd.lrp is back-upped). Didn't you
>>> change leaf.cfg and can you still backup packages to the usb-stick?
> Good point. Did not test
- plugged in and did a: dd of=/dev/sda
> if=stick.img
>
> It took 40 sec "burn" it
> Then I pluged in into the ASUS box again.
> And it worked like a charm
>
>
> I have Gzip'ed the image and it now take around 20Mb. Is there a place
> where
rd between
> binary versions.
>
> We could auto-generate config /etc files from a database. This is what
> we did in the JUNOS UI (my baby). Later on, we decided that XML constructs
> work very nicely for this kind of thing, but the overhead and bloat are
> hi
stalls
> them in /usr/share/shorewall/).
> That
> approach would also work for a LEAF distribution that wasn't constrained
> by 1.68MB media capacity.
>
Sorry Tom, I choose a wrong example ;-)
But there are other programs which don't keep backwar
ses.
An other, maybe less important problem is that when you "try" a package
the config file of that package will polute the local repository of config
files (after you delete the package, the config files are still present)
while with config inside a package this won't be the case.
team) definitly need your
help with reviewing the apkg format and tools and looking forward to share
experience.
Eric
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mob
p
and rename it to initrd.lrp)
-Change leaf.cfg and syslinux.cfg to use the correct boot device
So there is no need to maintain an image, just an extra target (next to
CD-ROM and Floppy) is needed.
Eric
---
This SF.Net email is sponsored b
Thanks, I will take a look at the Racoon 2.4 backport.
Eric
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime develope
Thanks, I will take a look at the Racoon 2.4 backport.
Eric
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime develope
Thanks, I will take a look at the Racoon 2.4 backport.
Eric
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime develope
. There is a 2.4
backport of the 2.6 ipsec stack available.
Eric
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime develo
Hi Mike,
>> I don't agree with you, there is still room for evolution.
>
>Eric,
>Where?
>
>2.6 kernel <-- discouraged
>initramfs <-- discouraged
>Alpine <-- discouraged
>
>I can go on, but I think you see my point.
>
I
Hello Mike,
>> I am wondering if may be used an ext2 filesystem. With that and
>> extlinux (present in the last syslinux distribution) I think it's easy
>> to boot from usb (and others).
>>
>> Regards,
>> Andrea
>>
>
> Eric,
> Does Andre
can be
installed on any USB key.
EricS
> On Thu, 2006-03-16 at 02:43, Eric Spakman wrote:
>
>> Can someone take a look at this link and create some script around it
>> which creates an USB-flash image?
>>
>>> Makebootfat Bootable FAT Disk Creation
>>
Hello all,
Can someone take a look at this link and create some script around it
which creates an USB-flash image?
Eric
>
> Eric,
> Does document help?
>
>
> Makebootfat Bootable FAT Disk Creation
> 7 Multi Standard USB Booting
> http://advancemame.sourceforge.
VS space for creation
of CD and floppy images, that one has to be changed ;-)
>
> (A tarball of src/config/webconf is maintained in
> src/bering-uclibc/apps/webconf. It was done to help out buildtool.)
>
> The process to build the tarball is documented in cvs:
> src/
Hello Mike,
Looks promising! Thanks for searching.
Eric
>>>>
>>> This would be the same sort of setup we would use:
>>> fdisk the pendrive, make it bootable, copy the contents, syslinux it
>>> and edit some files. This is no image setup and that's whe
Hello Mike,
Thanks!
Who is going to put the available lwp packages in leaf/bin/config/webconf?
Just a question.
If the directory is populated we have to change our image script to
download the webconf packages from this location (this is a reminder for
myself ;).
Eric
> On Wed, 2006-03-15
appy to keep my devel tree. Doesn't matter either way. :-)
>
> What's NOT in leaf/src/config/webconf is all of the .lwp's (anything
> beyond webconf.lrp / webconf.lwp)Perhaps there's a place for them in
> the same spot.
>
leaf/bin/config/webconf?
Mike, do you a
interfaces (like Nathan
explained this doesn't have to be for Bering-uClibc exclusively) or
creating images for specific functionality (using the big repository of
available packages).
It's just what you define as "evolution".
We are not the dominant branch because we gained enou
e same sort of setup we would use:
fdisk the pendrive, make it bootable, copy the contents, syslinux it and
edit some files. This is no image setup and that's where I'm looking
after.
>
> --
> Mike Noyes
> http://sourceforge.net/
Hello Mike,
>>> I agree. I thought this content was incorporated into the
>>> bering-uclibc documentation. :-(
>>
>> It is:
>> http://leaf.sourceforge.net/doc/guide/buc-devel.html
>> http://leaf.sourceforge.net/doc/guide/buc-install.html
or LEAF
>
> I agree. I thought this content was incorporated into the bering-uclibc
> documentation. :-(
>
It is:
http://leaf.sourceforge.net/doc/guide/buc-devel.html
http://leaf.sourceforge.net/doc/guide/buc-install.html
Eric
---
Hello Mike,
> Eric,
> Continuing the CD image is worthwhile, but not the floppy. Replace the
> floppy image with the new usb-hdd flash drive image.
>
I don't see any reason to replace the floppy image, it's still a nice
format for older hardware and like I said before it doe
ve seen leaf mentioned in a magazine or
>nominated for an award. :-(
>
Yes that's a pity
>--
>Mike Noyes
>http://sourceforge.net/users/mhnoyes/
>SF.net Projects: leaf, phpwebsite, phpwebsite-comm, sitedocs
>
Eric
>
>
>--
cengines WRAP this is USB support, not USB-boot support :-)
But anyway, why would you boot from an USB stick with a soekris or WRAP
when you have a CF card available in the enclosure?
Eric
---
This SF.Net email is sponsored by xPML, a grou
Hello Mike
>
> Eric,
> Is the Bering-uClibc team producing images specifically targeted at
> usb-hdd flash drives?
>
No specific images, but we provide different kind of initrd_xxx packages
which can be used for floppy, hdd, usb (flash) or cd use. So just choosing
the right ini
Hello Mike,
Bering-uClibc supports booting from USB flash devices with initrd_usb.
Eric
> Everyone,
> It looks like USB-HDD flash drives are the new floppy. Bios support for
> usb-hdd boot has been around for approximately three years now. The price
> of flash drives isn't
Hello Tom,
It is available but not on the base (floppy) image, adding it will
increase the imagsize with almost 60 kbyte (mawk.lrp + libm.lrp). This
would also mean that Bering(-uClibc) won't fit on a floppy anymore...
Eric
> Can I assume the presence of the 'awk' utility on L
dev environment is quite shakey thanks to compiler
> mismatches. I was hoping to not do any more leaf development until the
> upgrade to gcc-4.0 and a recent uclibc.
>
The next major version (3.0) of Bering-uClibc will have an uClibc update.
An update to gcc-4.0 is a different story, I on
Hello Paul,
>>> I thought, at one point, the ipp2p matching code was part of the
>>> build kernel, but it doesn't appear as if it's in the 2.4.32 kernel
>>> you compiled.
>>
>> No, the ipp2p code isn't in yet. I know Arne created some setups for
>> it, but we still need to discuss a bit about what
Paul,
> Eric,
>
>
> I thought, at one point, the ipp2p matching code was part of the build
> kernel, but it doesn't appear as if it's in the 2.4.32 kernel you compiled.
No, the ipp2p code isn't in yet. I know Arne created some setups for it,
but we still need to
Hello Erich,
The warnings are normal (AFAIK) and sourceforge is having problems, I'm
also not able to check out sources now.
Eric
> Hi Folks
>
>
> I started a new attempt at buildtool, still no luck. Here is the log...
>
>
> buildtool::Download::download:file ke
to use $(AUTOCONF) instead (or define it globally).
If everything works ok, I will update it in CVS.
Eric
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engin
irectory.
Can you point where you found the reference to the host include files?
Eric
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
sear
Hi Paul,
>
>Something needs to be done so that the pthread include files are used
>instead of the system include files.
>
Can you be a little more specific? If the system include files are used, it's
probably hardcoded somewhere in the upnpd sources. Is that wha
ut I can't find that reference... Can you be more specific in
which part it tries to execute it?
Eric
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search e
Hi Paul,
> (6)
>
>
> upnpd package needs to depend upon lpthread in sources.conf
>
That's not needed, the pthread library is build as part of uClibc and
already build in the buildenv setup. The pthread setup is only to create
the package, it's no d
but buildenv's gcc gets build by the host gcc and there are
currently some problems if the host compiler is gcc-4.0.
In your case it looks like binutils is corrupted somehow, I rebuilded
buildenv 2 days ago and didn't had a problem with compiling it.
Eric
-
>
> We can only help you if you provide a much more clear view of what you
> are trying to do.
>
>
> Luis Correia
> Bering uClibc Team Member
>
And in addition, for which version of LEAF?
Eric Spakman
Bering uClibc Team Member
-
Hello Mike,
Currently we are not working on it, but we do look at kernel development
ofcourse.
Kernel 2.6 is much bigger than 2.4, it needs a lot of changes in the base
packages (to make full use of the functions) and it has no real benefit for
leaf now.
Eric Spakman
>Is anyone working
No real reason, only a technical one. The webconf package is maintained by
Nathan and in his CVS space, the script that builds the packages page only
looks at our 'own' Bering-uClibc CVS space. But the latest webconf package is
included in Bering-uClibc beta4.
Eric Spakman
>Is t
need some specific
empty directories to be available where temporary data is saved. Some examples
are shorewall, openswan, root, dnsmasq, dhcpd, So those (empty)
directories should be saved in the package, or created somehow.
Eric Spakman
cf /dest/package.apk *
>
>I cannot really see how not supporting excludes is a problem.
>
>Also note that there is no /var/lib/apkdb/package.list file inside the
>package. It is created during installation from the contents of the tar
>package.
>
>--
>Natanael Copa
>
Er
this system
backwards compatible with the existing packages?
Eric Spakman
>I would like to tell you guys that im working on a package manager that
>you might be interested in.
>
>It is very similar to apkg (the Nathan Angelacos modified one) and is
>actually originally d
7;t think
this link will prevent sources from being crosscompiled (it points to
the crosscompiled loader).
AFAIK it has nothing to do with target-compiled executables on the
host system.
Eric
> Warning:The symlink from /lib/ld-uClibc.so.0 -->
> /home/pst/LEAF/buildtool/staging/lib
ebconf, both haserl and
>pwcrypt are bound to webconf, you don't have an alternative. But you
>can use an other httpd if you like (f.e. the ssl linked mhttpds or
>even apache ;-))
>
>
>True, but it might be _big_ :-))
LOL, ok thttpd.
>cheers
>Erich
Eric
---
, you don't have an alternative. But you
can use an other httpd if you like (f.e. the ssl linked mhttpds or
even apache ;-))
Eric
>Erich,
>
>Webconf is ported to buildtool, so making packages for a new uClibc
>version would only mean run buildtool to automatically recompil
101 - 200 of 473 matches
Mail list logo
