Re: ftream errors under g++ 3.2.2
Allan Bowhill wrote:
I recently updated one of my machines to -current to adapt some code to
build under the new version of gcc (3.2.2). However, file IO using fstream
gives error messages about implicit typenames being deprecated, and I can't
for the life of me figure out what to do my code to make the compiler happy.
Has anyone encountered this?
I do a lot of C++ development on -current, and I have been seeing these
exact warnings. The problem is in the fstream header, however, so there
is nothing you can do to your code to prevent the warnings. You could
modify /usr/include/g++/fstream to silence the warnings, but it would
get overwritten if you upgrade your system.
Below is a small example illustrating the problem. The source below should
compile fine on a previous version of g++, as in -stable. However, it will
not compile on -current using g++ 3.3.2. Does anyone know what to do to the
simple source below to get it to compile happily under -current?
From your output, I don't see compile failures, I see warnings. Do you
have -Werror turned on somewhere that wouldn't show up during normal
usage--like some environment variable or something? I was able to
compile and run your code without issue here.
Honestly, I am surprised that a GCC header would have an implicit
typename since the compiler clearly complains loudly about them. At any
rate, I think the update to GCC 3.3 in -current is going to happen quite
soon, and presumably, the updated GCC C++ headers will have warnings
such as these fully eliminated.
-Patrick
(yes, I have checked gnu gcc's mailing list and FAQ/docs. I can't find an
adequate explanation for it. I suspect it has something to do with stricter
conformance to the finalized C++ standard, but since I am still a novice any
explanation by gcc developers would probably have slipped by me)
-
#include fstream
int main()
{
std::ofstream afile(test.txt);
afile some data;
}
--
gcc -v
Using built-in specs.
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 3.2.2 [FreeBSD] 20030205 (release)
-
g++ test.cc
In file included from test.cc:1:
/usr/include/g++/fstream:304: warning: `typename std::basic_filebuf_CharT,
_Traits::int_type' is implicitly a typename
/usr/include/g++/fstream:304: warning: implicit typename is deprecated,
please
see the documentation for details
/usr/include/g++/fstream:309: warning: `typename std::basic_filebuf_CharT,
_Traits::int_type' is implicitly a typename
/usr/include/g++/fstream:309: warning: implicit typename is deprecated,
please
see the documentation for details
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
--
Patrick L. Hartling | Research Assistant, VRAC
[EMAIL PROTECTED] | 2274 Howe Hall Room 2624
PGP: http://www.137.org/patrick/pgp.txt | T: +1.515.294.4916
http://www.137.org/patrick/ | http://www.vrac.iastate.edu/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: patch for the nVidia driver and -CURRENT
Does anyone have this working with GDM 2.4.1.3 on -current? I've found that I can use the nvidia driver with Maxime's patch on a freshly built -current system as long as I don't use GDM. If I start up GDM, the system freezes as soon as the nvidia logo is replaced by the GDM login screen. In the end, it doesn't make any difference to me if I use GDM or XDM, but I would like to know if there is some existing problem with the accelerated nvidia driver and GDM or if my local X configuration is somehow broken. Thanks. -Patrick walt wrote: Maxime Henrion wrote: --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all, Recent interface changes made the nVidia driver unbuildable on -CURRENT. The attached patch should make it work as it used to. Please let me know if it doesn't. Yes! Mwa! [Big kiss to Maxime] Thank you! The only thing I needed to do to make it work was to delete this line from nv-freebsd.h: #error This driver does not support FreeBSD 5.0/-CURRENT! As long as you are patching you may as well patch that one also, yes? [patch snipped] -- Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2274 Howe Hall Room 2624 PGP: http://www.137.org/patrick/pgp.txt | T: +1.515.294.4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Time keeping problems with 5.0-RELEASE
I just updated a 4.7-STABLE system (last rebuilt using sources from Jan 7, 2003) to 5.0-RELEASE, and now the system clock is going nuts. I had the same problem when I updated from 3-STABLE to 4-STABLE quite a while back. To solve the problem then, I added the following to my kernel configuration file: device apm0 at nexus? disable flags 0x20 For my 5.0 kernel configuration, I have: device apm In /boot/device.hints, I have: hint.apm.0.disabled=1 hint.apm.0.flags=0x20 Unfortunately, this isn't working. Is there something different I need to do for 5.0? Looking in NOTES for information about APM, I see a reference to a sysctl variable kern.timecounter.method, but that doesn't seem to be a valid oid in 5.0. I don't think this system (a cheap, old Cyrix MediaGX-based computer) supports ACPI. At the very least, ACPI isn't enabled by default at boot time as it is on my Athlon system. -Patrick To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Time keeping problems with 5.0-RELEASE
That fixed it. Thanks a bunch. :) -Patrick John Baldwin wrote: On 23-Jan-2003 Patrick Hartling wrote: I just updated a 4.7-STABLE system (last rebuilt using sources from Jan 7, 2003) to 5.0-RELEASE, and now the system clock is going nuts. I had the same problem when I updated from 3-STABLE to 4-STABLE quite a while back. To solve the problem then, I added the following to my kernel configuration file: device apm0 at nexus? disable flags 0x20 For my 5.0 kernel configuration, I have: device apm In /boot/device.hints, I have: hint.apm.0.disabled=1 hint.apm.0.flags=0x20 Unfortunately, this isn't working. Is there something different I need to do for 5.0? Looking in NOTES for information about APM, I see a reference to a sysctl variable kern.timecounter.method, but that doesn't seem to be a valid oid in 5.0. I don't think this system (a cheap, old Cyrix MediaGX-based computer) supports ACPI. At the very least, ACPI isn't enabled by default at boot time as it is on my Athlon system. The sysctl is now kern.timecounter.hardware. For example: sysctl kern.timecounter.hardware kern.timecounter.hardware: ACPI-safe If it is currently set to 'tsc', try changing it to 'i8254' and see if it works better. If so, you can stick that in /etc/sysctl.conf. -- Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED]| 2274 Howe Hall Room 2624 PGP: http://www.137.org/patrick/pgp.txt | T: +1.515.294.4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: OpenOffice swriter working on -CURRENT
Based on your definition of works, I would say that mine does not. :( I just updated my -current system about 12 hours ago. -Patrick Sheldon Hearn wrote: Hi folks, Could someone with an up-to-date -CURRENT (as of anything since Wednesday last week) and OpenOffice let me know whether OpenOffice's swriter works? For me, works just implies that it starts up on a blank document before core dumping, and then accepts at least one character of input. Thanks, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED]| 2274 Howe Hall Room 2624 PGP: http://www.137.org/patrick/pgp.txt | T: +1.515.294.4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current issues
Mark Murray wrote: I'm trying to thrash 5.0 a bit but I've run into some rather more basic issues right off. 1) I think I'm suffering from the 1GB memory hang problem. I'm definitely getting the hangs :-) I'll leave this for now since I'll do some more testing tonight and it's already been raised by someone else anyway, so this is just a me too. I had a nasty console hang (all the VTYs hung about 2 minutes after boot, but the box was otherwise stable enough to make world). I make damn sure I was clean and did a proper make everything (no NOCLEAN) and all was well. I think that I am seeing this as well since I updated to -current from Dec 4. It doesn't bother me too much since I really only use the machine remotely right now. As a result, I haven't been keeping close track to see if there have been similar reports or a fix yet. The first time it hung for me was during 'make installworld' from a single-user boot. I was following the nine-step procedure in /usr/src/Makefile exactly. It sounds like doing another update would clear things up, no? -Patrick -- Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED]| 2274 Howe Hall Room 2624 PGP: http://www.137.org/patrick/pgp.txt | T: +1.515.294.4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current issues
Scott Long wrote: On Tue, Dec 10, 2002 at 09:37:20AM -0600, Patrick Hartling wrote: Mark Murray wrote: I'm trying to thrash 5.0 a bit but I've run into some rather more basic issues right off. 1) I think I'm suffering from the 1GB memory hang problem. I'm definitely getting the hangs :-) I'll leave this for now since I'll do some more testing tonight and it's already been raised by someone else anyway, so this is just a me too. I had a nasty console hang (all the VTYs hung about 2 minutes after boot, but the box was otherwise stable enough to make world). I make damn sure I was clean and did a proper make everything (no NOCLEAN) and all was well. I think that I am seeing this as well since I updated to -current from Dec 4. It doesn't bother me too much since I really only use the machine remotely right now. As a result, I haven't been keeping close track to see if there have been similar reports or a fix yet. The first time it hung for me was during 'make installworld' from a single-user boot. I was following the nine-step procedure in /usr/src/Makefile exactly. It sounds like doing another update would clear things up, no? There were console problems for people using the ahc and ahd drivers that were fixed late in the day on Dec 4. Maybe this is what you're seeing? Probably so! I am indeed using the ahc driver on the machine in question. Thanks for the suggestion. :) -Patrick -- Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED]| 2274 Howe Hall Room 2624 PGP: http://www.137.org/patrick/pgp.txt | T: +1.515.294.4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Lost disklabel
I have a machine that is running -current from October 10, 2002. It had been running fine for about two weeks--up until I had to reboot it. When it came back up, one of my disks apparently lost its disklabel. Is there any way to recover a disklabel? If not, I'm willing to grovel the disk and try to reconstruct its disklabel (there is really only one partition on it that I need to get back, and its at the beginning of the disk), but disklabel(8) won't even let me try to make a new one. If I run 'disklabel -e da3s1', I get an error saying ioctl DIOCGDINFO: Inappropriate ioctl for device. Running 'disklabel -r da3s1' gives a bad magic pack number error, which does not surprise me. This is a dangerously dedicated disk with a single BIOS partition containing four FreeBSD partitions. I have a second identical disk in the machine. fdisk(8) gives the same information for each, so I don't think the BIOS partition is messed up. Is there something obvious that I'm missing about how to fix this problem? -Patrick -- Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED]| 2274 Howe Hall Room 2624 PGP: http://www.137.org/patrick/pgp.txt | T: +1.515.294.4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
uuid.h is not C++ safe
I was just about to put the new DCE 1.1 UUID functions into use in some C++ code, but linking fails because the function prototypes in uuid.h are not protected with the __cplusplus/extern C bits. It's easy enough for me to fix my local copy, but I'm sure this same thing could trip up other people. -Patrick -- Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED]| 2274 Howe Hall Room 2624 PGP: http://www.137.org/patrick/pgp.txt | T: +1.515.294.4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: you need to install a new kernel before an installworld.
Peter Wemm wrote: Due to sigaction(2) syscall number changes, doing a 'make installworld' without having booted a new kernel would be rather messy. For example, if you tried to reboot with the old kernel, /sbin/init and /bin/sh would get a signal and abort. That would be bad. Does this apply to ports as well? GNOME applications have started crashing a lot all of a sudden after updating my kernel (I haven't done 'installworld' yet). Do I need to rebuild all the GNOME stuff, or should I just back off to my previous kernel and wait a little while longer before doing another cvsup? -Patrick -- Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED]| 2274 Howe Hall Room 2624 PGP: http://www.137.org/patrick/pgp.txt | T: +1.515.294.4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: you need to install a new kernel before an installworld.
Juli Mallett wrote: * De: Patrick Hartling [EMAIL PROTECTED] [ Data: 2002-10-28 ] [ Subjecte: Re: HEADS UP: you need to install a new kernel before an installworld. ] Peter Wemm wrote: Due to sigaction(2) syscall number changes, doing a 'make installworld' without having booted a new kernel would be rather messy. For example, if you tried to reboot with the old kernel, /sbin/init and /bin/sh would get a signal and abort. That would be bad. Does this apply to ports as well? GNOME applications have started crashing a lot all of a sudden after updating my kernel (I haven't done 'installworld' yet). Do I need to rebuild all the GNOME stuff, or should I just back off to my previous kernel and wait a little while longer before doing another cvsup? Really? My GNOME apps built from 2 months (up to 2 hours) ago have been working better as I run kernel+world nearer to the impending release. Mine had been working quite well up until this weekend. Only two things changed on my system: the kernel and the freetype2 port version (it's now freetype2-2.1.2_1). I'm running GNOME 2.0, so it may have some instability due to growing pains. However, I have been running GNOME 2 since the (excellent) ports team got it working on FreeBSD--the problems only began this weekend. What sorts of problems are you running into? Nearly all GNOME applications crash with an Abort trap error, and the only way I can log out is to restart the X server. Nautilus is particularly evil because it can get into a situation where it crashes, restarts itself, and crashes again--repeating the process indefinitely. Also, how old was your kernel, and how old is your userland? Userland and old kernel are from October 13. I built the new kernel Friday evening. I booted my Oct 13 kernel this morning, and the GNOME crashes are persisting, so I think my original diagnosis was wrong. I think I'll try to back off to the previous freetype2 revision and see if that fixes things. With no more info, I'd prolly advise you to update everything to the latest, and if problems persist, rebuild your GNOME stuff, and if problems persist, throw exception... I may do so if backing off freetype2 doesn't fix things. But the latter bits of that are a bit drastic, depending on the hw! I'll manage. :) These are the pains of living on the bleeding edge. -Patrick -- Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED]| 2274 Howe Hall Room 2624 PGP: http://www.137.org/patrick/pgp.txt | T: +1.515.294.4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Vinum problems
Bernd, This sounds very promising, but I want to make sure I do this correctly. When you say to remove the plexes, that means to use 'vinum rm' with appropriate options, correct? As far as reconfiguring, can I use the output from 'vinum printconfig' as the input configuration file? Thanks very much for your help. -Patrick Bernd Walter wrote: On Fri, Apr 12, 2002 at 05:46:29PM -0500, Patrick Hartling wrote: I suffered a system crash earlier today running -current from April 10. I have a Vinum volume set up as a mirror, and during the reboot, I had to fsck it. Everything seemed normal (at least that's what I thought), but now my volume cannot be mounted. The output from 'vinum list' is as follows: 2 drives: D a State: up /dev/da3s1e A: 0/12288 MB (0%) D b State: up /dev/da4s1e A: 0/12288 MB (0%) 1 volumes: V mirrorState: down Plexes: 2 Size: 11 GB 2 plexes: P mirror.p0 C State: faulty Subdisks: 1 Size: 11 GB P mirror.p1 C State: faulty Subdisks: 1 Size: 11 GB 2 subdisks: S mirror.p0.s0 State: crashed D: aSize: 11 GB S mirror.p1.s0 State: crashed D: bSize: 11 GB The fact that it says the drives have 0% used greatly concerns me. Before I delve into this any further, is that a sign that everything I had is just gone? Or is there some hope of recovery? There is nothing in /var/log/vinum_hitsory or /var/log/messages that gives me any insight into what went wrong. You have *both* plexes faulty which means that you either have waited too long running with only one disk left or that both failed a once. For the second point can be channel or power supply issues if they share a single resource in common. You will find it out by reading your log files. Of course you should fix the failure reason before doing anything else. I have made a bad expirience once in that if you revive one plex now you will get zeros written because there is no reference plex left. Greg: It's long ago but I forgot to tell you. Do you remember anything about such a bug got fixed? The shure way is to store the vinum printconfig output and then remove both plexes. finaly reconfigure them both beginning using the values from printconfig and start with the drive which run at last, because it has the most recent data. -- Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Vinum problems
I suffered a system crash earlier today running -current from April 10. I have a Vinum volume set up as a mirror, and during the reboot, I had to fsck it. Everything seemed normal (at least that's what I thought), but now my volume cannot be mounted. The output from 'vinum list' is as follows: 2 drives: D a State: up /dev/da3s1e A: 0/12288 MB (0%) D b State: up /dev/da4s1e A: 0/12288 MB (0%) 1 volumes: V mirrorState: down Plexes: 2 Size: 11 GB 2 plexes: P mirror.p0 C State: faulty Subdisks: 1 Size: 11 GB P mirror.p1 C State: faulty Subdisks: 1 Size: 11 GB 2 subdisks: S mirror.p0.s0 State: crashed D: aSize: 11 GB S mirror.p1.s0 State: crashed D: bSize: 11 GB The fact that it says the drives have 0% used greatly concerns me. Before I delve into this any further, is that a sign that everything I had is just gone? Or is there some hope of recovery? There is nothing in /var/log/vinum_hitsory or /var/log/messages that gives me any insight into what went wrong. -Patrick To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Vinum + DEVFS ?
Alfred Perlstein [EMAIL PROTECTED] wrote: } * Patrick Hartling [EMAIL PROTECTED] [010630 14:04] wrote: } I just got two new hard drives, and I am preparing to set them up to do } RAID-1 with Vinum. A few weeks ago (around the time that use of DEVFS } became the default in -current), I saw a message saying that Vinum was } not yet ready for use with DEVFS. Is that still the case? } } I fixed that. :) Let me and Grog know if you have problems. Everything seems to be okay with the vinum device node creation, but I am having problems with my vinum configuration. I basically copied this from an example in the online documentation (which is also in the vinum(8) manpage); drive da3e device /dev/da3s1e drive da4e device /dev/da4s1e volume mirror plex org concat sd length 12g drive da3e plex org concat sd length 12g drive da4e When I do 'vinum create', I get the following: 1: drive da3e device /dev/da3s1e ** 1 : Invalid argument 2: drive da4e device /dev/da4s1e ** 2 : Invalid argument 3: volume mirror 4: plex org concat 5: sd length 12g drive da3e 6: plex org concat 7: sd length 12g drive da4e Which one is the invalid argument, and why is it invalid? Is there some caveat I have missed? -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Vinum + DEVFS ?
Greg Lehey [EMAIL PROTECTED] wrote: } On Sunday, 1 July 2001 at 14:22:36 -0500, Patrick Hartling wrote: } Alfred Perlstein [EMAIL PROTECTED] wrote: } } * Patrick Hartling [EMAIL PROTECTED] [010630 14:04] wrote: } I just got two new hard drives, and I am preparing to set them up to do } RAID-1 with Vinum. A few weeks ago (around the time that use of DEVFS } became the default in -current), I saw a message saying that Vinum was } not yet ready for use with DEVFS. Is that still the case? } } I fixed that. :) Let me and Grog know if you have problems. } } Everything seems to be okay with the vinum device node creation, but I } am having problems with my vinum configuration. I basically copied this } from an example in the online documentation (which is also in the } vinum(8) manpage); } } drive da3e device /dev/da3s1e } drive da4e device /dev/da4s1e } volume mirror }plex org concat } sd length 12g drive da3e }plex org concat } sd length 12g drive da4e } } When I do 'vinum create', I get the following: } } 1: drive da3e device /dev/da3s1e } ** 1 : Invalid argument } 2: drive da4e device /dev/da4s1e } ** 2 : Invalid argument } 3: volume mirror } 4: plex org concat } 5: sd length 12g drive da3e } 6: plex org concat } 7: sd length 12g drive da4e } } Which one is the invalid argument, } } The name of the partition. } } and why is it invalid? } } I can't say for sure, since you don't supply the info asked for in the } man page and the web page. Sorry, I'll be sure to include everything next time. } But I'd be prepared to bet that your } da3s1e and da4s1e partitions are not of type Vinum. Look for } 'disklabel' in the man page. That was it, thanks. I must have missed that point in reading the web pages yesterday (which are very helpful and readable, btw). } BTW, it's bad practice to name your drives after the partition on } which they are currently resident. You can take those two drives and } swap their SCSI IDs. Vinum will still find them and operate } correctly, but your da3s1e partition will be drive da4e, and da4s1e } will be drive da3e, which is completely confusing. Thanks for the tip. -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Vinum + DEVFS ?
I just got two new hard drives, and I am preparing to set them up to do RAID-1 with Vinum. A few weeks ago (around the time that use of DEVFS became the default in -current), I saw a message saying that Vinum was not yet ready for use with DEVFS. Is that still the case? -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Fixed: LyX 1.1.5.2 dumping core
Alex Zepeda [EMAIL PROTECTED] wrote: } On Sun, Jan 28, 2001 at 01:28:03PM -0600, Patrick Hartling wrote: } } ldd was telling me that it had both libc.so.3 and libc.so.5 which seemed } very bad to me. When I recomipled LyX to see if that would fix things, } I noticed that ld was giving a warning about libc.so.3 and libc.so.5 } potentially conflicting. It hadn't ever been a problem before, but it } doesn't seem like the safest arrangment. With the symlink in place, ldd } reports that only libc.so.5 is being used, and everything seems to be } okay. } } Something that LyX is linking to is depending on libc v3. You should } rebuild all of the dependencies, and then rebuild LyX. Yes, I think it's the xforms library which is distributed only in binary form. All of the ports I build myself are linking to libc.so.4 (they were built before the version number was bumped) or to libc.so.5. The xforms website doesn't seem to have anything built for newer versions of FreeBSD. I just have to be patient while the LyX developers work on moving away from xforms to Motif or GTK+ or anything better. -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fixed: LyX 1.1.5.2 dumping core
Jeroen Ruigrok van der Werven [EMAIL PROTECTED] wrote: } -On [20010127 22:30], Patrick Hartling ([EMAIL PROTECTED]) wrote: } Making a symlink from /usr/lib/libc.so.5 to /usr/lib/libc.so.3 seems to } have fixed my LyX problems. I'm guessing libc.so.5 and libc.so.3 were } causing conflicts, especially with the recent changes to libc, but I'm no } expert. Whatever the case, I can get back to work on my thesis now. :) } } Have you tried recompiling LyX with the new libc? I did try that initially, but the problems persisted until I made the symlink and relinked the executable. } That should normally clear any problems. } } I suspect from what you said above, that when you do ldd `which lyx` it } will report lyx being linked against libc.so.3, but for some reason is } trying to use the higher version libc. ldd was telling me that it had both libc.so.3 and libc.so.5 which seemed very bad to me. When I recomipled LyX to see if that would fix things, I noticed that ld was giving a warning about libc.so.3 and libc.so.5 potentially conflicting. It hadn't ever been a problem before, but it doesn't seem like the safest arrangment. With the symlink in place, ldd reports that only libc.so.5 is being used, and everything seems to be okay. -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
LyX 1.1.5.2 dumping core
I just rebuilt my -current system yesterday, and now LyX is throwing up all over itself. It starts up fine, but if I try to load a document or create a new one, it immediately dumps core. The problem seems to be occuring the the xforms library. I have a fresh copy of the compat3x distribution from 4.2-RELEASE installed, but LyX is still unhappy. Does anyone have any suggestions on how I might fix this? I'm not opposed to reverting back to a version of -current from earlier this month. The previous version I was running was from approximately January 5. -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Fixed: LyX 1.1.5.2 dumping core
Patrick Hartling [EMAIL PROTECTED] wrote: } I just rebuilt my -current system yesterday, and now LyX is throwing up } all over itself. It starts up fine, but if I try to load a document or } create a new one, it immediately dumps core. The problem seems to be } occuring the the xforms library. I have a fresh copy of the compat3x } distribution from 4.2-RELEASE installed, but LyX is still unhappy. Does } anyone have any suggestions on how I might fix this? I'm not opposed to } reverting back to a version of -current from earlier this month. The } previous version I was running was from approximately January 5. Making a symlink from /usr/lib/libc.so.5 to /usr/lib/libc.so.3 seems to have fixed my LyX problems. I'm guessing libc.so.5 and libc.so.3 were causing conflicts, especially with the recent changes to libc, but I'm no expert. Whatever the case, I can get back to work on my thesis now. :) -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld fails
Nick Sayer [EMAIL PROTECTED] wrote: } -- } stage 4: populating /usr/obj/usr/src/i386/usr/include } -- [snip] } === rpcsvc } rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h } rpcgen: cannot find any C preprocessor (cpp) I have seen exactly this and reported it a week ago. No one seemed to have noticed though. :\ -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/gnu/usr.bin/cc/cccp Makefile
If I remove the old /usr/libexec/cpp with a newer cpp0 installed, 'make world' fails with the following: -- stage 4: populating /usr/obj/usr/src/i386/usr/include -- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.6.0 DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 SHARED=symlinks includes cd /usr/src/include;make -B all install creating osreldate.h from newvers.sh setvar PARAMFILE /usr/src/include/../sys/sys/param.h; . /usr/src/include/../sys/conf/newvers.sh;echo "$COPYRIGHT" osreldate.h;echo \#'undef __FreeBSD_version' osreldate.h; echo \#'define __FreeBSD_version' $RELDATE osreldate.h === rpcsvc rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h rpcgen: cannot find any C preprocessor (cpp) *** Error code 1 Stop in /usr/src/include/rpcsvc. *** Error code 1 Stop in /usr/src/include. *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error Should other tools be updated to use cpp0 as a result of the change below? -Patrick "David E. O'Brien" [EMAIL PROTECTED] wrote: } obrien 2001/01/03 18:16:24 PST } } Modified files: } gnu/usr.bin/cc/cccp Makefile } Log: } The preprocessor used by the `cc' driver is now named `ccp0' to make it } clear this is the 1st pass of compilation and to make clear this particular } cpp is for `cc's use only. } } Revision ChangesPath } 1.17 +2 -2 src/gnu/usr.bin/cc/cccp/Makefile } } } } To Unsubscribe: send mail to [EMAIL PROTECTED] } with "unsubscribe cvs-all" in the body of the message Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: console freeze
John Baldwin [EMAIL PROTECTED] wrote: } } On 12-Dec-00 Nicolas Souchu wrote: } Hi there, } } I did browse the lists but found nothing about my problem. } Compiling GENERIC of 5.0 works correctly but once I remove } most of uneeded hardware, the console/kbd freeze. } } I join the MACHINE file and the output. } } I even tried to change the graphic card to a PCI S3, same. } } I can get the getty on the serial line, so I tried vidcontrol -i } on it. It reports stupid info. } } Is there something I can try? } } You haven't setup device hints. You can either statically compile them into } your kernel or copy GENERIC.hints to /boot/device.hints and edit it } appropriately. Has there been any resolution to this? I've been having this problem ever since the SMPng stuff went into the tree. I have no success in getting my splash screen to work anymore or in changing video modes with vidcontrol. The splash_bmp KLD always reports the following: module_register_init: MOD_LOAD (splash_bmp, c037f824, 0) error 2 I have done a careful comparison of GENERIC.hints and the /boot/device.hints that I made back when it became a requirement. I've searched the archives and come up empty. I also read cvs-all faithfully, and while I have gotten backed up on mail due to a short vacation here and there, I haven't seen any related commits. What have I missed in keeping up to date? -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: smp instability
Patrick Hartling [EMAIL PROTECTED] wrote: } John Baldwin [EMAIL PROTECTED] wrote: } } } } } On 25-Oct-00 Chuck Robey wrote: } } I'm having rather extreme problems with stability on my dual PIII } } setup. I know this is to be expected, but it's gotten so extreme on my } } system, I can't spend more than a few minutes before it locks up. } } } } Is there any chance that I could make things better by using a sysctl to } } tell the box it's now a single-cpu system? I can't read man pages at the } } moment (I'm composing this on my Sparc Ultra-5) so if this might work, an *** d } } someone knows the exact command to use, I'd appreciate a bit of help. } } } } You can use kernel.old to compile a UP kernel. I always keep a UP kernel } } around just in case. Also, when did your SMP box become unstable? There } } was a known problem with SMP boxes when the vm page zero'ing during the idl *** e } } loop was first turned on that has since been fixed with the latest commit t *** o } } vm_machdep.c yesterday. Symptoms were frequent kernel panic 12's with } } interrupts disabled . } } I am having the same lockup problems as Chuck with SMP kernels built since } October 21. The system completely locks up after a short period of time. } If I'm running X, it does it within 10-15 minutes, but if I don't run X } and just leave it at the console, it can go for a few hours. It does } eventually lock up, though. I haven't tried building a UP kernel, but I } will try the latest vm_machdep.c changes. If that doesn't work, I'll go } the UP route since I'm tired of being unable to list my processes. :\ To follow up on this, I rebuilt everything using sources from approximately 11:00 am CDT yesterday (10/26), and everything is great again. Hooray! -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: smp instability
John Baldwin [EMAIL PROTECTED] wrote: } } On 25-Oct-00 Chuck Robey wrote: } I'm having rather extreme problems with stability on my dual PIII } setup. I know this is to be expected, but it's gotten so extreme on my } system, I can't spend more than a few minutes before it locks up. } } Is there any chance that I could make things better by using a sysctl to } tell the box it's now a single-cpu system? I can't read man pages at the } moment (I'm composing this on my Sparc Ultra-5) so if this might work, and } someone knows the exact command to use, I'd appreciate a bit of help. } } You can use kernel.old to compile a UP kernel. I always keep a UP kernel } around just in case. Also, when did your SMP box become unstable? There } was a known problem with SMP boxes when the vm page zero'ing during the idle } loop was first turned on that has since been fixed with the latest commit to } vm_machdep.c yesterday. Symptoms were frequent kernel panic 12's with } interrupts disabled . I am having the same lockup problems as Chuck with SMP kernels built since October 21. The system completely locks up after a short period of time. If I'm running X, it does it within 10-15 minutes, but if I don't run X and just leave it at the console, it can go for a few hours. It does eventually lock up, though. I haven't tried building a UP kernel, but I will try the latest vm_machdep.c changes. If that doesn't work, I'll go the UP route since I'm tired of being unable to list my processes. :\ My working world+kernel was built October 4. Normally, I update my -current system more frequently than that, but this has been an abnormally busy month. Because of that, I can't narrow down exactly when the instability began. Right now, I'm running with a world built October 23 and the October 4 kernel which is rather unpleasant. -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Panic in pmap_enter
I rebuilt my -current system this morning and am now getting paincs with both the SMP and non-SMP kernels. The current panic with a uniprocessor kernel is: panic: pmap_enter: invalid page directory, pdir=0, va=0xc0da It occurs right after the output for pci0. I'm currently sitting at the db prompt with this kernel. With an SMP kernel, I get the following at the same point in the boot process: panic: pmap_enter: invalid page directory, pdir=0, va=0xc0da3000 mp_lock=0023; cpuid=0; Fatal trap 12: page fault while in kernel mode mp_lock=0024; cpuid=0; This is with sources cvsup'd around 8:30 am CST today (3/31). I can still boot my old kernel (from 3/26), but I get a panic in ifconfig when my Ethernet card (an onboard Intel EtherExpress Pro 10/100) is configured, so it's not easy for me to get working sources or newer changes. Has anyone else seen this? I haven't seen much email today because my -current machine is where I normally get my mail. :( -Patrick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic in pmap_enter
Matthew Dillon [EMAIL PROTECTED] wrote: :I rebuilt my -current system this morning and am now getting paincs with :both the SMP and non-SMP kernels. The current panic with a uniprocessor :kernel is: : :panic: pmap_enter: invalid page directory, pdir=0, va=0xc0da : :It occurs right after the output for pci0. I'm currently sitting at the db :prompt with this kernel. : :With an SMP kernel, I get the following at the same point in the boot :process: : :panic: pmap_enter: invalid page directory, pdir=0, va=0xc0da3000 This usually happens when you set kernel resource options that are too high. If you are setting kernel resource options, try commenting them out. Well, I did recently add options for shared memory settings to get XFree86 4.0 working better. It hadn't caused any problems until now though. I just tried commenting out those options and recompiling, but I still get the panic. To get your old kernel to boot you may have to remove your ethernet card. That's not an option. ;) I am, however, using the if_fxp module instead of compiling the driver into the kernel, so I can avoid loading the module. :I can still boot my old kernel (from 3/26), but I get a panic in ifconfig :when my Ethernet card (an onboard Intel EtherExpress Pro 10/100) is ^^^ :configured, so it's not easy for me to get working sources or newer changes. :Has anyone else seen this? I haven't seen much email today because my :-current machine is where I normally get my mail. :( : : -Patrick You can boot the kernel into single user mode. Interrupt the FreeBSD boot sequence by hitting space, then (typically) type 'boot /kernel -s' (specify a path to your working kernel if not /kernel). Yes, I know how to get into single-user mode and how to choose kernels at boot time. I was a bit vague in what I was trying to do with my old kernel. Sorry for any confusion. -Patrick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic in pmap_enter
Patrick Hartling [EMAIL PROTECTED] wrote: Matthew Dillon [EMAIL PROTECTED] wrote: :I rebuilt my -current system this morning and am now getting paincs with :both the SMP and non-SMP kernels. The current panic with a uniprocessor :kernel is: : :panic: pmap_enter: invalid page directory, pdir=0, va=0xc0da : :It occurs right after the output for pci0. I'm currently sitting at the d b :prompt with this kernel. : :With an SMP kernel, I get the following at the same point in the boot :process: : :panic: pmap_enter: invalid page directory, pdir=0, va=0xc0da3000 This usually happens when you set kernel resource options that are too high. If you are setting kernel resource options, try commenting them out. Well, I did recently add options for shared memory settings to get XFree86 4.0 working better. It hadn't caused any problems until now though. I just tried commenting out those options and recompiling, but I still get the panic. Revision 1.5 of sys/isa/pnpparse.c has fixed my problems, and I didn't have to give up the shared memory options. It was acquired through the magic of cvsweb and copied over via a floppy. :) What a day. -Patrick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
LD_LIBRARY_PATH not working?
Today I have been having problems with applications being unable to find shared libraries at run time with LD_LIBRARY_PATH set correctly. If the library is moved into a directory set at boot time with ldconfig (via rc), it works fine. I have tried it with several different libraries (both C and C++ used by both C and C++ apps), and the results are always the same. This is on a -current system built with sources cvsup'd at approximately 09:10 (CST) March 11, 2000. Did I overlook some configuration change? Thanks. -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: compile error (graphics)
Stephan van Beerschoten [EMAIL PROTECTED] wrote: } ... } cc -Wall -Wstrict-prototypes -Wnested-externs -Wno-format \ } -L/usr/X11R6/lib -o xscreensaver xscreensaver.o windows.o \ } timers.o subprocs.o xset.o splash.o setuid.o stderr.o prefs.o \ } lock.o passwd.o passwd-kerberos.o passwd-pwent.o ../utils/fade.o \ } ../utils/overlay.o ../utils/xroger.o ../utils/spline.o \ } ../utils/yarandom.o ../utils/resources.o ../utils/usleep.o \ } ../utils/visual.o-L/usr/X11R6/lib -lXmu -lXss -lXdpms -lXxf86vm \ } -lSM -lICE -lXmu -lXt -lXt -lX11 -lXext -lkrb -ldes -lcrypt } /usr/lib/libkrb.so: undefined reference to `init_error_table' } /usr/lib/libkrb.so: undefined reference to `initialize_error_table_r' } *** Error code 1 } } I got the same error while trying to compile xlockmore from ports, } and I know I've seen this before that one as well, I just can't } remember. anyone ? You need to add -lcom_err to your link line. -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | Carver Lab - 0095E Black Engineering http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Kerberized telnet not installed
I just built and installed sources cvsup'd at 17:45 CDT October 9 with
${MAKE_KERBEROS4} enabled, but the Kerberized telnet was not installed. I
looked over the recent changes to add SRA to telnet, but I am not familiar
enough with the order in which things are built and installed to figure
out what happened. I did notice that secure/usr.bin/telnet/Makefile was
brought back to life after being dead for about 3 years, but this was the
only change that really jumped out at me as being significant. Is there
something new I need do to get a Kerberized telnet? Thanks.
-Patrick
Patrick L. Hartling | Research Assistant, VRAC
[EMAIL PROTECTED] | Carver Lab - 0095E Black Engineering
http://www.137.org/patrick/ | http://www.vrac.iastate.edu/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
X-related panic
For quite some time, I've been having panics while running X and never saw the actual message. This time, I happened to be in console mode when the crash happened. Here is the panic message: kernel: type 12 trap, code=0 Stopped at pmap_remove_pages+0xd0: decl 0(%ecx) The stack trace I got was: pmap_remve_pages(c7bf1f28,0,bfbfe000,c7c42e6c,c7371034) at pmap_remove_pages+0xd0 exec_new_vmspace(c7c42e6c,c7bd7700,3,c02388fc,4e070840) at exec_elf_imgact+0x109 execve(c7bd7700,c7c42f80,80f740c,,80f74c0) at execve+0x1fe syscall(2f,2f,2f,80f74c0,) at syscall+0x199 Xint0x80_syscall() at Xint0x80_syscall()+0x31 Is this helpful? -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | Carver Lab - 0095E Black Engineering http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: X-related panic
Patrick Hartling [EMAIL PROTECTED] wrote: } For quite some time, I've been having panics while running X and never saw } the actual message. This time, I happened to be in console mode when the } crash happened. I meant to include that I'm using XFree86 3.3.5 built from the ports collection with a kernel and userland built from sources cvsup'd at 17:45 CDT October 9. -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | Carver Lab - 0095E Black Engineering http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
Mike Holling m...@ees.com wrote: } If we want FreeBSD to have any credibility as a workstation OS, we } need DHCP. It should be possible for a user or admin to smack in the } boot floppy, have it autoconfigure the selected network interface, and } perform an FTP installation. This would be really nifty for a lot of people. I've installed Windows NT about a zillion times due to its instability and tendencies to eat itself, but I always liked being able to say at the installation phase that I needed to use DHCP to get my IP address. } I built a static version of the WIDE client and server, both were only } around 140K. What's the problem? It's not like putting emacs in the base } install or anything. I still run FreeBSD on a 386/40 with a 40M MFM main } drive, and even so I'm not worried about the bloat of adding DHCP. Lots } of people have been asking about DHCP on the lists and the newsgroups, } probably because DSL/cablemodems are becoming more readily available (at } least in the US). People repeatedly ask me if FreeBSD comes with a DHCP client when I suggest it as an alternative to Linux. I always tell them You can build the port or install a precompiled package, and as easy as that is for people who are familiar with FreeBSD's wonderful ports and package systems, it still causes some people to shy away. } Windows comes with DHCP. Heck, even my old Mac IIci running System 7.5.5 } comes with DHCP. It's small and increasingly useful, why not make it part } of the base distribution? Or would you rather have FreeBSD be like } RedHat, where you have to install an RPM for just about everything? When someone can simply click a radio button or mark a check box in their network configuration in these operating systems, they seem to assume that having to do anything more than that will be too hard. I think that having this small client (which I have installed as a port) in the base operating system will get people to warm up to the idea of trying out FreeBSD. It's one less thing that inexperiencied people have to worry about. These new people may find it semi-frightening to have to remember all those numbers and have to type them in, possibly more than once if something goes wrong. -Patrick Patrick L. Hartling | Research Assistant, ICEMT myst...@friley-184-92.res.iastate.edu | Carver Lab - 0095E Black Engineering http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Incorrect idle times
I'm getting some weird/wrong idle times with newly opened windows. For example, this is from a few minutes ago: w 3:27PM up 13 mins, 6 users, load averages: 0.21, 0.18, 0.13 USER TTY FROM LOGIN@ IDLE WHAT [...] mystify p3 :0.0 3:17PM 1:00 ssh friley-185-206.res [...] mystify p5 :0.0 3:26PM 2:03 ssh -l patrick crunche mystify p6 :0.0 3:27PM 28:41 ssh -l patrick crunche These are in xterms that I just opened and in which I have done nothing (including type in a password thanks to ssh). This is on a freshly built 4.0-current system running XFree86 3.3.3.1. I saw this before rebuilding this afternoon but didn't pay attention to the conditions under which it happened. It's easily repeatable by simply opening a new xterm and not typing anything in it. If I close the xterm on ttyp6 by logging out and then open a new one, the idle time is at zero. If I close it by clicking on the window manager's close button, the idle time picks up where it left off. It's not a problem or even an annoyance. It's just a little strange since it seems as though idle times are being recycled in a way. -Patrick Patrick L. Hartling | Research Assistant, ICEMT myst...@friley-184-92.res.iastate.edu | Carver Lab - 0095E Black Engineering http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Reading a text file with BTX
Mike Smith m...@smith.net.au wrote: } Is there a way to view the contents of a text file (specifically, } /boot/loader.rc) with BTX? Now that there are all these nifty new modules, } my kernel is a lot smaller and my /boot/loader.rc is a lot longer. The way } I have my /boot/loader.rc setup is such that it unloads everythin } automatically loaded if I drop to the BTX prompt instead of autobooting. } This is fairly convenient except when I want to boot an alternate kernel but } still load all the same modules that I use in my default kernel. If there } isn't such a feature, it would be really nice if there were a 'cat' command } or something along those lines so that I could read the contents of } /boot/loader.rc and get everything properly reloaded by hand. Could it be } added or could I just make my own somehow? Thanks a bunch. } } Perhaps try something like: } } @set kernelname=kernel } @read -t 5 -p Enter kernel name [kernel] : kernelname } @load $kernelname } @include /boot/modules.default } -include /boot/modules.$kernelname } @autoboot 5 } } The 'include' commands make it easier to keep your module sets } organised, should you want to do that. That looks great to me. I was thinking that something like the above would probably be necessary, but I haven't learned Forth yet. This should be just what I need though. Thanks! -Patrick Patrick L. Hartling | Research Assistant, ICEMT myst...@friley-184-92.res.iastate.edu | Carver Lab - 0095E Black Engineering http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Reading a text file with BTX
Is there a way to view the contents of a text file (specifically, /boot/loader.rc) with BTX? Now that there are all these nifty new modules, my kernel is a lot smaller and my /boot/loader.rc is a lot longer. The way I have my /boot/loader.rc setup is such that it unloads everythin automatically loaded if I drop to the BTX prompt instead of autobooting. This is fairly convenient except when I want to boot an alternate kernel but still load all the same modules that I use in my default kernel. If there isn't such a feature, it would be really nice if there were a 'cat' command or something along those lines so that I could read the contents of /boot/loader.rc and get everything properly reloaded by hand. Could it be added or could I just make my own somehow? Thanks a bunch. -Patrick Patrick L. Hartling | Research Assistant, ICEMT myst...@friley-184-92.res.iastate.edu | Carver Lab - 0095E Black Engineering http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Reading a text file with BTX
Daniel C. Sobral d...@newsguy.com wrote: } Patrick Hartling wrote: } } Is there a way to view the contents of a text file (specifically, } /boot/loader.rc) with BTX? Now that there are all these nifty new modules, } my kernel is a lot smaller and my /boot/loader.rc is a lot longer. The way } I have my /boot/loader.rc setup is such that it unloads everythin } automatically loaded if I drop to the BTX prompt instead of autobooting. } This is fairly convenient except when I want to boot an alternate kernel but } still load all the same modules that I use in my default kernel. If there } isn't such a feature, it would be really nice if there were a 'cat' command } or something along those lines so that I could read the contents of } /boot/loader.rc and get everything properly reloaded by hand. Could it be } added or could I just make my own somehow? Thanks a bunch. } } You might be refering to the loader prompt, not the btx prompt. If } you type something as soon as the first | is shown, that's btx. If } you wait a little, or enter /boot/loader, then you get loader. } Specifically, if it has processed loader.rc, then you are inside } loader, not btx. Ah, I see. Sorry for using the wrong name, but you did figure out what I meant which is good. :) } Showing contents of a file happens to be possible too, as soon as } bin/9753 gets in. Jordan promised cat and more for us, but since he } is too busy with his update targets, I decided to get more in. :-) Cool beans, that's what I was curious about. Thanks for the info. -Patrick Patrick L. Hartling | Research Assistant, ICEMT myst...@friley-184-92.res.iastate.edu | Carver Lab - 0095E Black Engineering http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Changes to pam_kerberosIV broke ftpd
It appears that revision 1.9 of lib/libpam/modules/pam_kerberosIV/klogin.c and revision 1.3 of lib/libpam/modules/pam_kerberosIV/pam_kerberosIV.c broke ftpd when compiling with MAKE_KERBEROS defined. The errors I get when compiling with 4.0-current sources (and presumably 3.0-stable though I haven't tried compiling that yet) cvsup'd last night at about 11:00 pm CST are: === libexec/ftpd [...] cc -O -pipe -DSETPROCTITLE -DSKEY -DLOGIN_CAP -DVIRTUAL_HOSTING -Wall -I/usr/src/libexec/ftpd/../../contrib-crypto/telnet -DKERBEROS -I/usr/obj/usr/src/tmp/usr/include -o ftpd ftpd.o ftpcmd.o logwtmp.o popen.o skey-stuff.o klogin.o -lskey -lmd -lcrypt -lutil -lkrb -ldes ftpd.o: In function `pass': ftpd.o(.text+0x11c9): undefined reference to `klogin' klogin.o: In function `_pam_klogin': klogin.o(.text+0x3e): undefined reference to `_pam_noticketsdontcomplain' klogin.o(.text+0xd2): undefined reference to `_pam_krbtkfile_env' klogin.o(.text+0x1a3): undefined reference to `_pam_notickets' This could be the case for other Kerberized programs, but this is as far as my 'make world' got. -Patrick Patrick L. Hartling | Research Assistant, ICEMT myst...@friley-184-92.res.iastate.edu | Carver Lab - 0095E Black Engineering http://www.public.iastate.edu/~oz/ | http://www.icemt.iastate.edu/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
