Re: Modifying and compiling openpam / passwd.c
Mr CW [EMAIL PROTECTED] writes: I'm working on a personal-learning project using FreeBSD 5.4 that requires me to recompile passwd.c. My deliema is simple: I want to be able to make changes to /usr/src/contrib/openpam/lib/pam_get_authtok.c and have these changes compiled into passwd. cd /usr/src/lib/libpam make make install ...but if you think that you need to modify pam_get_authtok.c to change how passwd behaves, you're almost certainly on the wrong track. Perhaps you should tell us what you're trying to do, instead of how you're trying to do it. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Creating real bool type for simulation in physics
On Mon, Mar 13, 2006 at 11:13:41AM -0600, Dan Nelson wrote: In the last episode (Mar 13), Mathieu Prevot said: I use freebsd/amd64 (RELENG_6) for simulation in physics. I am working on the Ising model: an assembly of spins (micromagnets) which interact and which are in one of two states (up or down). Until now I use char to define the state of each spin (-1 or 1), however, I remarked that most time is spent on memory I/O. Most of bits are unused. I think that if I can use just one bit per spin, I can have something much faster. I need advices on how to use it. I guess I can't define a new type with a 1/8 byte height (or one bit), yes ? What variable (int, char...) do you recommend to use for a sempron 64 bits. I think I'll need to define new operators (opaque operators, built with bit operators) to switch my spins or use directly the following: | ^ ~ ... Take a look at the bitstring functions, which let you allocate an array of bits and manipulate them individually. They're documented in the bitstring manpage. Thank you. bitstring functions (macros) are based on char (8bits) type. This is not ANSI or POSIX, I will include /usr/src/sys/sys/bitstring.h in my program for portability. vi (nvi), and bind9 also use these macros, but are a bit different. -- Mathieu P http://scienceclue.ath.cx ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: freebsd-hackers Digest, Vol 156, Issue 2
...but if you think that you need to modify pam_get_authtok.c to change how passwd behaves, you're almost certainly on the wrong track. My appologies and thank you for pointing out my error. I have been walking the source tree trying to find out how different programs work and, I'll admit, passwd is one of the first few programs. I had believed that pam_get_authtok.c was tied into passwd through the many different includes in the program tree. Specifically, I want to learn how passwd works from the point where it prompts for the password, where it actually receives the input, how it passes the password off for encryption, and when it finally obtains the encrypted value. The lower portion of ...get_authtok.c appeared to me where this happens, when the response is stored in resp, retyped into resp2 to ensure the two are the same, then sent to pam_set_item() for encryption (?). The way I am reading it, resp points to the unencrypted password string, but I could be wrong. Thank you for your previous tips on recompiling pam. J. Hunt _ FREE pop-up blocking with the new MSN Toolbar get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-hackers Digest, Vol 156, Issue 2
Mr CW [EMAIL PROTECTED] writes: My appologies and thank you for pointing out my error. I have been walking the source tree trying to find out how different programs work and, I'll admit, passwd is one of the first few programs. I had believed that pam_get_authtok.c was tied into passwd through the many different includes in the program tree. Specifically, I want to learn how passwd works from the point where it prompts for the password, where it actually receives the input, how it passes the password off for encryption, and when it finally obtains the encrypted value. It uses PAM. Start by reading the following: URL:http://www.freebsd.org/doc/en/articles/pam/ The lower portion of ...get_authtok.c appeared to me where this happens, when the response is stored in resp, retyped into resp2 to ensure the two are the same, then sent to pam_set_item() for encryption (?). No, pam_set_item() merely stores the password in the PAM context. The way I am reading it, resp points to the unencrypted password string, but I could be wrong. That is correct. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
6.1-PRE boot locks up, using USB keyboard
Hello. I cvsup'd to 6.1-PRERELEASE today (Mar 14 2006), installed world, and tried booting the GENERIC kernel. My machine hangs after the following messages: pmtimer0 on isa0 orm0: ISA Option ROM at iomem 0xd-0xd3 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 (None of the other visible messages pertain to the keyboard or USB, and I can't scroll back) I'm using a USB keyboard, no PS/2. I've tried the hint to disable kbdmux, I've tried with and without selecting the Boot w/ USB keyboard and the machine locks up in the same spot no matter what I try. The same hardware boots just fine with 6.0-RELEASE (although I need to choose the USB keyboard option if I plan on typing). Any suggestions? -- Rick C. Petty ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
CVSup upgrading?
Hi, Can someone tell me what is the src-all tag= . to download the latest beta source with cvsup? Best regards, Carlos Silva ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup upgrading?
On Wed, Mar 15, 2006 at 02:52:43AM +, Carlos Silva, yourdot-internet.com wrote: Hi, Can someone tell me what is the src-all tag= . to download the latest beta source with cvsup? RELENG_6 Kris pgp1KpYhJF3qh.pgp Description: PGP signature
Re: CVSup upgrading?
Hi, but, it erases all! I have a doubt if he downloads the beta kernel sources. do you have another solution? -- Best Regards, Carlos Silva, YourDOT Web: http://www.yourdot-services.com/ Eric Yu escreveu: HEAD On 3/15/06, Carlos Silva, yourdot-internet.com [EMAIL PROTECTED] wrote: Hi, Can someone tell me what is the src-all tag= . to download the latest beta source with cvsup? Best regards, Carlos Silva ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup upgrading?
On Tuesday 14 March 2006 21:01, Carlos Silva, yourdot-internet.com wrote: Hi, but, it erases all! I have a doubt if he downloads the beta kernel sources. do you have another solution? If it erases all, then your supfile is not correct. As Kris said, RELENG_6 is the correct tag to use for what you asked for. Don ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup upgrading?
Carlos Silva, yourdot-internet.com wrote: Hi, but, it erases all! I have a doubt if he downloads the beta kernel sources. do you have another solution? HEAD is not the correct tag. Before I go further, to avoid any confusion, there is no beta source code nor are the kernel sources maintained seperately. That said... If you want the branch of development from which the most recent (version-wise) releases are being made, use tag=RELENG_6. If you want the source tree corresponding to the point of all new development, including experimental, rapidly-changing and otherwise unstable, brand-new code not yet put through broad-base testing, use tag=.. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.1-BETA2/FreeBSD 5.5-BETA2 Available
Announcement The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 6.1-BETA4 and FreeBSD 5.5-BETA4. Both FreeBSD 6.1 and FreeBSD 5.5 are meant to be a refinement of their respective branches with few dramatic changes. A lot of bugfixes have been made, some drivers have been updated, and some areas have been tweaked for better performance, etc. but no large changes have been made to the basic architecture. The FreeBSD 5.5 Release is being done for people who are unable to make the jump to FreeBSD 6.X at this time. We do encourage people to make that transition as soon as possible, though. There have been some updates made between FreeBSD 5.4 and FreeBSD 5.5 but not all of the bugfixes done to RELENG_6 have been backported to RELENG_5. This will almost certainly be the last 5.X release. We encourage people to help with testing so any final bugs can be identified and worked out. Availability of ISO images is given below. If you have an older system you want to update using the normal CVS/cvsup source based upgrade the branch tag to use is RELENG_6 for 6.1 and RELENG_5 for 5.5, though that will change later in the release cycle when we start doing the Release Candidates. Problem reports can be submitted using the send-pr(1) command. The list of open issues and things still being worked on are on the todo list: http://www.freebsd.org/releases/6.1R/todo.html http://www.freebsd.org/releases/5.5R/todo.html Known Issues A couple of significant changes were made to 6.1-BETA4. First is a large set of fixes to the VFS layer and various filesystems that should sigficantly help performance under heavy load and also fix problems with forcefully unmounting these filesystems. While these changes have recieved considerable developer testing, users are requested to test filesystem stability as much as possible to ensure that there are no regressions. The second large change is that sysinstall will now install both the GENERIC and SMP kernels and automatically select the appropriate one based on whether it detects one CPU in the system or multiple CPUs. However, single CPU systems with hyperthreading will still be treated as uni-processor by sysinstall. The automatic selection can be overridden within sysinstall. Testing of this is requested to help identify systems that are not detected correctly. Availability The BETA4 ISOs and FTP support are available on most of the FreeBSD Mirror sites. A list of the mirror sites is available here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html The MD5s are: MD5 (5.5-BETA4-pc98-disc1.iso) = bf6cf1238c000a01fe8c34ed4554e66e MD5 (5.5-BETA4-alpha-bootonly.iso) = 84e55974d8854692a85d43558e10c658 MD5 (5.5-BETA4-alpha-disc1.iso) = b5fc0a01dc6cb96924c7cd9c18af6dd9 MD5 (5.5-BETA4-i386-bootonly.iso) = e54261162e775b692138597ae2512bf6 MD5 (5.5-BETA4-i386-disc1.iso) = 15f3161d4c5f996bbbc9b28682198dde MD5 (5.5-BETA4-i386-disc2.iso) = 10c4c7985eea736862480b0212e60155 MD5 (5.5-BETA4-amd64-bootonly.iso) = 371522c9ab80e7d5c0fadd71d670543e MD5 (5.5-BETA4-amd64-disc1.iso) = 4811510b11620f8706f51e4e0154b8b1 MD5 (5.5-BETA4-amd64-disc2.iso) = 54ee8ec3240de9d84576f1f0cbf2048a MD5 (6.1-BETA4-pc98-disc1.iso) = ee891f12ddb7b62b2c1d3672555ceb3b MD5 (6.1-BETA4-ia64-bootonly.iso) = b05da331e737c6c614acbb924584199e MD5 (6.1-BETA4-ia64-disc1.iso) = d0b09231c1d55308fb8fb45eec845284 MD5 (6.1-BETA4-ia64-livefs.iso) = 9db26824bb09ee98e33eceadb643 MD5 (6.1-BETA4-alpha-bootonly.iso) = c77a7d80803efeba3b8140072ccd4969 MD5 (6.1-BETA4-alpha-disc1.iso) = b2701eb2931dd815b3b595f9183ae5a4 MD5 (6.1-BETA4-i386-bootonly.iso) = 113f1b990d298aa8b7f81d93a3636dc3 MD5 (6.1-BETA4-i386-disc1.iso) = aee3a4416eec24b1795346efeb624416 MD5 (6.1-BETA4-i386-disc2.iso) = 01b01719f7a06d2613a3e9fe15417b3f MD5 (6.1-BETA4-amd64-bootonly.iso) = c52a2081931d89cbbebf50f198e8b169 MD5 (6.1-BETA4-amd64-disc1.iso) = 5624a6ba41abdc60802d21be9ab4cf6e MD5 (6.1-BETA4-amd64-disc2.iso) = db427ec7ab4af75a8224a890c476846d The SHA256s are: SHA256 (5.5-BETA4-pc98-disc1.iso) = 0574c7db49a81c77d1d9cded1add28451026fee5ca52605be03ab6660f9b5ab5 SHA256 (5.5-BETA4-i386-bootonly.iso) = 077a4b6561311af08d9f760d734fc822d2589554f4a25ac413cfeb275a59361c SHA256 (5.5-BETA4-i386-disc1.iso) = 3367499f48d7fdc526a1f447f8e83ee4eef7a76e74784eb7471124499440e05d SHA256 (5.5-BETA4-i386-disc2.iso) = 40751884348826807f6c24ec78d424568be21c3e64fcb002f7cfd2bf9ec3bfa7 SHA256 (5.5-BETA4-amd64-bootonly.iso) = ca7390623cfa64589a4f19c80fa557e8a6085c54335811010c6b609a4202fd20 SHA256 (5.5-BETA4-amd64-disc1.iso) = a9cba0901cf6747193e173eb1c1d1b843ddaa59d12f2e8e84d0d634d2aba5bb0 SHA256 (5.5-BETA4-amd64-disc2.iso) = 763d5dfe8d7bed4dadc8850e04e2ad04b8c3f4ae6e283df6cfdd25b9475a80d0 SHA256 (6.1-BETA4-pc98-disc1.iso) = 3de12c8ec0d65a651bcb200049c5fa7b4a9228ebea6f64dea15b35ab07d19178 SHA256 (6.1-BETA4-ia64-bootonly.iso) =
BETA4! [Re: FreeBSD 6.1-BETA2/FreeBSD 5.5-BETA2 Available]
Sorry, I accidentally sent out an incomplete draft. This announcement is for BETA4, of course. Also, the note about VFS changes below should stress that the changes were made for stability, not performance. Sorry for the confusion. Scott Long wrote: Announcement The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 6.1-BETA4 and FreeBSD 5.5-BETA4. Both FreeBSD 6.1 and FreeBSD 5.5 are meant to be a refinement of their respective branches with few dramatic changes. A lot of bugfixes have been made, some drivers have been updated, and some areas have been tweaked for better performance, etc. but no large changes have been made to the basic architecture. The FreeBSD 5.5 Release is being done for people who are unable to make the jump to FreeBSD 6.X at this time. We do encourage people to make that transition as soon as possible, though. There have been some updates made between FreeBSD 5.4 and FreeBSD 5.5 but not all of the bugfixes done to RELENG_6 have been backported to RELENG_5. This will almost certainly be the last 5.X release. We encourage people to help with testing so any final bugs can be identified and worked out. Availability of ISO images is given below. If you have an older system you want to update using the normal CVS/cvsup source based upgrade the branch tag to use is RELENG_6 for 6.1 and RELENG_5 for 5.5, though that will change later in the release cycle when we start doing the Release Candidates. Problem reports can be submitted using the send-pr(1) command. The list of open issues and things still being worked on are on the todo list: http://www.freebsd.org/releases/6.1R/todo.html http://www.freebsd.org/releases/5.5R/todo.html Known Issues A couple of significant changes were made to 6.1-BETA4. First is a large set of fixes to the VFS layer and various filesystems that should sigficantly help performance under heavy load and also fix problems with forcefully unmounting these filesystems. While these changes have recieved considerable developer testing, users are requested to test filesystem stability as much as possible to ensure that there are no regressions. The second large change is that sysinstall will now install both the GENERIC and SMP kernels and automatically select the appropriate one based on whether it detects one CPU in the system or multiple CPUs. However, single CPU systems with hyperthreading will still be treated as uni-processor by sysinstall. The automatic selection can be overridden within sysinstall. Testing of this is requested to help identify systems that are not detected correctly. Availability The BETA4 ISOs and FTP support are available on most of the FreeBSD Mirror sites. A list of the mirror sites is available here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html The MD5s are: MD5 (5.5-BETA4-pc98-disc1.iso) = bf6cf1238c000a01fe8c34ed4554e66e MD5 (5.5-BETA4-alpha-bootonly.iso) = 84e55974d8854692a85d43558e10c658 MD5 (5.5-BETA4-alpha-disc1.iso) = b5fc0a01dc6cb96924c7cd9c18af6dd9 MD5 (5.5-BETA4-i386-bootonly.iso) = e54261162e775b692138597ae2512bf6 MD5 (5.5-BETA4-i386-disc1.iso) = 15f3161d4c5f996bbbc9b28682198dde MD5 (5.5-BETA4-i386-disc2.iso) = 10c4c7985eea736862480b0212e60155 MD5 (5.5-BETA4-amd64-bootonly.iso) = 371522c9ab80e7d5c0fadd71d670543e MD5 (5.5-BETA4-amd64-disc1.iso) = 4811510b11620f8706f51e4e0154b8b1 MD5 (5.5-BETA4-amd64-disc2.iso) = 54ee8ec3240de9d84576f1f0cbf2048a MD5 (6.1-BETA4-pc98-disc1.iso) = ee891f12ddb7b62b2c1d3672555ceb3b MD5 (6.1-BETA4-ia64-bootonly.iso) = b05da331e737c6c614acbb924584199e MD5 (6.1-BETA4-ia64-disc1.iso) = d0b09231c1d55308fb8fb45eec845284 MD5 (6.1-BETA4-ia64-livefs.iso) = 9db26824bb09ee98e33eceadb643 MD5 (6.1-BETA4-alpha-bootonly.iso) = c77a7d80803efeba3b8140072ccd4969 MD5 (6.1-BETA4-alpha-disc1.iso) = b2701eb2931dd815b3b595f9183ae5a4 MD5 (6.1-BETA4-i386-bootonly.iso) = 113f1b990d298aa8b7f81d93a3636dc3 MD5 (6.1-BETA4-i386-disc1.iso) = aee3a4416eec24b1795346efeb624416 MD5 (6.1-BETA4-i386-disc2.iso) = 01b01719f7a06d2613a3e9fe15417b3f MD5 (6.1-BETA4-amd64-bootonly.iso) = c52a2081931d89cbbebf50f198e8b169 MD5 (6.1-BETA4-amd64-disc1.iso) = 5624a6ba41abdc60802d21be9ab4cf6e MD5 (6.1-BETA4-amd64-disc2.iso) = db427ec7ab4af75a8224a890c476846d The SHA256s are: SHA256 (5.5-BETA4-pc98-disc1.iso) = 0574c7db49a81c77d1d9cded1add28451026fee5ca52605be03ab6660f9b5ab5 SHA256 (5.5-BETA4-i386-bootonly.iso) = 077a4b6561311af08d9f760d734fc822d2589554f4a25ac413cfeb275a59361c SHA256 (5.5-BETA4-i386-disc1.iso) = 3367499f48d7fdc526a1f447f8e83ee4eef7a76e74784eb7471124499440e05d SHA256 (5.5-BETA4-i386-disc2.iso) = 40751884348826807f6c24ec78d424568be21c3e64fcb002f7cfd2bf9ec3bfa7 SHA256 (5.5-BETA4-amd64-bootonly.iso) = ca7390623cfa64589a4f19c80fa557e8a6085c54335811010c6b609a4202fd20 SHA256 (5.5-BETA4-amd64-disc1.iso) = a9cba0901cf6747193e173eb1c1d1b843ddaa59d12f2e8e84d0d634d2aba5bb0 SHA256
