Re: Why Are You NOT Using FreeBSD ?
On 6/9/2012 14:50, O. Hartmann wrote: Lucky man! We are "off" from some desktop services (like LibreOffice and Firefox) for more than a week now! Why did you update to begin with? Bug/security fix? -- Adam Strohl http://www.ateamsystems.com/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: sysinstall: is it really at the end of its lifecycle?
On Wed, 15 Dec 1999, Poul-Henning Kamp wrote: > With due attention paid to realities I offer the following two code > names for your consideration: > > "freon" YES! This has my vote - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall: is it really at the end of its lifecycle?
On Tue, 14 Dec 1999, Jordan K. Hubbard wrote: > VESA syscons, either using libvgl and an array of crude widgets or > something like MGR and its widget set, has long been on the wish-list > but I didn't even include it in my summary since it's still very much > a pipe-dream. :-) Hmm, this has been a fantasy of mine, as well. I was hoping to assist with the syscons code enough so that we could get a simple primative API down for drawing graphics on the screen, but my job seems to be taking up any time I'd have to do that now, hopefully that will change :P However, the syscons cleanup is proceeding anyway from what I've seen on the list. As long as we have basic graphics drawing, we'd be able to impliment our own widgets, if need be. I don't know how big the requirements for libvgl are, or how much spare space on that second floppy we have, though. > There's actually one mode you forgot, which is > what I call "text mode", and that's straight ascii prompts, no CUI-style > dialog boxes or anything. Think about text-to-speach devices for > the blind or serial consoles attached to really *dumb* terminals. :-) This is a cool idea, also good for script based installs where you want it to go fast and dirty. - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall: is it really at the end of its lifecycle?
On Wed, 15 Dec 1999, Thomas David Rivers wrote: > This is important to note... 25% of all the installs I do are > on MGA (remember monochrome graphics adapter - a hercules card.) True, hence there would be other display targets, ie; CUI, and I like Jordan's text-only non GUI idea, too. It doesn't really matter. The new sysinstall architecture should be such that it is completely indepentent of the UI (or lack there of). > So, I would not be in favor of any replacement that required a VESA > or VGA platform... I agree, this would not be a requirement, just another option. - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall: is it really at the end of its lifecycle?
On Wed, 15 Dec 1999, Daniel C. Sobral wrote: > Hey, I like CUI. I'd rather install with a CUI than a GUI, all other > things being equal. And besides some quirks here and there, I really > like sysinstall. Its nice, but its not where it should be. > But the fact is that when we get featured in a magazine article, > user-friendly install == GUI. No GUI, it's not an user-friendly install. > End of review. You can kick and scream all you want, that's the way it > is. Either we live by these rules, or we loose. A VESA GUI based sysinstall replacement would probably be small enough to fit on a floppy, yet still have the friendlyness that a new user/reviewer would look for. If we follow jkh's outline, making another "front end target" for the script shouldn't be that hard. You have X, VESA Syscons, and Text Syscons. The script says "ok, prompt user for ", under X it opens a window, under Text some ASCII dialog, and under VESA a little window. - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: LinkSys probe locks up some NE2000 clones (was: ed0 hangs atboot)
I also get this lock up on a machine with a ISA NE2000 clone: ed0 at 0x300-0x31f irq 9 on isa ed0: address 00:40:33:23:6b:c1, type NE2000 (16 bit) I have every other NIC driver removed, but a -CURRENT kernel with ed0 enabled on it will cause it to lock hard. Disabling the device in the kernel config will let me boot. On Sun, 31 Oct 1999, Bob Bishop wrote: > >> The LinkSys probe code (in particular the checksum at the start of > >> ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the machine > >> up. I guess you have the same problem. > >> > > > > ouch! not goodwhat is the ethernet address of your ne2000 > >clone? > > ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0 > ed0: address 00:20:18:72:97:67, type NE2000 (16 bit) - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: protecting from attacks
I seem to recall allowing a limit for max processes when I was looking at
fork bombs back in '95 ... ahh the memories.
- ----( Adam Strohl ) -
- UNIX Operations/Systems http://www.digitalspark.net -
- adams (at) digitalspark.netxxx.xxx. x -
- ( DigitalSpark.NET )--- -
On Fri, 29 Oct 1999, Luke wrote:
> I have been trying to figure out a sane method of stopping this one:
> while(1) {
> fork();
> }
>
> on a machine with no limits the load went to 290+ I tried fiddling with
> limits and got it down to making the load 2-3 but the limits are ridiculous.
> I didn't look in mail archives so sorry if this has been discussed before
>
> Luke
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Current Uncompilable?
On 3 Oct 1999, Rajappa Iyer wrote: > I had the same problem, but only with make -j8 world. Plain "make > world" worked fine for me. I compiled with make -j 12 actually, dual processor madness and all :P (51 minutes on my Dual Celeron 450s UDMA 33 IDE disks /w SoftUpdates) I could hear my IDE disks begging for mercy. However, I have seen cases where some programs, and kernels wouldn't compile with the -j or -l (gmake only) options, this is a problem in the makefile organization, and generally any modern makefile should withstand being -j ed. - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Current Uncompilable?
I just rebuilt from a system that was pre-sig update (cvsuped an hour or so ago) and everything worked perfectly. I did however build, install, and boot a new kernel before doing a make world. - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - On Mon, 4 Oct 1999, Greg Lehey wrote: > On Sunday, 3 October 1999 at 19:51:21 -0400, Bill A. K. wrote: > > Hi Everybody, > > my -current dosen't want to build today. it's failing with a signal 12 > > on libgcc1.c (or could it be libgccl.c)? Anybody else have these problems > > today? As of about 30-45 minutes ago when I tried CVsuping again, there was > > so changes to the libs or anything that I think could be this. > > Have you built a new kernel first? > > Greg > -- > See complete headers for address, home page and phone numbers > finger [EMAIL PROTECTED] for PGP public key > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: sigset_t changes committed
On Wed, 29 Sep 1999, Jim Bloom wrote: > I believe this must be fixed. At some point in time, there is going to be > another change to the kernel such that some older version of the code cannot run > on a new kernel. I believe this situation has occurred before. This will lead > to a situation where a new kernel is required before the build and a new build > is required before the new kernel is installed. We cannot have this paradox. FTPing a GENERIC kernel from somewhere would solve this, then just single user the box, make world. Build your kernel. Reboot. I have to side with the people who say that this being a problem for someone means that person shouldn't be running -current. Furthermore, for when 4.0 becomes a -R or -S, ftping in a compiled kernel shouldn't be that hard of a price to pay for going from 3.2. /stand/sysinstall based upgrades could easily seemlessly take care of this, too. I'm sure people are working on a fix for having to do this, but doing it just isn't this big of a deal. Maybe I'm missing something. - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Wierd su problem still there
> I too have encountered the same symptoms. I have no idea why this started > happening, but I have found a couple ways around it. First, two Control-Ds > will act as a Return if you find the status lines appearing. Second, the > stty command will fix it totally. I use `stty status ^T' to remap the status > command to Control-T rather than Control-J (the ^T is a carat, T): Damn, that works like a charm, but I wonder what is causing this to begin with. > I hope this helps, Yeah, good work around thanks :) - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Wierd su problem still there
adams@nightfall(18:06:51)$ su Password:load: 0.37 cmd: su 381 [ttyin] 0.00u 0.00s 0% 668k load: 0.37 cmd: su 381 [ttyin] 0.00u 0.00s 0% 668k load: 0.37 cmd: su 381 [ttyin] 0.00u 0.00s 0% 668k each "load" line is an enter press. If I rlogin to localhost and su there is no problem other programs do this, too: --- FTP 220 silver FTP server (Version 6.00LS) ready. Name (silver:adams): load: 0.16 cmd: ftp 387 [ttyin] 0.01u 0.00s 0% 1072k --- Telnet (only some hosts, thought) BSDI BSD/OS 4.0.1 (granite) (ttyp1) login: adams Password:load: 0.17 cmd: login_radius 23867 [running] 0.00u 0.01s 0% 228k As soon as I get this the app becomes totaly useless, I can't control-z or control-c it, I have to kill the term. VNC (on the password prompt) and other random apps do this too, but you get the idea, I just rebuild/installed world from an cvsup from about 30 minutes ago, this has been going on for over a week (I cvsup every day). Any ideas? - ----( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
libcrypt issue upgraded to "Fiasco" status ;'D
Rebuilt world and kernel about 20 minutes ago, now XDM cores, along with login, I've had to fall back to single user mode, whoever is workin' on this let me know if you commit some fixes, I'll be awake for a few hours and I'd love to test them (read as "love to have my box working again" ;'D). -- Adam To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Wierd su/vnc issue
Well, is there a work around, telneting out does the same thing, using the -l option used to allow me to log into remote hosts, not anymore, same with loopback telneting and suing. I can hear Jordan already: "TAKE IT LIKE A MAN!" ;'D - ----( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - On Tue, 21 Sep 1999, Pierre Beyssac wrote: > On Mon, Sep 20, 1999 at 09:16:13PM +, Adam Strohl wrote: > > adams@nightfall(21:13:30)$ su > > Password:load: 0.35 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k > > > > As soon as I hit enter I get more: > > load: 0.32 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k > > I saw that, too. That might be a strange side effect of the > libcrypt->libscrypt change (note how it happens with programs which > ask for a passwd). I just get SIGSEVs right now when I try su but > I've had the same as you at least once before that. > -- > Pierre Beyssac[EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Wierd su/vnc issue
adams@nightfall(21:13:30)$ su Password:load: 0.35 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k As soon as I hit enter I get more: load: 0.32 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k load: 0.32 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k load: 0.32 cmd: su 407 [ttyin] 0.00u 0.00s 0% 664k (hit enter 3 times). I can't do anything here, I have to telnet back into my machine log in as myself, and then su, it looks like some wierd tty issue. Also, vncviewer does the same thing: vncviewer: VNC server supports protocol version 3.3 (viewer 3.3) Password: load: 0.13 cmd: vncviewer 422 [ttyin] 0.00u 0.00s 0% 840k This has been going on for the last few days, I just rebuilt my entire world about 30 seconds ago, still there. - ----( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata drivers
Remake your acd device, I think you may need a patch to do it. I had the same problem, until I rm-ed the device and remade it. - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - On Sun, 19 Sep 1999, Gary Hampton wrote: > I have been trying to get the ata drivers to work on my system for a > a while now but can't seem to mount my cdrom drives. This is what I get on > boot up: > ata-pci0: at device 7.1 on pci0 > ata-pci0: Busmastering DMA supported > atapi: piomode=4, dmamode=2, udmamode=-1 > ata0: master: setting up WDMA2 mode on PIIX3/4 chip OK > atapi: DMA transfer mode set > acd0: CDROM drive at ata0 as master > acd0: drive speed 1034KB/sec, 512KB cache, DMA > acd0: supported read types: CD-R, CD-RW, CD-DA, packet track > acd0: supported write types: CD-R, CD-RW, test write > acd0: Audio: play, 128 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: CD-ROM 120mm data disc loaded, unlocked, lock protected > atapi: piomode=3, dmamode=1, udmamode=-1 > atapi: PIO transfer mode set > acd1: < 8X_CD-ROM/ A01> CDROM drive at ata0 as slave > acd1: drive speed 1367KB/sec, 120KB cache > acd1: supported read types: CD-DA > acd1: Audio: play, 255 volume levels > acd1: Mechanism: ejectable tray > acd1: Medium: CD-ROM 120mm data disc loaded, unlocked > > Is there a trick I need to know to mount this? I have tride mounting > /dev/ almost every thing with "cd" in it but no luck the only drive I can > mount is /dev/cd0c my scsi cdrom. I was able to mount these drives with > the default atapi drivers but my system hung whe I tride to write to the > cd-rw drive. > > The easiest way to figure the cost of living is to take your income and > add ten percent. > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 2xPIIIx450 results & NFS results
On Sat, 18 Sep 1999, Rodney W. Grimes wrote: > So far about alls I have confirmed is that the problem does not exists > with BIOS 1009 when the apm code is not compiled into the kernel. I'll > have a full matrix of with/without apm 1008/1009/1010 some time tomarrow, > as the machines are building there system disks now. Sounds good. Is there a way to detect the BIOS revision on boot or something and either warn (ie; Say "Update yer BIOS!") or install a work around? - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 2xPIIIx450 results & NFS results
OK, Upgraded my Asus P2B-D machien from BIOS version 1008 to 1010, the problem disappeared. Popped back to my old 1008 BIOS, problem came back. Looks like there was some wierd issue that got resolved in 1009 or 1010. - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - On Sat, 18 Sep 1999, Garrett Wollman wrote: > < >said: > > > I've been getting this too on 4.0-C, just rebuild last night, still there. > > top displays: > > CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% > > idle > > On my dual-PPro Intel BB440FX system I am not seeing this. > > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > [EMAIL PROTECTED] | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 2xPIIIx450 results & NFS results
I've been getting this too on 4.0-C, just rebuild last night, still there. top displays: CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle AND loads > 2 make the machine very unresponsive, its like SMP was before that pci_support.c patch a month or two ago. - ----( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - On Fri, 17 Sep 1999, Rodney W. Grimes wrote: > > :> I/O, and then closing it. > > : > > :4.0-CURRENT (SMP on an ASUS P2B-DS with two CPU's installed; BIOS revision > > :1008.A, running `systat -vm 1' gives the normal display but without any > > :numbers filled in, then switches over to an empty screen that says: > > :... > > > > Whenever systat or top do weird things it probably means you > > need to recompile libkvm. > > This is not a libkvm problem on my box, these are fresh make worlds > on 3.3-RC as of 2 days ago. It only appears to occur when running SMP, > and has been a problem in the past if you look at the cvs log for > systat/vmstat.c. Search for the specific message given by this > user in the log, you'll see it has come and gone at least once. > > I already sent one message out about this, in response to Jordans > ``release tag going down''. > > -- > Rod Grimes - KD7CAX - (RWG25)[EMAIL PROTECTED] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More benchmarking stuff...
Actually, the IIRC, NetApps have NVRAM cache, powering the thing down and back up doesn't change anything. - ----( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - On Fri, 17 Sep 1999, Dan Nelson wrote: > In the last episode (Sep 17), Brad Knowles said: > > At 8:05 AM -0700 1999/9/17, Thomas Dean wrote: > > > Are the files deleted before they are actually written to disk? > > > > Good question. I don't know the answer. I know that the > > process is to create all the files first, then operate on them > > (including deletions and more creations), and then finally do a > > removal of all of them as quickly as possible at the end of the test. > > > > I'd be willing to guess a lot of files do get created and then > > deleted before the data ever gets written to disk. After all, > > postmark was written to simulate the kind of a load that a > > heavily-used mail system places on the machine, and that's precisely > > the sort of environment where something like softupdates or mounting > > filesystems async does tend to help the most. > > Hmm. But when you're running a mail spool, you _want_ your files to > get committed to disk, don't you? If you've got (guessing) 500 spool > files sitting in unflushed disk caches and you reboot, those files are > lost. Softupdated just guarantees that the disk will be in a stable > state after a crash, not that all data written before the crash will be > available. > > Don't NetApps do logging, so if the system crashes, the files are > recovered from the log? > > -- > Dan Nelson > [EMAIL PROTECTED] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NewPCM and Quake :)
I get this two, it sounds like its playing at the wrong sampling speed, but none of them (speeds) sound right. - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - On Fri, 10 Sep 1999, Daniel O'Connor wrote: > Hi, > I am trying NewPCM on -current with an AWE64. > It works fine for normal sound apps like esd, splay etc etc.. but Quake 1 & 2 > which use the DMA buffers to play their sound. It is allowed to do this (the > ioctl is supported), but it stutters very badly. > > Its a bit hard to explain :) > > --- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3.3RC install errors
It'll let you installworld, but its not fixed :)
gnu/usr.bin/perl/utils/h2ph/Makefile is where it gets triggered.
The afterinstall rule calls some miniperl routine:
afterinstall:
cd ${DESTDIR}/usr/include; \
miniperl ${.OBJDIR}/${PROG} -d \
${DESTDIR}/usr/libdata/perl/5.00503/mach * */*
which resolves to (all one line):
cd /usr/include; miniperl \
/usr/obj/usr/src/gnu/usr.bin/perl/utils/h2ph/h2ph -d \
/usr/libdata/perl/5.00503/mach * */*
Checking on it further reveals that the miniperl routine is returning an
non-normal exit for some reason (?), changing the rule to ignore the
return value like this:
afterinstall:
-cd ${DESTDIR}/usr/include; \
miniperl ${.OBJDIR}/${PROG} -d \
${DESTDIR}/usr/libdata/perl/5.00503/mach * */*
allows it to be run from the Makefile as well without generating a fatal
error (and aborting the make).
I don't know perl at all, someone else will have to take a look at the
file (/usr/obj/usr/src/gnu/usr.bin/perl/utils/h2ph/h2ph) and see why its
returning an error in this case (it's output shows nothing that resembles
an error condition).
Good luck :)
- ----( Adam Strohl ) -
- UNIX Operations/Systems http://www.digitalspark.net -
- adams (at) digitalspark.netxxx.xxx. x -
- ( DigitalSpark.NET )--- -
On Tue, 7 Sep 1999, Kip Macy wrote:
> Thanks, that fixed it.
>
> -Kip
>
> On Tue, 7 Sep 1999, Adam Strohl wrote:
>
> > I get this on 4.0-C its because of this thing in
> > gnu/usr.bin/perl/utils/h2ph if I remeber correctly. I just removed the
> > directory from the utils Makefile ("when in doubt comment it out") and
> > everything works, though I don't work with perl much.
> >
> > That being said, I've held off mentioning it as I wasn't sure that it
> > wasn't due to an error on my part. 4.0-C has been doing this for the last
> > 2-3 weeks, up until my last cvsup about 2 days ago.
> >
> > Let me know if anyone needs more specific info/what you need, I'd be happy
> > to help.
> >
> > - ( Adam Strohl ) -
> > - UNIX Operations/Systems http://www.digitalspark.net -
> > - adams (at) digitalspark.netxxx.xxx. x -
> > - ( DigitalSpark.NET )--- -
> >
> > On Tue, 7 Sep 1999, Kip Macy wrote:
> >
> > > I am sorry if I am repeating something that has already been fixed -
> > > I just did buildworld which completed without errors - however, when I did
> > > installworld it ended with the following:
> > >
> > >
> > > vm/vm_object.h -> vm/vm_object.ph
> > > vm/vm_page.h -> vm/vm_page.ph
> > > vm/vm_pageout.h -> vm/vm_pageout.ph
> > > vm/vm_pager.h -> vm/vm_pager.ph
> > > vm/vm_param.h -> vm/vm_param.ph
> > > vm/vm_prot.h -> vm/vm_prot.ph
> > > vm/vm_zone.h -> vm/vm_zone.ph
> > > vm/vnode_pager.h -> vm/vnode_pager.ph
> > > *** Error code 1
> > >
> > > Stop.
> > > *** Error code 1
> > >
> > > Stop.
> > > *** Error code 1
> > >
> > > Stop.
> > > *** Error code 1
> > >
> > > Stop.
> > > *** Error code 1
> > >
> > > Stop.
> > > *** Error code 1
> > >
> > > Stop.
> > > *** Error code 1
> > >
> > > Stop.
> > > *** Error code 1
> > >
> > > Stop.
> > > *** Error code 1
> > >
> > > Stop.
> > > *** Error code 1
> > >
> > > Stop.
> > >
> > >
> > >
> > >
> > >
> > > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > > with "unsubscribe freebsd-current" in the body of the message
> > >
> > >
> >
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
> >
> >
>
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: 3.3RC install errors
I get this on 4.0-C its because of this thing in
gnu/usr.bin/perl/utils/h2ph if I remeber correctly. I just removed the
directory from the utils Makefile ("when in doubt comment it out") and
everything works, though I don't work with perl much.
That being said, I've held off mentioning it as I wasn't sure that it
wasn't due to an error on my part. 4.0-C has been doing this for the last
2-3 weeks, up until my last cvsup about 2 days ago.
Let me know if anyone needs more specific info/what you need, I'd be happy
to help.
- ( Adam Strohl ) -
- UNIX Operations/Systems http://www.digitalspark.net -
- adams (at) digitalspark.netxxx.xxx. x -
- ( DigitalSpark.NET )--- -
On Tue, 7 Sep 1999, Kip Macy wrote:
> I am sorry if I am repeating something that has already been fixed -
> I just did buildworld which completed without errors - however, when I did
> installworld it ended with the following:
>
>
> vm/vm_object.h -> vm/vm_object.ph
> vm/vm_page.h -> vm/vm_page.ph
> vm/vm_pageout.h -> vm/vm_pageout.ph
> vm/vm_pager.h -> vm/vm_pager.ph
> vm/vm_param.h -> vm/vm_param.ph
> vm/vm_prot.h -> vm/vm_prot.ph
> vm/vm_zone.h -> vm/vm_zone.ph
> vm/vnode_pager.h -> vm/vnode_pager.ph
> *** Error code 1
>
> Stop.
> *** Error code 1
>
> Stop.
> *** Error code 1
>
> Stop.
> *** Error code 1
>
> Stop.
> *** Error code 1
>
> Stop.
> *** Error code 1
>
> Stop.
> *** Error code 1
>
> Stop.
> *** Error code 1
>
> Stop.
> *** Error code 1
>
> Stop.
> *** Error code 1
>
> Stop.
>
>
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: it's time...
On Wed, 11 Aug 1999, Warner Losh wrote: > It also would allow one to kick the VGA display into 132 columns in > the boot loader and have more of a chance to get more of the boot > process on the screen. syscons already supports parts of this... I was just reading through the thread again, and I was thinking about a Sun style boot where the screen is kicked into the VESA mode of your choice, we could have a FreeBSD daemon displaying in the upper left corner, etc. > There is no reason to hard code 80 into the kernel. Otherwise one > could argue why have stty columns at all :-). I have to agree with this, flexibility == AGoodThing(TM). > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HELP!!! -CURRENT libtool problem.
On Sun, 11 Jul 1999, Nik Clayton wrote: > Q: I want to use this cool piece of software that's in the FreeBSD > ports system. But I can't build it on my 3.x-stable system. > > Why not? > > A: Ah, sorry. The ports system only targets -current, trying to get > it to work with -stable is too much work. If you want to be sure > of using the ports system successfully you need to be running > -current. > A: E-mail the port maintainer. You'll find that's a lot easier. And if the port maintainer doesn't respond/and or you want it fixed ASAP, instead of going through the hassel of (for new people) learning how to cvsup make build world, etc, fix the problem yourself. Also: Last I checked the port system didn't "target" -current. Infact I bet more stuff compiles under -stable than -current, esspecially when things are getting shaken up. I think the real issue is that people see/hear that something works under -current and without thinking of the other tradeoffs (ie; they can't just type 'make' and it all works without them knowing what is going on), leap off and go to -current because at the time it was the easiest way to get something working. You're basically restating something we already know. -current has the latest. Sometimes this means that it has more because its all working pretty well, sometimes it doesn't. We know this. That's the point. - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Interesting new warnings in boot msgs from -current kernel
I too get those exact messages with my bktr, and my sound drivers. pcib0: on motherboard pci0: on pcib0 WARNING: "bktr" is usurping "bktr"'s cdevsw[] - cut - snd0: WARNING: "snd" is usurping "snd"'s cdevsw[] sbmidi0 at port 0x330 on isa0 snd0: WARNING: "snd" is usurping "snd"'s cdevsw[] The devices all work fine, though. - ( Adam Strohl ) - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.netxxx.xxx. x - - ( DigitalSpark.NET )--- - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
