Re: cvs deprecated
27.12.2012 20:29, Sam Fourman Jr. wrote: On Thu, Dec 27, 2012 at 4:18 AM, Wojciech Puchar wrote: but i can't find "moron guide" for using svn to update tree. I cant seem to find a way to handle conflicts, ive tried to do svn revert on every directory, but there is always more... maybe svn just isnt a good way to keep your ports tree current svn up Updating '.': Skipped 'databases' -- Node remains in conflict Skipped 'irc' -- Node remains in conflict Skipped 'lang' -- Node remains in conflict Skipped 'security/cyrus-sasl2' -- Node remains in conflict Skipped 'x11/keybinder' -- Node remains in conflict Skipped 'net-mgmt' -- Node remains in conflict At revision 309546. Summary of conflicts: Skipped paths: 6 svn revert -R /usr/ports - works for me. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: watching for a directory with kqueue
06.03.2012 0:57, Markiyan Kushnir wrote:
On 05.03.2012 20:12, Sergey Matveychuk wrote:
Hi.
I've met a problem with the subj. Could you help?
I'm watching for a directory:
EV_SET(kq_change_list, fd, EVFILT_VNODE,
EV_ADD | EV_ENABLE | EV_ONESHOT,
NOTE_DELETE | NOTE_WRITE | NOTE_EXTEND | NOTE_ATTRIB,
0, 0);
When the directory changed, I read its contens with opendir, like that:
struct kq_event kq_event[1000];
...
while(1) {
n = kevent(kq, kq_change_list, chlist_used, kq_event, 1000, NULL);
for(i = 0; i < n; i++) {
if(kq_event[i].fflags & NOTE_EXTEND || kq_event[i].fflags & NOTE_WRITE) {
opendir(.)
It works when I create a few files (1-3), but when I create 10 files
with touch(1) I see only 3-6 files with opendir. I've got only one event
with kevent() (n=1). Looks like I should got a few events, but I did
not. Could you give an advice how to get all created files?
Try to put some delay (~10ms) after your call to kevent().
Not enough smooth for me, but works.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
watching for a directory with kqueue
Hi.
I've met a problem with the subj. Could you help?
I'm watching for a directory:
EV_SET(kq_change_list, fd, EVFILT_VNODE,
EV_ADD | EV_ENABLE | EV_ONESHOT,
NOTE_DELETE | NOTE_WRITE | NOTE_EXTEND | NOTE_ATTRIB,
0, 0);
When the directory changed, I read its contens with opendir, like that:
struct kq_event kq_event[1000];
...
while(1) {
n = kevent(kq, kq_change_list, chlist_used, kq_event, 1000, NULL);
for(i = 0; i < n; i++) {
if(kq_event[i].fflags & NOTE_EXTEND || kq_event[i].fflags &
NOTE_WRITE) {
opendir(.)
It works when I create a few files (1-3), but when I create 10 files
with touch(1) I see only 3-6 files with opendir. I've got only one event
with kevent() (n=1). Looks like I should got a few events, but I did
not. Could you give an advice how to get all created files?
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
watching for a directory with kqueue
Hi.
I've met a problem with the subj. Could you help?
I'm watching for a directory:
EV_SET(kq_change_list, fd, EVFILT_VNODE,
EV_ADD | EV_ENABLE | EV_ONESHOT,
NOTE_DELETE | NOTE_WRITE | NOTE_EXTEND | NOTE_ATTRIB,
0, 0);
When the directory changed, I read its contens with opendir, like that:
struct kq_event kq_event[1000];
...
while(1) {
n = kevent(kq, kq_change_list, chlist_used, kq_event, 1000, NULL);
for(i = 0; i < n; i++) {
if(kq_event[i].fflags & NOTE_EXTEND || kq_event[i].fflags &
NOTE_WRITE) {
opendir(.)
It works when I create a few files (1-3), but when I create 10 files
with touch(1) I see only 3-6 files with opendir. I've got only one event
with kevent() (n=1). Looks like I should got a few events, but I did
not. Could you give an advice how to get all created files?
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: LIST_REMOVE problem
Joerg Sonnenberger wrote: On Fri, Nov 07, 2008 at 10:07:17PM +0300, Sergey Matveychuk wrote: If we'll take a look at code, LIST_REMOVE don't change a head pointer if you remove the first element: It does via le_priv. OK, thanks. I see now. I'll try to find out why my code don't work this way on 6.4. -- Dixi. Sem. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
LIST_REMOVE problem
Hi!
I wonder how this example from queue(3) works:
while (!LIST_EMPTY(&head)) {/* List Deletion. */
n1 = LIST_FIRST(&head);
LIST_REMOVE(n1, entries);
free(n1);
}
If we'll take a look at code, LIST_REMOVE don't change a head pointer if
you remove the first element:
#define LIST_FIRST(head)((head)->lh_first)
...
#define LIST_REMOVE(elm, field) do {\
if (LIST_NEXT((elm), field) != NULL)\
LIST_NEXT((elm), field)->field.le_prev =\
(elm)->field.le_prev; \
*(elm)->field.le_prev = LIST_NEXT((elm), field);\
} while (0)
So n1 in the example above will point to removed (and freed) element.
--
Dixi.
Sem.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gprof: weird output
Hi. Why there are signed counters in gprof? It look weird: -0.20 -0.10 3749040/-2102105488 insert_overlayed [1800] 112.74 57.07 -2105854528/-2102105488 route2ro [4] [5] 76.3 112.53 56.97 -2102105488 ro_sort [5] 56.960.00 -447564710/-447429068 __bswap32 [6] 0.000.00 243125/94363371 strcmp [13] -- Dixi. Sem. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to get a kthread ID?
Is there a possibility to get a kthread ID inside a kthread? Just like pthread_self(3). -- Dixi. Sem. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
passwd: what problem to allow to try PAM?
Hi!
passwd(1) now disallow changing a password via PAM. Why? Is there some
hidden reason like a security one or something I missed?
Here is code:
/* check where the user's from */
switch (pwd->pw_fields & _PWF_SOURCE) {
case _PWF_FILES:
fprintf(stderr, "Changing local password for %s\n",
pwd->pw_name);
break;
case _PWF_NIS:
fprintf(stderr, "Changing NIS password for %s\n",
pwd->pw_name);
break;
default:
/* XXX: Green men ought to be supported via PAM. */
errx(1,
"Sorry, `passwd' can only change passwords for local or NIS
users.");
}
A comment about green men discouraged, PAM calls are bellow.
--
Dixi.
Sem.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd port of gnu parted
Viktor Vasilev wrote: > Hi, > > I've spent some time this saturday trying to port gnu parted over to > FreeBSD. You can find the result and some instructions on building it here: > > http://0xdeadc0de.net/v/parted/ > > For the moment it only handles ATA drives. A chart describing parted's > features can be found here: > > http://www.gnu.org/software/parted/ > > Since it's a preliminary port, there will be some bugs, so use with caution. > It would be best if you experiment on a spare drive with no precious data. > > Have fun :) You can make a port: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ -- Dixi. Sem. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portmanager
Michael C. Shultz wrote:
if ( getenv("TERM") )
{
. . .
}
Anyway you should use code like that for the cases:
char *term;
term = getenv("TERM");
And check the variable afterwards. It much better than call getenv() twice.
And the first condition would be:
if( term && !strncmp( term, "xterm", 5 ) && isatty(fileno(stdout)) )
And some people not recomend use '!' with str[n]cmp(). Using '== 0' is
better.
It was someting about a code style.
--
Sem.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bin/76089: The "-n" option in /usr/bin/w is broken
Sergey Matveychuk wrote: BTW, UT_HOSTSIZE=16 is too short in my opinion. As I can see, linux has UT_HOSTSIZE=256. -- Sem. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bin/76089: The "-n" option in /usr/bin/w is broken
Garance A Drosihn wrote: Actually, it would be nice to log both. That's what I have done for some printer-related statistics (not sure if I did that in FreeBSD, but I do that for production use at RPI). I like the idea. We can add field 'address' in utmp structure and save hostname and IP address there. It will some backward compatible then (but not for wtmp though). -- Sem. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bin/76089: The "-n" option in /usr/bin/w is broken
Peter Jeremy wrote: Depending on the environment, the IP address may be more changeable than the hostname. Definitely, in a DHCP or dialup environment, you can't rely on the IP address at any time other than during the session. There is little (if any) benefit in logging the IP address instead of the hostname. I agree, environments are different. So may be it makes no sense to change hostname with IP. It was just an idea. But fact is, we lost 'w -n' semantic. And it should be fixed. BTW, UT_HOSTSIZE=16 is too short in my opinion. -- Sem. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bin/76089: The "-n" option in /usr/bin/w is broken
w(1) behaviour has changed with brien commit in w.c revision 1.48. Funny, but looks like '-n' options works right after commit, not before. The reason is utmp holds a host name and w(1) with '-n' flag _do_ resolve hostname back in IP address and without '-n' don't resolve it. It's confised. IMHO to be more robust, we should make utmp to hold an IP address instead of a hostname and change all applications that use it. As bonus it will fix a delay on login when resolving does not work. And last(1) will show more useful IP address instead of changable hostname. But I'm not sure about standards. -- Sem. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
primary slave HDD hangs
Hello. I've sent this email in stable@ but got no answer. Can you give me some advice on this situation? I had have a Maxtor 6Y120L0 HDD (120Gb, 2Mb cache) as primary master. Now I bought Maxtor 6Y160P0 (160Gb, 8Mb cache) and installed it as slave. 4.8-RELEASE hangs on booting with diagnostic: ad1: READ command timeout tag=0 serv=0 - resetting ata0: resetting device On both -CURRENT and WindowsXP system is all right. HDD looks working. Can I do something with it? I'm ready to disable second disk on 4.8 but I'v got no idea how to do it without kernel hacking. (I can disable slave checking, but I'll lost my secondary slave CD-Writer then). -- Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pkg_create
Adam Balogh wrote: On Wed, 2003-08-20 at 07:21, Sergey Matveychuk wrote: Adam Balogh wrote: Hello, Has anyone found a solution for the pkg_create problem mentioned here in June? I'm planing to hack pkg_install with other reasons. So, I can take a look on this. Sem. That would indeed be great :) I can't reproduce a problem. Can you send me an exact example? Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
GNATS problem
What's up with GNATS? PR's are not submitted from august 18 evening. Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pkg_create
Adam Balogh wrote: Hello, Has anyone found a solution for the pkg_create problem mentioned here in June? I'm planing to hack pkg_install with other reasons. So, I can take a look on this. Sem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OpenPAM and OSVERSION
> Because most PAM problems in ports are bugs in the ports themselves, > which Linux-PAM just happens to tolerate and OpenPAM doesn't. In > other words, it should be possible to find a solution to the problem > which works equally well for Linux-PAM and OpenPAM, without the need > to know which is which. And as a last resort, you can make OpenPAM- > specific code conditional on the _OPENPAM preprocessor symbol. No difference for port's user how source is change. Either a patch will apply for 5.0 only when port build or general pach where PAM version detects with preprocessor directives. Result code will be the same. I think it's a style question. What the community opinion? > > What fix will be a right one? > > I can't tell you unless you show me what you believe needs fixing. What a right way escape from PAM_CONV_AGAIN/PAM_TRY_AGAIN and relate code from LINUX_PAM? Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: OpenPAM and OSVERSION
> If you've fixed it in a way which requires knowing whether the system > runs Linux-PAM or OpenPAM, you've fixed it wrong. OK. Why? What fix will be a right one? My strategy is checking OSVERSION when build port and aplay a patch if it's 5.0+. Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: OpenPAM and OSVERSION
> Sergey Matveychuk <[EMAIL PROTECTED]> writes: > > What is OSVERSION num right after OpenPAM implemented? > > What problem are you trying to solve? security/pam-* ports. I'v fiexed pam-mysql for this time. It's works for me. I'm working for PR. Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
OpenPAM and OSVERSION
What is OSVERSION num right after OpenPAM implemented? There is no such in the porters-handbook :( To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Weak port system or how can I attract attention to my PRs?
Hi! For a long time I'v been disapointed with features in ports system. No ports conflicts checking and other stuff. Last year I'v begun make some things - I'v found obsoleted bin/13649 and ports/13650 PRs that introduce a ports conflics checking, I'v asked in freebsd-ports and portmgr about this patches fortune. I'v got an answer from portmgr: "it's good features and could I adapt this patches for current bsd.port.mk and pkg_tools?" I'v spend a weekend for rewriting patches (many changes really was done) and send it as followup to the PRs. It was 1 December 2002. Till now there is no reactions. I'v wrote a few mails to portmgr but I'v just ignored. Now I decide to make a new my own PRs: bin/47145 and ports/47156. Is there a chance somebody look on it and commit it? I'v got more ideas about improvement of bsd.ports.mk. Is interesting my patches to team? May be I'v just spend a time for nothing? I'd like to hear some reaction somebody of team. Comments, advises or so. Who can I talk about bsd.ports.mk improvements? Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
ports conflicts: PR/13650
I'v tried find out a fate of PR/13650 dated by September 1999. I'v wrote to freebsd-ports and to Satoshi. And I'v got no answer. Who can answer me? Who can change bsd.port.mk? Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: wc* function
> On Wed, Dec 05, 2001 at 03:28:29PM +0300, Sergey Matveychuk wrote: > > According to mail archive, work on supporting wide-char functions was in > > progress some time but then stopped. > > We are in need of a new wchar i18n person. Interested? Yes, but I can't. I don't know a lot about wchar. I read now some docs, but not sure it's enough. Alfred Perlstein has offered to integrate this code from netbsd. And it must be tested a few people. I'm ready to take a part. Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: wc* function
> Check out Citrus[1] project's CVS Repo. They have quite promising implementation > of w* functions. Also as I recall correctly some amount of w* functions > are already commited in. > > [1] http://citurs.bsdclub.org Link is dead. Can you check it? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: wc* function
> Check out Citrus[1] project's CVS Repo. They have quite promising implementation > of w* functions. Also as I recall correctly some amount of w* functions > are already commited in. > > [1] http://citurs.bsdclub.org Link is dead. Can you check it? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
wc* function
According to mail archive, work on supporting wide-char functions was in progress some time but then stopped. May be is there some results of this work somewhere? Continue will better than beginning from scratch. Sem. --- Sergey Matveychuk | System Administrator E-Mail: [EMAIL PROTECTED] | Institute Of Aviation Motors Tel: +7(095)362-56-58 | Moscow, Russia Pager: +7(095)918-19-19 ab.2244 | ICQ UIN: 3317990 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
??: wctype.h
> If you can provide sample code to verify the correctness of an implementation > then i may be able to integrate it from netbsd. To my sorrow I don't know enough about wide-char. I need this functions for porting some programm. But if you send me a code I promise to find out about wide-char and test it. Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: wctype.h
> what is great in that? I need them to port some application. May be exist some external libs? > why don't u write ur own release to everyone? I'v got no enough time. But if I would have time may be exist some troubles with it if FreeBSD don't have this function yet. Sem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
wctype.h
Hi! Why widechar functions is not implemented? Is there real difficulty? And can I get it somwhere from a external lib? I need towupper, towlower and iswspace. Thank you. Sem. --- Sergey Matveychuk | System Administrator E-Mail: [EMAIL PROTECTED] | Institute Of Aviation Motors Tel: +7(095)362-56-58 | Moscow, Russia Pager: +7(095)918-19-19 ab.2244 | ICQ UIN: 3317990 --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
