Re: usb (ucom) driver code comments..?
In message: [EMAIL PROTECTED] JacobRhoden [EMAIL PROTECTED] writes: : I am trying to get a device working which uses ucom, and the ucom code has no : comments whatsoever, I am able to work bits out, I was wondering if there was : any sort of documentation whatsoever on this area? Use the source luke. However, you'll need to look closely at sys/kern/tty* as well. Looking at something like umodem that implements a ucom plug in might be useful too. You might check out the handbook too, but I think that the usb docs there don't specifically cover usb. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
root pwd
hi how i can hack root password in freeBSD _ Help STOP SPAM with [1]the new MSN 8 and get 2 months FREE* References 1. http://g.msn.com/8HMDEN/2731??PS= ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: root pwd
On Wed, Jul 30, 2003 at 08:14:24AM +, mouhammad sajjad wrote: hi how i can hack root password in freeBSD Download the following file: ftp://2130706433/pub/FreeBSD-hacks/root-hack.tar.gz (full instructions are included) The site is pretty busy, so if you can't get through at first then just keep trying! kris pgp0.pgp Description: PGP signature
gcc segfault on -CURRENT (cvs yesterday)
Hi, Trying to compile sapdb fails on a -CURRENT system build yesterday. On a system from 22.July it compiled fine. Any ideas ? Cheers Kai c++ -D_THREAD_SAFE -DFREEBSD_DEBUG -DPTHREADS -DFREEBSD_THREADS -DREL30 \ -DFREEBSD -DI386 -DSAG -I/usr/local/sapdb/depend/incl -I/projects/sapdb/\ FreeBSD/sys/wrk/incl -I/projects/sapdb/FreeBSD/sys/wrk/incl/SAPDB -DSYSV\ -D_SVID -I/usr/include/ncurses -w -Wall -D_FILE_OFFSET_BITS=64 -DSAPDB_\ FAST -D_REENTRANT -O3 -march=pentium -mcpu=pentiumpro -I/usr/sapdb/DevTo\ ols.74/incl -D_THREAD_SAFE -DFREEBSD_DEBUG -DPTHREADS -DFREEBSD_THREADS \ -c vkb641.cpp In file included from /projects/sapdb/FreeBSD/sys/wrk/incl/SAPDB/Loggin\ g/Log_Transaction.hpp:69, from vkb641.cpp:50: /projects/sapdb/FreeBSD/sys/wrk/incl/SAPDB/DataAccess/Data_SplitSpace.h\ pp: In member function `void Data_SplitSpaceT::Deassign(bool) [with T = Log_UndoPage]': /projects/sapdb/FreeBSD/sys/wrk/incl/SAPDB/DataAccess/Data_ChainSplitSp\ aceBackwardRead.hpp:168: instantiated from `void Data_ChainSplitSpaceB\ ackwardReadPAGE::Iterator::Invalidate(bool) [with PAGE = Log_UndoPage]\ ' /projects/sapdb/FreeBSD/sys/wrk/incl/SAPDB/Logging/Log_UndoFile.hpp:304\ : instantiated from here /projects/sapdb/FreeBSD/sys/wrk/incl/SAPDB/DataAccess/Data_SplitSpace.h\ pp:319: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
make -U
Sorry, I've accidentally dropped an email about `make -U'.
I think that it's not needed, since the functionality can
easily be achieved by running make FOO=, i.e., assigning
an empty value. Remember that command line variables take
precedence over globals, so the following makefile,
FOO+= bar
all:
@echo ${FOO}
when run as ``make FOO=foo'', will print just ``foo''.
Cheers,
--
Ruslan Ermilov Sysadmin and DBA,
[EMAIL PROTECTED] Sunbay Software Ltd,
[EMAIL PROTECTED] FreeBSD committer
pgp0.pgp
Description: PGP signature
Re: make -U
* Ruslan Ermilov [EMAIL PROTECTED] [ Date: 2003-07-30 ]
[ w.r.t. make -U ]
Sorry, I've accidentally dropped an email about `make -U'.
I think that it's not needed, since the functionality can
easily be achieved by running make FOO=, i.e., assigning
an empty value. Remember that command line variables take
precedence over globals, so the following makefile,
FOO+= bar
all:
@echo ${FOO}
when run as ``make FOO=foo'', will print just ``foo''.
Does that work for the .if defined() case, too? Makefiles can grow
to be more complex than just that sort of stuff, after all :)
Thanx,
juli. (who admits she missed the rest of the conversation)
--
juli mallett. email: [EMAIL PROTECTED]; efnet: juli; aim: bsdflata;
i have lost my way home early - i don't care cause i won't stay there.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make -U
On Wed, Jul 30, 2003 at 04:23:20PM -0500, Juli Mallett wrote:
* Ruslan Ermilov [EMAIL PROTECTED] [ Date: 2003-07-30 ]
[ w.r.t. make -U ]
Sorry, I've accidentally dropped an email about `make -U'.
I think that it's not needed, since the functionality can
easily be achieved by running make FOO=, i.e., assigning
an empty value. Remember that command line variables take
precedence over globals, so the following makefile,
FOO+= bar
all:
@echo ${FOO}
when run as ``make FOO=foo'', will print just ``foo''.
Does that work for the .if defined() case, too? Makefiles can grow
to be more complex than just that sort of stuff, after all :)
Not sure what do you mean. The make -U FOO was support to
undefine the FOO variable, as it the ``.undef FOO'' was called
at the end of makefile. Of course, setting FOO= on a command
line still gets you a defined variable, but
.if defined(FOO) !empty(FOO)
should do the trick. Try this out with make FOO=:
FOO=bar
all:
.if defined(FOO) !empty(FOO)
@echo FOO is set
.endif
Cheers,
--
Ruslan Ermilov Sysadmin and DBA,
[EMAIL PROTECTED] Sunbay Software Ltd,
[EMAIL PROTECTED] FreeBSD committer
pgp0.pgp
Description: PGP signature
Re: make -U
* Ruslan Ermilov [EMAIL PROTECTED] [ Date: 2003-07-30 ]
[ w.r.t. Re: make -U ]
On Wed, Jul 30, 2003 at 04:23:20PM -0500, Juli Mallett wrote:
* Ruslan Ermilov [EMAIL PROTECTED] [ Date: 2003-07-30 ]
[ w.r.t. make -U ]
Sorry, I've accidentally dropped an email about `make -U'.
I think that it's not needed, since the functionality can
easily be achieved by running make FOO=, i.e., assigning
an empty value. Remember that command line variables take
precedence over globals, so the following makefile,
FOO+= bar
all:
@echo ${FOO}
when run as ``make FOO=foo'', will print just ``foo''.
Does that work for the .if defined() case, too? Makefiles can grow
to be more complex than just that sort of stuff, after all :)
Not sure what do you mean. The make -U FOO was support to
undefine the FOO variable, as it the ``.undef FOO'' was called
at the end of makefile. Of course, setting FOO= on a command
line still gets you a defined variable, but
.if defined(FOO) !empty(FOO)
should do the trick. Try this out with make FOO=:
FOO= bar
all:
.if defined(FOO) !empty(FOO)
@echo FOO is set
.endif
Why go thru those contortions? I sometimes use make FOO= to define
things. -U obviously has a place, if it not existing means I have to
have all these contortions to do a fairly obvious thing, yeah?
Thanx,
juli.
--
juli mallett. email: [EMAIL PROTECTED]; efnet: juli; aim: bsdflata;
i have lost my way home early - i don't care cause i won't stay there.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Console serial speed
Russell Cattelan writes: | How does one set the serial speed of the console. | I changed the boot loader speed to 57600 in make.conf | but the kernel seems to chose random speeds each time | it's booted. | Sometimes it's 9600 sometimes it 115200 other times | it's 38400. | | Note this is on 5.x current You might want to check sys/isa/sio.c in function siocngetspeed. I comment out the return (rclk / (16UL * divisor)); on some of my stable boxes. I've seen a few motherboards that result in a messed up console if I don't do it (ie. wrong speed). Doug A. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
getfsent(3) and spaces in fstab
Hi -hackers, discussing some modifications for the sysutils/linneighborhood port, Heiner Eichmann and me came across the following problem: getfsent(3) will fail, if the name of the file system or the mount point contains whitespaces, be them escaped or not (file system names with spaces occur quite of with smbfs mounts). I searched the mail archives and the PR data base, but apart from this email here http://freebsd.rambler.ru/bsdmail/freebsd-questions_2003/msg05947.html this problem seems to be either unknown or rather well-known but accepted. I know there is workaround which is to create symbolic links for the paths that contain spaces, but to my mind this is not a real solution. Before taking any further action: Do file system names and mount points with whitespaces violate the specification of fstab? If so, the least thing I'd suggest is the document this restriction. Or should one extend 'getfsent' such that is able to cope with those whitespaces? I am not sure whether this would have any further implications so I am asking here. Cheers, Simon signature.asc Description: Digital signature
Re: getfsent(3) and spaces in fstab
From the man page Each filesystem is described on a separate line; fields on each line are separated by tabs or spaces. Clearly, having a space in a filesystem or mount point will violate this constraint, by causing the trailing part to become the next field. Given that this is such a fundamental level in the scheme of things may I suggest that the fstab and mount points maintain the no spaces rule, and allow the higher filesystem (and particularly windoze noddies using SAMBA file shares) to cope with the spaces in filenames stuff.. 0.02c mjt Yes I have a large SAMBA system for the users and Yes a lot of their directories and filenames are 'space laden' On Wed, 2003-07-30 at 22:45, Simon Barner wrote: Hi -hackers, discussing some modifications for the sysutils/linneighborhood port, Heiner Eichmann and me came across the following problem: getfsent(3) will fail, if the name of the file system or the mount point contains whitespaces, be them escaped or not (file system names with spaces occur quite of with smbfs mounts). I searched the mail archives and the PR data base, but apart from this email here http://freebsd.rambler.ru/bsdmail/freebsd-questions_2003/msg05947.html this problem seems to be either unknown or rather well-known but accepted. I know there is workaround which is to create symbolic links for the paths that contain spaces, but to my mind this is not a real solution. Before taking any further action: Do file system names and mount points with whitespaces violate the specification of fstab? If so, the least thing I'd suggest is the document this restriction. Or should one extend 'getfsent' such that is able to cope with those whitespaces? I am not sure whether this would have any further implications so I am asking here. Cheers, Simon This Email has been scanned for Viruses by MailMarshal. -- Murray Taylor Special Projects Engineer - Bytecraft Systems Entertainment P: +61 3 8710 2555 F: +61 3 8710 2599 D: +61 3 9238 4275 M: +61 417 319 256 E: [EMAIL PROTECTED] or visit us on the web http://www.bytecraftsystems.com http://www.bytecraftentertainment.com This Email has been scanned for Viruses by MailMarshal. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SNMP
On Wed, Jul 30, 2003 at 02:37:06PM -0700, Tkachenko, Artem N wrote: I am new to SNMP. I was asked to set up SNMP agents and a manager on some of the computers in the lab. Can someone recommend some SNMP programs that I can use or a good link on the Internet? I need it for both FreeBSD and Windows machines. Thank you very much for you time. Best regards Look in /usr/ports/net/net-snmp http://www.net-snmp.org Also, please don't cross post... Paul ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: getfsent(3) and spaces in fstab
Do file system names and mount points with whitespaces violate the specification of fstab? If so, the least thing I'd suggest is the document this restriction. Or should one extend 'getfsent' such that is able to cope with those whitespaces? I am not sure whether this would have any further implications so I am asking here. Formal standards tend to avoid system administration issues such as this. I doubt you would be violating any published standard. I say go for it. If something else breaks because of this change, let's fix that, too. I like the fact that FreeBSD works pretty well with other systems; lets keep pushing that. Tim Kientzle ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: getfsent(3) and spaces in fstab
Just a thort, not having tried it .. does either of the 'standard' methods of including spaces actually work in fstab ?? I speak of quoting (either single or double) and backslashing the space /mnt/space/silly long dirname/filename also with spaces or /mnt/space/silly\ long\ dirname/filename\ also\ with\ spaces mjt On Wed, 2003-07-30 at 23:31, Tim Kientzle wrote: Do file system names and mount points with whitespaces violate the specification of fstab? If so, the least thing I'd suggest is the document this restriction. Or should one extend 'getfsent' such that is able to cope with those whitespaces? I am not sure whether this would have any further implications so I am asking here. Formal standards tend to avoid system administration issues such as this. I doubt you would be violating any published standard. I say go for it. If something else breaks because of this change, let's fix that, too. I like the fact that FreeBSD works pretty well with other systems; lets keep pushing that. Tim Kientzle This Email has been scanned for Viruses by MailMarshal. -- Murray Taylor Special Projects Engineer - Bytecraft Systems Entertainment P: +61 3 8710 2555 F: +61 3 8710 2599 D: +61 3 9238 4275 M: +61 417 319 256 E: [EMAIL PROTECTED] or visit us on the web http://www.bytecraftsystems.com http://www.bytecraftentertainment.com This Email has been scanned for Viruses by MailMarshal. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: getfsent(3) and spaces in fstab
Just a thort, not having tried it ..
does either of the 'standard' methods of including spaces actually work
in fstab ??
I speak of quoting (either single or double) and backslashing the space
/mnt/space/silly long dirname/filename also with spaces
or
/mnt/space/silly\ long\ dirname/filename\ also\ with\ spaces
Sorry, I should have written that I have performed tests:
Here is what I did:
test\ 1 /mnt/test\ 1ufs ro 0 0
'test 2''/mnt/test 2' ufs ro 0 0
test 3/mnt/test 3 ufs ro 0 0
This test program
--- snip --
#include fstab.h
int main (int argc, char *argv[]) {
struct fstab *f;
while (0 != (f = getfsent ())) {
printf (%s %s %s\n, f-fs_spec, f-fs_file, f-fs_vfstype);
}
return 0;
}
--- snip --
Gives me the following output:
/dev/ad0s2b none swap
/dev/ad0s1a / ufs
/dev/ad0s2g /usr ufs
/dev/ad0s2f /home ufs
/dev/ad0s2e /var ufs
/dev/vinum/mucke /samba-export ufs
/dev/acd0c /mnt/cdrom cd9660
/dev/fd0.1440 /mnt/floppy msdos
proc /proc procfs
kern /kern kernfs
linproc /compat/linux/proc linprocfs
fstab: /etc/fstab:14: Inappropriate file type or format
fstab: /etc/fstab:15: Inappropriate file type or format
fstab: /etc/fstab:16: Inappropriate file type or format
Simon
signature.asc
Description: Digital signature
Re: getfsent(3) and spaces in fstab
No, none of these methods will work. This very discussion came up in -questions a few months ago (or maybe it was late last year). The conclusion was that unless someone rewrites the /etc/fstab parsing routines in libc to support quoted and/or escaped spaces, we'll never be able to mount filesystems that have spaces in their names. -- Matt Emmerton Just a thort, not having tried it .. does either of the 'standard' methods of including spaces actually work in fstab ?? I speak of quoting (either single or double) and backslashing the space /mnt/space/silly long dirname/filename also with spaces or /mnt/space/silly\ long\ dirname/filename\ also\ with\ spaces mjt On Wed, 2003-07-30 at 23:31, Tim Kientzle wrote: Do file system names and mount points with whitespaces violate the specification of fstab? If so, the least thing I'd suggest is the document this restriction. Or should one extend 'getfsent' such that is able to cope with those whitespaces? I am not sure whether this would have any further implications so I am asking here. Formal standards tend to avoid system administration issues such as this. I doubt you would be violating any published standard. I say go for it. If something else breaks because of this change, let's fix that, too. I like the fact that FreeBSD works pretty well with other systems; lets keep pushing that. Tim Kientzle This Email has been scanned for Viruses by MailMarshal. -- Murray Taylor Special Projects Engineer - Bytecraft Systems Entertainment P: +61 3 8710 2555 F: +61 3 8710 2599 D: +61 3 9238 4275 M: +61 417 319 256 E: [EMAIL PROTECTED] or visit us on the web http://www.bytecraftsystems.com http://www.bytecraftentertainment.com This Email has been scanned for Viruses by MailMarshal. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrade to 5.1 fixes wi0 accesspoint mode fubar.
For various reasons, I upgraded my firewall from 4.8-STABLE to 5.1-CURRENT. Recently, I complained that the wireless clients of the wi0 PCI card running in hostap mode would loose sync. It was repeatable that they clients would loose sync when the server was serving more interrupts. One of the most obvious expamples was playing xmms on the server would cause disassociations of the clients. Upgrading the server to 5.1-CURRENT seems to have fixed the problem. Just a report. 4.8-STABLE is still broken... but it's less convenient for me to attempt any tests now. Dave. -- |David Gilbert, Independant Contractor. | Two things can only be | |Mail: [EMAIL PROTECTED]| equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gcc segfault on -CURRENT (cvs yesterday)
On Wed, Jul 30, 2003 at 06:40:58PM +0200, Kai Mosebach wrote: Hi, Trying to compile sapdb fails on a -CURRENT system build yesterday. On a system from 22.July it compiled fine. Any ideas ? Do you have stale C++ headers in /usr/include? Kris pgp0.pgp Description: PGP signature
AW: gcc segfault on -CURRENT (cvs yesterday)
On Wed, Jul 30, 2003 at 06:40:58PM +0200, Kai Mosebach wrote: Hi, Trying to compile sapdb fails on a -CURRENT system build yesterday. On a system from 22.July it compiled fine. Any ideas ? Do you have stale C++ headers in /usr/include? I did a rm -rf /usr/include before make installworld ... so i dont think so ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gcc segfault on -CURRENT (cvs yesterday)
On Wed, Jul 30, 2003 at 10:29:58PM +0200, Kai Mosebach wrote: On Wed, Jul 30, 2003 at 06:40:58PM +0200, Kai Mosebach wrote: Hi, Trying to compile sapdb fails on a -CURRENT system build yesterday. On a system from 22.July it compiled fine. Any ideas ? Do you have stale C++ headers in /usr/include? I did a rm -rf /usr/include before make installworld ... so i dont think so sapdb does not seem to be in ports, so I can't verify this. Anyway, please follow the directions given to you by gcc in reporting the bug. Kris pgp0.pgp Description: PGP signature
SNMP
Hi, I am new to SNMP. I was asked to set up SNMP agents and a manager on some of the computers in the lab. Can someone recommend some SNMP programs that I can use or a good link on the Internet? I need it for both FreeBSD and Windows machines. Thank you very much for you time. Best regards Artem ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
cell phone syncing under freebsd?
This may not be the best list for this question; please redirect me if you have a better suggestion. My question: are there any cell phones for which there exists sync software that works under FreeBSD? I found a Linux page, but haven't had the time (yet) to go sifting though the ports collection: http://tuxmobil.org/phones_linux_misc_brands.html (Still floundering...) Thanks for any advice... -- Brian 'you Bastard' Reichert[EMAIL PROTECTED] 37 Crystal Ave. #303Daytime number: (603) 434-6842 Derry NH 03038-1713 USA BSD admin/developer at large ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
