On Sun, Jul 06, 2008 at 01:13:05AM +0300, Hasso Tepper wrote:
> Many thanks for hint. It turned out exactly the problem you already fixed
> once in security/nss. 2.0.0.15 introduced security/nss-fips directory
> with same problem.
>
> http://leaf.dragonflybsd.org/~hasso/pkgsrc-www-firefox.patch
On Sat, July 5, 2008 6:33 pm, Matthew Dillon wrote:
>
> So... who would like the job?
>
> I know we have several people with access to pkgbox already, and I'll
> add Hasso too (if you want the added burden :-)). What we need now is
> someone to be the person in-charge of packages f
:..
:> I've seen this in the past and it was always a linker error.
:> Check if there's some new conditional somewhere missing the DragonFly
:> case.
:
:Many thanks for hint. It turned out exactly the problem you already fixed
:once in security/nss. 2.0.0.15 introduced security/nss-fips directory
Joerg Sonnenberger wrote:
> On Thu, Jul 03, 2008 at 04:27:40PM +0300, Hasso Tepper wrote:
> > Recent Firefox (security) update to 2.0.0.15 in pkgsrc broke it for
> > DragonFly:
>
> I've seen this in the past and it was always a linker error.
> Check if there's some new conditional somewhere missing
:Well, internal hard disks under 100G are getting hard to find, so I doubt
:this is going to be a huge issue. It should be documented.
:
:There's also the possibility that things could be mounted under /, instead
:of multiple partitions.
Yah. I think what we are moving towards is more of a
On Sat, July 5, 2008 2:27 pm, Matthew Dillon wrote:
> The main issue for /tmp/ and /var is going to be size. HAMMER is
> not really designed for tiny partitions. They would have to be
> mounted 'nohistory' at a minimum and probably also have to be
reblocked > daily, depending on h
Placed a small bounty on http://wiki.dragonflybsd.org/index.cgi/Code_Bounties,
since I got a new machine and I'd need RAID1 ... any takers?
--
Regards,
Rumko
The main issue for /tmp/ and /var is going to be size. HAMMER is
not really designed for tiny partitions. They would have to be mounted
'nohistory' at a minimum and probably also have to be reblocked daily,
depending on how full they get.
The absolute bare minimum would be on
:> Well, AFAIK HAMMER is still not production material, so it's just a
:> matter of time before it can be used (since from what I read Matt
:> intends to make HAMMER usable till the next release, it should be
:> usable for anything but / when 2.0 comes out?).
:
:It's obvious that bugs can occur, a
On Sat, 05 Jul 2008 19:50:47 +0200
Rumko <[EMAIL PROTECTED]> wrote:
> Well, AFAIK HAMMER is still not production material, so it's just a
> matter of time before it can be used (since from what I read Matt
> intends to make HAMMER usable till the next release, it should be
> usable for anything bu
Gergo Szakal wrote:
> On Sat, 05 Jul 2008 16:18:39 +0200
> Rumko <[EMAIL PROTECTED]> wrote:
>
>> Hmm, I also encountered 'Bad file descriptor' message (with a ls -la
>> couldn't see the socket, but csh's autocomplete did find it and that
>> message was displayed whenever I tried to rm it), but th
:Gergo Szakal wrote:
:
:> I have noticed a strange problem on HAMMER: when UNIX domain sockets
:> are created on my HAMMER partition, they cannot be accessed ('Socket
:> operation on non-socket'), when I try to remove them, I get a 'Bad file
:> descriptor' message. After a reboot they disappear. W
On Sat, 05 Jul 2008 16:18:39 +0200
Rumko <[EMAIL PROTECTED]> wrote:
> Hmm, I also encountered 'Bad file descriptor' message (with a ls -la
> couldn't see the socket, but csh's autocomplete did find it and that
> message was displayed whenever I tried to rm it), but thought I
> messed up the machin
Gergo Szakal wrote:
> I have noticed a strange problem on HAMMER: when UNIX domain sockets
> are created on my HAMMER partition, they cannot be accessed ('Socket
> operation on non-socket'), when I try to remove them, I get a 'Bad file
> descriptor' message. After a reboot they disappear. What is
I have noticed a strange problem on HAMMER: when UNIX domain sockets
are created on my HAMMER partition, they cannot be accessed ('Socket
operation on non-socket'), when I try to remove them, I get a 'Bad file
descriptor' message. After a reboot they disappear. What is the reason
for this?
--
Ger
Ferruccio Zamuner wrote:
Hasso Tepper wrote:
/scratch/www/firefox/work/mozilla/security/nss/cmd/shlibsign/DragonFly1.13_OPT.OBJ/shlibsign
-v -i /scratch/www/firefox/work/mozilla/dist/lib/libsoftokn3.so
Bus error (core dumped)
make[3]: ***
[/scratch/www/firefox/work/mozilla/dist/lib/libsoftokn
On Thu, Jul 03, 2008 at 04:27:40PM +0300, Hasso Tepper wrote:
> Recent Firefox (security) update to 2.0.0.15 in pkgsrc broke it for
> DragonFly:
I've seen this in the past and it was always a linker error.
Check if there's some new conditional somewhere missing the DragonFly
case.
Did I say I ha
Hasso Tepper wrote:
/scratch/www/firefox/work/mozilla/security/nss/cmd/shlibsign/DragonFly1.13_OPT.OBJ/shlibsign
-v -i /scratch/www/firefox/work/mozilla/dist/lib/libsoftokn3.so
Bus error (core dumped)
make[3]: *** [/scratch/www/firefox/work/mozilla/dist/lib/libsoftokn3.chk]
Error 138
Looking
18 matches
Mail list logo
