freebsd-update upgrade -r 12.0-RC2
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 2 mirrors found.
Fetching metadata signature for 12.0-RC1 from update4.freebsd.org... done.
Fetching metadata index... done.
Fetching 3 metadata files... failed.
Seems like freebsd-upd
Steve Jobs :)
Finally, the greatest mistake is not reading the terrific FreeBSD handbook.
Best.
José Miguel Martínez Carrasco
---
http://www.jm2dev.com
http://identi.ca/jm2dev
http://twitter.com/jm2dev
___
freebsd-stable@f
er such a "time sharing system" and many people run
desktops and part-time servers, wouldn't it be desirable to have a periodic
job scheduling mechanism that would reliably run jobs when a given amount
of time (uptime or not) had passed?
Greetings,
Miguel Ramos
Lisboa
_
Dear all.
I have been trying to use portsnap update to update automatically the
ports tree in a server running release 6.2, but I always receive the
same message:
'Ports tree is already up to date'
I know this is not true because I have other freeBSD 6.2 machines with
newer ports. If I'm not
t reproduced here.
Maybe because my i386 is on 7.0, different compiler (although the amd64 is
still on RELENG_6).
Since you've rulled out everything else by building a static binary,
did you try using the new C99 functions in fenv.h related to the
floating-point environment?
Miguel Ramos
Lisb
tput.
All it takes is to move 268 to line 191, as I said before.
Of course, I don't think this is a critical or prioritary issue, not at all.
It was only fun, because I could look into it in a half hour.
But the kludge to solve the +1/-1 inconvenient is there and is ugly.
Greetings
Miguel
___
problematic line was introduced
6 years and 5 months ago by ru... Complete reference: src/bin/date.c Revision
1.32.2.4
Is ru around?
Who fills in a pr for this?
In summary, I think we should move line 268 to line 191 and erase the comment
on line 267 (mktime() is no one to decide, strptime
erying the media type that you're actually using, you
can use ifconfig media parameter.
The actual value that this parameter accepts are device dependent but
in practice quite standard like 100baseTX or 1000baseTX.
say, ifconfig | grep media:
Greetings,
Miguel
_
problematic line was introduced
6 years and 5 months ago by ru... Complete reference: src/bin/date.c Revision
1.32.2.4
Is ru around?
Who fills in a pr for this?
In summary, I think we should move line 268 to line 191 and erase the comment
on line 267 (mktime() is no one to decide, strptime
t.
I'm using /var/tmp for the image file, it is a hard disk.
The only other place where I've found this error message was on some ubuntu
mailing list, but the problem didn't seem to be the same.
Did anyone else ever experienced this? What can be wrong?
Thanks,
Miguel
-- .xsess
> From [EMAIL PROTECTED] Tue Oct 16 22:01:02 2007
>
> I should just be able to change the TAG in standard-supfile from 6_1 to 6_2,
> do a cvsup, and the builds etc to end up with 6.2-RELEASE right?
> yes? no?
Right. And back, you can change the tag back to 6_1... Or just RELENG_6 for
6-STABLE.
TP the ssys.* files
from the src directory of 6.2-RELEASE. Also fetch the install script,
install.sh,
on the same directory. Then run it :-)
Oh... about building... see the handbook, I'm sure to forget some step.
Miguel Ramos
___
freebsd-stable@fre
probably the author of the change will have to make a local workaround, such as
casting the u_quad_t to ull or #ifdef...
Miguel
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any
do it...
I hate to admit I let it happen... and I have been blaming myself for having
forgotten to disable password authentication on ssh to this machine... but maybe
something else is to blame.
Miguel Ramos,
Lisboa.
___
freebsd-stable@freebsd.org mail
every hardware/os change must imply some compatibility
testing.
Miguel
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5 15:37:08 shiva2 ntpd[385]: kernel time sync enabled 2001
someone suggested in the archives that disabling ipv6 could resolv the
problem, i already commented out options inet6 and recompiled the
kernel, i think the time is syncronized thoug.
what can i check?
s would
conflict with GDM's default configuration file.
If this is your case, try these two solutions:
1- change FirstVT to a diferent (higher) value
2- disable all VTs below 9 in /etc/ttys
I chose the second solution, because GDM can use more than one VT, enabling
several users of the s
e
the bug. I'm glad you could, no daemons on my machine...
I failed finding a way to reproduce it on other machines using mount_nfs -2,
so aditional assistance may be needed to the developers.
If the problem is reported and no further information is needed from me,
then I can
re you have *_enable="YES" in rc.conf for each script you want
to run?
Check rc.conf, rc.conf.local and the scripts, and if you're unable to find
out what's wrong, post them. It may also be useful if you tell us what
version of FreeBSD are you running.
Miguel
_
see any
> changes to rpc.lockd or nfs locking that were made since then.
Yes, I had also checked that earlier today. I don't know if I did something
that could have caused this... I'm almost sure it worked on 6.0 (although not
completely, because I only got this machine working w
this diskless machine, whereas the other problem, the one that occurs on
files that are already locked, happens on all machines.
If I keep using a common home directory for all machines, and keep using
lockd for that mount on that machine, then my only workaround is still to
go back to 6.0-RELEASE.
hat again. I had problems in the past with using the -L
option, gnome didn't run. Probably it was because it was a single / filesystem
mounted on boot and the option on fstab was ignored, I must try it again.
Miguel
___
freebsd-stable@freebsd.org
;t boot normally. The lock persists even though the file is not
"physically" locked on the server. I've tried stopping nfslocking on both
sides and removing both /var/db/statd.status. Is there any other persistent
storage for this?
Miguel
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
illable... (and should
not also the open system call in lockf be interruptible?)
So, I'm led to believe that beyond that issue with rpc.lockd, which,
I understand, is an unresolved problem, there is now another problem,
perhaps with pidfile.c...
Thank you for all your time on this issue. I'm s
ile
on the server with lockf. The description of the problem that I have becomes
increasingly similar to what is in pr bin/80something.
Greetings,
Miguel
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
7;t allow me to change the flag.
>
> Thanks anyways
> Nick
Is it really the securelevel? I had a similar problem on a diskless machine,
file flags couldn't be changed through NFS, so I had to remove the schg flags
on the server.
Miguel
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
couldn't kill cron and
the trace didn't grow either.
> Also while you're there, could you obtain a binary format tcpdump
> (tcpdump -w) instead? This may be parsed with tools like ethereal
> which will help with the analysis.
The tcpdump
l.pt/~mlsr/nfsx.dump
> > is the output of tcpdump -X -vvv host targa and udp port nfs
>
> Hmm, looks like you need -s 0 in addition to -X -vvv.
There. http://mega.ist.utl.pt/~mlsr/nfsxs.dump
I did just cron, instead of /etc/rc.
> From: Benjamin Sher <[EMAIL PROTECTED]>
> Subject: Re: Can't boot into setup to install FreeBSD 6
>
> Dear Miguel:
>
> Thank you so very much for trying to help. My answers below:
>
> > I think this is a bit off-topic on this list, but of course I'd li
sr.sbin/cron/cron.c, even
though there was a change at 2006/01/15, and this setup seemed to work before
January.
Another thing, I didn't start this thread, and I hope I'm not moving attention
away from the original post from Jun Kuriyama who was asking for help debugging
a documented
it off-list, since it is 69kB for -vvv
or 196kB for -X -vvv. Are you willing to look at the dump yourself? Anyone?
BTW, cron was left in an unkillable state, it couldn't be killed with SIGKILL.
In the meanwhile, I'll try to revert lib/libutil/pidfile.c to Jan 1st, which
> OK, thanks. Please try to obtain a tcpdump -vvv trace of the broken
> operation.
>
> Kris
Will you help me? I've been trying to use tcpdump -vvv on this but I get
either a lot of trash or nothing. Which ports should I dump?
So far I tried running on the server
# tcpdump -vvv 'host and (udp po
hines there's no
locking, there's no system hang and all that occurs is:
can't open or create /var/run/cron.pid: Operation not supported.
which is ok, of course, although it's a pitty that it can't work without
locking.
Miguel
___
0 +0900, Jun Kuriyama escreveu:
> At Mon, 06 Mar 2006 22:56:46 +,
> Miguel Ramos wrote:
> > I'm getting rpc.lockd related hangs on a single machine which is remote
> > booted. I'm goind to test you patch as soon as possible.
&g
> So, rpc.lockd _is_ needed on the client?
> What about the statement in rc.conf(5) then, claiming it was
> only started on servers?
Yes rpc.lockd and rpc.statd are needed on the client.
I suspect it's the statements in rc.conf(5) that are
> From [EMAIL PROTECTED] Fri Feb 24 09:48:08 2006
> Date: Fri, 24 Feb 2006 10:47:18 +0100
> From: [EMAIL PROTECTED]
> To: freebsd-stable@freebsd.org
> Subject: rip2 ospf: freebsd 6.0
>
> hi liste
>
> I'm looking for a dynamic routing (rip2, ospf) solution under freebsd
> 6.0. currently, I've alway
wn conclusions.
But don't do that unless you have good reason for it.
/ is a mainly read filesystem. It won't be under heavy write load.
On FreeBSD disks are commonly partitioned according to the usage profile,
not so common on Linux default installations. That's why separate /
> From: James Wyatt <[EMAIL PROTECTED]>
> Subject: Re: Ifconfig with rc.conf Broken
>
> Don't alias interfaces have to be added to the "network_interfaces=" line?
> I thought only "real" interfaces were autodetected...
I don't think this is the case. It shouldn't be...
But MC can test that using
.
>
> Uhh.. that's nasty.. :)
>
Not so nasty, since there's really no point in having more than one NIC
on the same segment. And the log message is justifiable.
Sorry for my intrusion.
Miguel
___
freebsd-stable@freebsd.org mailing li
Qua, 2006-02-15 às 21:11 +0100, Gianmarco Giovannelli escreveu:
> At 16.54 14/02/2006, Miguel Ramos wrote:
>
> >> Check with vmstat -i to see if you have an interrupt storm of
> >> some sort.
> >>
> >> David.
> >
> >It is on ir
Ter, 2006-02-14 às 13:16 +, David Malone escreveu:
> On Tue, Feb 14, 2006 at 01:00:40PM +0000, Miguel Ramos wrote:
> > Any sugestions?
>
> Check with vmstat -i to see if you have an interrupt storm of
> some sort.
>
> David.
Very good sugestion, than
could make any difference, or even in what
section of the kernel may the problem be.
Has anyone ever had a similar problem?
Any sugestions?
I was hopping to narrow the circumstances of this problem before
sending a pr.
Hi there,
On 11/13/05, Daniel O'Connor <[EMAIL PROTECTED]> wrote:
> On Mon, 14 Nov 2005 01:00, Miguel Mendez wrote:
> > > The first is that when you force it to capture audio (so mute and volume
> > > control work, or you can use mencoder) it does about 0.25 fps
look much nicer :)
Yes, it rocks. I've been using xawtv for a month and mplayer is so
much better. :)
Cheers,
--
Miguel Mendez <[EMAIL PROTECTED]>
http://energyhq.blogspot.com
PGP Key: 0xDC8514F1
___
freebsd-stable@
John-Mark Gurney wrote:
Miguel wrote this message on Tue, Nov 08, 2005 at 14:09 -0600:
I dont understand exactly why do you have to recompile, unless a new
future is needed, like SMP, isnt it?, what harm is doing those extra megs?
In the general case, no, you do not need to recompile
John-Mark Gurney wrote:
GENERIC is already so large, that if you want/need a smaller kernel,
you're going to rebuild anyways,
Since I care about that extra 2megs, I recompiled my own kernel,
And the real problem of a big kernel is
I dont understand exactly why do you have to recompile
re attractive than the old one!
Regards,
--
Miguel Saturnino
http://www.teiadigital.pt/ http://www.pelosanimais.org/
http://www.encontra-me.org/ http://www.esteriliza-me.org/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebs
on't follow up!! Don't reply!! Just nod quietly and DON'T MAKE THIS
> MISTAKE AGAIN
>
> -Bill <---- SEE!!! LOOK!!! IT'S RIGHT THERE! IDIOTS!
Bill Paul,
Your surname, family name, last name, or whatever it is called, *is
still your na
.E' Removable Disk
0,1,0 1) *
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
Any sugestions?
TIA!
Miguel
___
freebsd-stable@freebsd.org ma
On Mon, May 27, 2002 at 03:35:52PM +0200, Miguel Mendez wrote:
Hi, hate to quote myself...
> I feel curious about this. Both ODS and VxVM are just kernel modules
> that sit between hardware and the VFS layer if I'm not mistaken. What
^^
W
> Does anyone have any suggestions for troubleshooting this? Any ideas on
> where to continue looking for problems? I'm not looking for answers(unless you
> got them) I'm looking for the next place to look.
When is FreeBSD going to fix the bug that makes nmap -sO crash/reboot
the machine ? :)
> Ipfw and ipf to my eye (without glasses that is) seem to do pretty much the same
> thing. The same is true for ipnat and natd. Of course there are differences
> between the two (ritgh?).
How do you map with a single rule a pool of private addresses into a pool of
real addresses with natd ? :>
> Still reading on this ipfilter for use with ppp0. I made a set of rules
> andd tested them out with ipftest and it just hung there. in controlled c
> out of it no problem. Whatever.
what ipfilter are you using on which version of FreeBSD ?
kernel, module ?
> I am cinfused as to what i sho
53 matches
Mail list logo
