Upgrading from a not-very-current current

If you want to complain that I shouldn't be running -current in the first place, don't bother. I upgraded because -stable doesn't support SMP + fork with shared memory. I want to upgrade from a pre-signal changes -current to -current (I'm having problems with a pnic card getting corrupted mbufs

Re: Fallback to PIO (was: Errors from the ata disk driver)

It seems Greg Lehey wrote: > On Monday, 13 December 1999 at 9:03:16 +0100, Soren Schmidt wrote: > > It seems [EMAIL PROTECTED] wrote: > >> Will the backdown to PIO mode be permanent till the next reboot of the > >> machine, or will the driver be able to attempt to return to DMA mode after > >> a

Re: vinum start needs block device

On Monday, 13 December 1999 at 18:18:14 -0500, Bill Fumerola wrote: > On Sun, 12 Dec 1999, Peter Wemm wrote: > >>> -if (drive->vp->v_type != VBLK) { /* only consider bl >> ock devices */ >>> +if (!vn_isdisk(drive->vp)) { /* only consider

Re: FYI: Benchmarked ATA driver

On Saturday, 11 December 1999 at 18:55:27 +0100, Soren Schmidt wrote: > It seems Dieter Rothacker wrote: >> Hi, >> >> here I have my Bonnie++ 0.99d output: >> machine is a P233MMX, 128MB, Hotrod66 with IBM DJNA-352500. >> (One slice, one partition UFS) >> -- >> Version 0.99d--Sequentia

Fallback to PIO (was: Errors from the ata disk driver)

On Monday, 13 December 1999 at 9:03:16 +0100, Soren Schmidt wrote: > It seems [EMAIL PROTECTED] wrote: >> Will the backdown to PIO mode be permanent till the next reboot of the >> machine, or will the driver be able to attempt to return to DMA mode after >> a timeout period. I'm only seeing thes

Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

In message <[EMAIL PROTECTED]> Brian Somers writes: : *cough*DEVFS*cough* devfs*D* Warner 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?

> 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. You can reprogram the character table and draw fairly nice looking menus in text mode. The last generations of MS-DOS based programs used them

Re: sysinstall: is it really at the end of its lifecycle?

> 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. VESA sysc

Re: RE: Speaking of moving files (Re: make world broken building fortunes )

: :Poul-Henning Kamp wrote :> It would make more sense, considering the way FreeBSD is distributed for :> /usr/local to be a mountpoint than for /usr to be a mountpoint. :> :> /var is traditionally a mountpoint to keep the logs out of harms :> way (and vice versa), but /usr never had that level o

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

Re: sysinstall: is it really at the end of its lifecycle?

Just to to correct a misunderstanding... Ryan Thompson wrote: > > Daniel, here, sees the X install as being "user-friendly". Is the text > based install not? Granted, it's not the point and click interface that > windows users are accustomed to, but, clearly, if users can't navigate the > menu

Re: syscons extension: "propellers"

>> I'm not yet 100% convinced that it would make sense to separate >> the propellers code into a module. Is 5 Kbyte of kernel code >> really that much of a problem? Please note that > >I certainly wouldn't argue this based on size, no. To understand the >point I was arguing, consider what woul

Re: sysinstall: is it really at the end of its lifecycle?

> My interest lies in exactly the opposite direction: I want to stick > a floppy in and have a box find an install server and follow a > pre-defined recipe for building itself, ala Jumpstart or Kickstart. And you're far from alone in wanting this, another reason I've been wanting to go to a scrip

Re: sysinstall: is it really at the end of its lifecycle?

"Jordan K. Hubbard" wrote: > > > As far as the successor to sysinstall goes, I think it would be > > nice to have both a console version and an X version, with some X > > tookit such as Lesstif or Qt, or Tcl/Tk. It could be a lot like > > RedHat's "linuxconf", where you can use it as both an i

Re: Speaking of moving files

> > A person who really knew fsdb could do it /bin/fsdb, infact it's > > And for everyone else ;-) > > WARNING >Use this tool with extreme caution--you can damage an FFS file system >beyond what fsck(8) can repair. Yea.. well... fsdb /dev/rda0s1a cd /dev/ cd da0s1g chown root c

Re: configure problems

On Tue, Dec 14, 1999 at 03:06:58PM -0800, Chris Piazza wrote: > > [EMAIL PROTECTED] is for issues surounding the bleading edge > > development in the base system. > > It *is* a problem with freebsd-current, though. See PR bin/15328. That was not obvious from the email. It still should have *s

Re: Speaking of moving files

> A person who really knew fsdb could do it /bin/fsdb, infact it's And for everyone else ;-) WARNING Use this tool with extreme caution--you can damage an FFS file system beyond what fsck(8) can repair. tonym To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe f

Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

On Wed, Dec 15, 1999 at 01:39:28AM +, Brian Somers wrote: > [.] > > On a related subject: don't you think it's high time to end up this > > madness with MAKEDEV being a shell script, and reimplement it in C? Today, > [.] > *cough*DEVFS*cough* Gesunteit. - mark -- Mark Newt

Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

> [.] > > On a related subject: don't you think it's high time to end up this > > madness with MAKEDEV being a shell script, and reimplement it in C? Today, > [.] > *cough*DEVFS*cough* Yea... been hearing that for 4 years... one of it's big short comings is that it needs a persistent back

Re: sysinstall: is it really at the end of its lifecycle?

> On Wed, Dec 15, 1999, George Michaelson wrote: > > Why do we have to make FreeBSD more like HP-UX? the most sucky UNIX ever > > invented apart from AIX? Hmmph. When FreeBSD has a fully SMP-ized kernel, including filesystem and network stacks and device drivers, and when it has something that

Re: sysinstall: is it really at the end of its lifecycle?

On Wed, Dec 15, 1999, George Michaelson wrote: > Why do we have to make FreeBSD more like HP-UX? the most sucky UNIX ever > invented apart from AIX? Is this a fact? I always sort of liked HP-UX. Not as fun as FreeBSD for obvious reasons, but... > sysinstall is perfectly good enough as an en

Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

[.] > On a related subject: don't you think it's high time to end up this > madness with MAKEDEV being a shell script, and reimplement it in C? Today, [.] *cough*DEVFS*cough* -- Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]>

Re: sysinstall: is it really at the end of its lifecycle?

On Tue, 14 Dec 1999, Jordan K. Hubbard wrote: > Something we also have to stay aware of in this discussion is the fact > that even if most hackers could give a fig for graphical installers > and consider them to be an unneeded bit of hand-holding, it would > still be nice to have a framework whic

Re: Speaking of moving files

[Charset ISO-8859-1 unsupported, filtering to ASCII...] > Ben Rosengart wrote in list.freebsd-current: > > On Tue, 14 Dec 1999, Matthew Dillon wrote: > > > > > I think at one time or another all of us have missed *something* in > > > /usr that wasn't in /. For example, disklabel -e d

Re: sysinstall: is it really at the end of its lifecycle?

On Tue, Dec 14, 1999 at 05:37:09PM -0600, Ryan Thompson wrote: > Daniel, here, sees the X install as being "user-friendly". Is the text > based install not? Let's not get too fixated on the visual aspect of installing the OS: That's just a sideline (an important one, but a sideline nonethele

MAKEDEV (Re: Speaking of moving files (Re: make world broken buildingfortunes ) )

On Mon, 13 Dec 1999, Bill Fumerola wrote: > On Mon, 13 Dec 1999, Louis A. Mamakos wrote: > > > So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with > > just the root file system mounted? > > As one who just got his ass bitten by this, I would vote yes. On a related subject

Re: Speaking of moving files (Re: make world broken building fortunes )

> "BSDman" == BSDman <[EMAIL PROTECTED]> writes: BSDman> one idea about /usr is to allow the admin to mount it BSDman> read-only. I didn't tried it but this would give some BSDman> level of security against modifications of the files there BSDman> in. This is particulary us

Re: sysinstall: is it really at the end of its lifecycle?

Argh!!! SMIT! Hack! Puke! Why do we have to make FreeBSD more like HP-UX? the most sucky UNIX ever invented apart from AIX? Those of us old enough to remember the SunView install tool with graphical disk icons and the amazing 'free disk hog' barchart partition manager, while finding it vaguely

Re: sysinstall: is it really at the end of its lifecycle?

I have one request for whatever becomes of sysinstall. And that is to make it technically consistent with the command line utilities capabilities. For example, I ran into (on several different occasions) problems where i would label a disk, allocate paritions, change parition types, etc., and i

RE: Speaking of moving files (Re: make world broken building fortunes )

Poul-Henning Kamp wrote > It would make more sense, considering the way FreeBSD is distributed for > /usr/local to be a mountpoint than for /usr to be a mountpoint. > > /var is traditionally a mountpoint to keep the logs out of harms > way (and vice versa), but /usr never had that level of justi

Re: sysinstall: is it really at the end of its lifecycle?

On Wed, Dec 15, 1999, Wilko Bulte wrote: > This does, however, have all the risks of building yet another SMIT or > SAM. :-( Neither attempt at making Unix sysadm 'user-friendly' makes > me want to cheer. What do you want in making Unix quick to administer? Seems to me that's the real goal of

Re: sysinstall: is it really at the end of its lifecycle?

On Wed, Dec 15, 1999, Peter Jeremy wrote: > Firstly, size: One of sysinstall's requirements is that it fit (along > with a variety of other related commands) onto a floppy disk. Last > time I checked, the /stand bundle (sysinstall + friends) was ~640K. > The smallest X-server (XF86_VGA16) is 1.7M

Re: sysinstall: is it really at the end of its lifecycle?

On Wed, 15 Dec 1999, Daniel C. Sobral wrote: > Peter Jeremy wrote: > > > > [...] > > Motif, it's several times the size of the Xserver. Unless we want to > > mandate the use of ZIP drives (or similar) as FreeBSD install > > floppies, we're limited to a syscons (or VTxxx) sysinstall. > > There

Re: sysinstall: is it really at the end of its lifecycle?

On Tue, Dec 14, 1999, Jordan K. Hubbard wrote: > That's one of the design precepts of the New System, in fact. There > is one common UI abstraction which sysinstall II (hereafter referred > to as Setup) and the new package system both use. The generic UI > front-end API is "bound" at runtime to

Re: sysinstall: is it really at the end of its lifecycle?

> And: how many people would volunteer for such a job? > Or is it assumed that since this appears suspiciously like Real Work > it will be a paid-for job? It will be a paid-for job, naturally. Something we also have to stay aware of in this discussion is the fact that even if most hackers could

Re: sysinstall: is it really at the end of its lifecycle?

On Tue, Dec 14, 1999, Donn Miller wrote: > Maybe we could call it "sysconfig", in honor of the old > /etc/sysconfig file that was superceded bt /etc/rc.conf. That's not very creative! I had "Trident" in mind. Only problem is that the name is used by a company that makes video card chips and

Re: sysinstall: is it really at the end of its lifecycle?

On Wed, Dec 15, 1999 at 08:33:52AM +1030, Mark Newton wrote: > On Wed, Dec 15, 1999 at 07:47:00AM +1100, Peter Jeremy wrote: > > Given the primary mission of sysinstall is to load FreeBSD, I'd > > go so far as to say that developing an X version would be wasting > > valuable developer resource

Re: sysinstall: is it really at the end of its lifecycle?

Most people I have shown the FreeBSD installer are much more impressed with it than Redhat's snazzy GUI. -Kip On Tue, 14 Dec 1999, jack wrote: > Today Mike Smith wrote: > > > > Given the primary mission of sysinstall is to load FreeBSD, I'd > > > go so far as to

Re: sysinstall: is it really at the end of its lifecycle?

> Personally, I like the speed of the current installation and wouldn't > want to wait for X to start. It will triple my install setup time > since right now I'm hardware speed limited (nearly) with sysinstall. > It is much faster to draw the dialog boxes with libdialog than to > start X. It wil

Re: sysinstall: is it really at the end of its lifecycle?

Personally, I like the speed of the current installation and wouldn't want to wait for X to start. It will triple my install setup time since right now I'm hardware speed limited (nearly) with sysinstall. It is much faster to draw the dialog boxes with libdialog than to start X. But I'm a mutant

Re: syscons extension: "propellers"

In message <[EMAIL PROTECTED]> jack writes: : I just tried only netscape in my .xinitrc and it worked fine. As : well as "ddd ${WINDOW_MANAGER}" or "xterm" run from .xinitrc has : for me in the past. Nearly all applications "work" without a window manager for some reduced expection of "work."

Re: configure problems

On Tue, Dec 14, 1999 at 08:24:06AM -0800, David O'Brien wrote: > On Tue, Dec 14, 1999 at 05:00:14PM +0100, Pascal Hofstee wrote: > > I have noticed some weird problems lately when running configure-scripts. > > E.g. when trying to build the gtk12-port configure just hangs waiting for > > Please r

Re: sysinstall: is it really at the end of its lifecycle?

Today Mike Smith wrote: > > Given the primary mission of sysinstall is to load FreeBSD, I'd > > go so far as to say that developing an X version would be wasting > > valuable developer resources (IMHO, of course). > > It's a painful tradeoff between functionality and flash. The latter is > an

Re: syscons extension: "propellers"

Today Oliver Fromme wrote: > I'm afraid that wouldn't work. In order to run non-trivial X11 > apps, you _will_ need a full-blown X server, including X libs. > You'll also need at least a very simple window manager (while > xclock would probably work without, Netscape would certainly be > pretty

Re: sysinstall: is it really at the end of its lifecycle?

> > I know Jordan mentioned Qt before his over-enthusiastic hand-waving > > made him over-balance, but Lesstif and Qt (or anything else related to > > X11) have a number of serious problems. > > That's ok; He also said it could be back-ended by TurboVision, with > the decision of which GUI to

Re: sysinstall: is it really at the end of its lifecycle?

On 14-Dec-99 Peter Jeremy wrote: > On 1999-Dec-14 18:36:04 +1100, Donn Miller <[EMAIL PROTECTED]> wrote: >>As far as the successor to sysinstall goes, I think it would be >>nice to have both a console version and an X version, with some X >>tookit such as Lesstif or Qt, or Tcl/Tk. > > I know Jor

Re: sysinstall: is it really at the end of its lifecycle?

Peter Jeremy wrote: > > Firstly, size: One of sysinstall's requirements is that it fit (along > with a variety of other related commands) onto a floppy disk. Last > time I checked, the /stand bundle (sysinstall + friends) was ~640K. > The smallest X-server (XF86_VGA16) is 1.7MB (plus libraries).

Re: sysinstall: is it really at the end of its lifecycle?

On Wed, Dec 15, 1999 at 07:47:00AM +1100, Peter Jeremy wrote: > On 1999-Dec-14 18:36:04 +1100, Donn Miller <[EMAIL PROTECTED]> wrote: > >As far as the successor to sysinstall goes, I think it would be > >nice to have both a console version and an X version, with some X > >tookit such as Lesst

Re: syscons extension: "propellers"

Donn Miller wrote in list.freebsd-current: > Actually, that's not a bad idea. One idea I had was combining > syscons with XFree86 server code, so you always have a crippled X > server running without the bloat of a full-blown X server > running. I'm afraid that wouldn't work. In order to ru

Re: syscons extension: "propellers"

> I'm not yet 100% convinced that it would make sense to separate > the propellers code into a module. Is 5 Kbyte of kernel code > really that much of a problem? Please note that I certainly wouldn't argue this based on size, no. To understand the point I was arguing, consider what would have

Re: pcm driver breakage

[Followup to myself] With the latest changes to the pcm driver, a downgrade of channel.c to 1.8 doesn't help any more: I cannot hear anything while playing something (in my case with mpg123). A verbose output of mpg123 shows me that the application seems to hang after a few write()'s to the sound

Re: sysinstall: is it really at the end of its lifecycle?

> > Firstly, size: One of sysinstall's requirements is that it fit (along > with a variety of other related commands) onto a floppy disk. Last > time I checked, the /stand bundle (sysinstall + friends) was ~640K. > The smallest X-server (XF86_VGA16) is 1.7MB (plus libraries). I don't > have eit

Re: Speaking of moving files (Re: make world broken building fortunes )

> How about removing awk from MAKEDEV so life isn't so hard to recover > when you use a 3.3 fixit floppy after removing /dev and not making > enough of it again. How about finally starting to work on devfs and forget about all the MAKEDEV junk and leave it as it is for now? Blaz Zupan, [EMAIL PR

Re: sysinstall: is it really at the end of its lifecycle?

On 1999-Dec-14 18:36:04 +1100, Donn Miller <[EMAIL PROTECTED]> wrote: >As far as the successor to sysinstall goes, I think it would be >nice to have both a console version and an X version, with some X >tookit such as Lesstif or Qt, or Tcl/Tk. I know Jordan mentioned Qt before his over-enthusiast

Re: syscons extension: "propellers"

Andrzej Bialecki wrote in list.freebsd-current: > On Tue, 14 Dec 1999, Donn Miller wrote: > > I think another way (instead of ifdefs) would be to provide some > > hooks into syscons, so that the "propellers" code can be loaded > > or unloaded via kldload/unload. I'm not yet 100% convinced tha

Re: Speaking of moving files

Ben Rosengart wrote in list.freebsd-current: > On Tue, 14 Dec 1999, Matthew Dillon wrote: > > > I think at one time or another all of us have missed *something* in > > /usr that wasn't in /. For example, disklabel -e doesn't work without > > vi -- which is in /usr. > > Good e

Re: Speaking of moving files (Re: make world broken building fortunes )

On Tue, Dec 14, 1999 at 07:38:32PM +0100, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Matthew Dillon writes: > > > >I think at one time or another all of us have missed *something* in > >/usr that wasn't in /. For example, disklabel -e doesn't work without > >vi -- whic

Re: Speaking of moving files (Re: make world broken building fortunes )

On Tue, Dec 14, 1999 at 10:32:23AM -0800, Matthew Dillon wrote: > :> > :> > So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with > :> > just the root file system mounted? > :> > :> As one who just got his ass bitten by this, I would vote yes. > : > :As one who's missed chown

FTP and PAM syslog question

I've been working with ftp and PAM lately and I noticed that when there is no entry for ftp in pam.conf the following messages are generated in the system logs: Dec 14 11:04:11 frink ftpd[61865]: no modules loaded for `ftpd' service Dec 14 11:04:11 frink ftpd[61865]: auth_pam: Permission denied

Re: make world broken building fortunes

On 1999-Dec-13 20:42:36 +1100, Marcel Moolenaar <[EMAIL PROTECTED]> wrote: >Index: Makefile.inc1 >=== >RCS file: /home/ncvs/src/Makefile.inc1,v >retrieving revision 1.106 >diff -u -r1.106 Makefile.inc1 >--- Makefile.inc1 1999/12

Re: Broken sh(1): A more specific example

Warner Losh wrote: > > In message <[EMAIL PROTECTED]> Marcel Moolenaar writes: > : #!/bin/sh > : PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ > : /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\ > : /usr/games:/usr/local/bin:/usr/X11R6/bin:/home/marcel/bin ls > :

ESS1688 newpcm support, soundblaster panics at boot

I have an old, wheezing Dell Lattitude LM with an ESS1688 sound chip. (specs at http://support.dell.com/docs/systems/pespmmx/specs.htm) I have managed to get newpcm to find the 1688 via 'options PNPBIOS' and the following patch: Index: sys/dev/sound/isa/sbc.c ==

Re: Speaking of moving files (Re: make world broken building fortunes )

[Recipient list trimmed down to just the list. dhw] >Date: Tue, 14 Dec 1999 19:38:32 +0100 >From: Poul-Henning Kamp <[EMAIL PROTECTED]> > >It would make more sense, considering the way FreeBSD is distributed for >/usr/local to be a mountpoint than for /usr to be a mountpoint. It's hardly

Re: Broken sh(1): A more specific example

In message <[EMAIL PROTECTED]> Marcel Moolenaar writes: : #!/bin/sh : PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ : /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\ : /usr/games:/usr/local/bin:/usr/X11R6/bin:/home/marcel/bin ls : ls Isn't path not exported, so it

Re: Speaking of moving files (Re: make world broken building fortunes )

In message <[EMAIL PROTECTED]>, Matthew Dillon writes: > >I think at one time or another all of us have missed *something* in >/usr that wasn't in /. For example, disklabel -e doesn't work without >vi -- which is in /usr. EDITOR=/bin/ed export EDITOR disklabel

Re: Speaking of moving files (Re: make world broken building fortunes )

On Tue, 14 Dec 1999, Matthew Dillon wrote: > I think at one time or another all of us have missed *something* in > /usr that wasn't in /. For example, disklabel -e doesn't work without > vi -- which is in /usr. Good example of something else that would be great to have in /bin. *du

Re: Speaking of moving files (Re: make world broken building fortunes )

:> :> > So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with :> > just the root file system mounted? :> :> As one who just got his ass bitten by this, I would vote yes. : :As one who's missed chown at times when only root's mounted, I'm with Bill. : :-- : Ben Rosengart : :UN

Last ATA checkin broke the IDE drive on my Toshiba Portege

Got myself a Toshiba Portégé 3110CT last week. The IDE controller isn't recognized by the ata driver. It's an Intel(0x8086) with the device ID 0x7199. Until the last DMA related checkins by Søren, the drive was working in PIO mode. Now it says it's using DMA and after the "Mounting root from ...

Re: syscons extension: "propellers"

On Tue, Dec 14, 1999 at 02:42:52PM +0200, Sheldon Hearn wrote: > On Tue, 14 Dec 1999 13:56:45 +0200, Sheldon Hearn wrote: > > > YES! This comes up at least once a month on the -questions mailing > > list. :-) > > I should have been more specific. People are dead keen on these two > features: >

Re: syscons extension: "propellers"

On Tue, Dec 14, 1999 at 12:40:34PM +0100, Oliver Fromme wrote: > By the way, is there interest in giving the "Print Screen" > key an appropriate meaning, i.e. capturing a screenshot? > I have a few patches for this to implement that, I'd just > have to clean the code up and write a bit of document

Re: Speaking of moving files (Re: make world broken building fortunes )

On Mon, 13 Dec 1999, Bill Fumerola wrote: > On Mon, 13 Dec 1999, Louis A. Mamakos wrote: > > > So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with > > just the root file system mounted? > > As one who just got his ass bitten by this, I would vote yes. As one who's missed

PCM/AD1816

Hi. Would someone please fix recording for the Ad1816 chip in the newpcm code ? (the problem is, that the dma is started on the wrong channel, because the channel number is not initialized during setup.) I've already sent a patch to the maintainer but it seems he didn't like it. -- German Tisch

Re: configure problems

On Tue, Dec 14, 1999 at 05:00:14PM +0100, Pascal Hofstee wrote: > I have noticed some weird problems lately when running configure-scripts. > E.g. when trying to build the gtk12-port configure just hangs waiting for Please repost this in [EMAIL PROTECTED] as that is the proper list for ports-rela

configure problems

Hi, I have noticed some weird problems lately when running configure-scripts. E.g. when trying to build the gtk12-port configure just hangs waiting for "conftest" to finish (which never seems to do so). I have noticed similair problems with other configure checks (e.g. SDL). Is this a known is

sh(1) broken caching [was: Re: Broken sh(1)?]

Sheldon Hearn wrote: > > On Tue, 14 Dec 1999 15:42:11 +0100, Marcel Moolenaar wrote: > > > > You set all those variables for the first make command, but not for the > > > second. What did you expect to happen? > > > > That make(1) would execute. > > But what was the PATH set to _before_ you se

Re: Broken sh(1)?

Sheldon Hearn wrote: > > On Tue, 14 Dec 1999 14:30:59 +0100, Marcel Moolenaar wrote: > > > #!/bin/sh -ev > > cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386 \ > > PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ > > /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:

Re: Broken sh(1): A more specific example

Sheldon Hearn wrote: > > On Tue, 14 Dec 1999 14:48:51 +0100, Marcel Moolenaar wrote: > > > #!/bin/sh > > PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ > > /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\ > > /usr/games:/usr/local/bin:/usr/X11R6/bin:/home/marcel/bi

Re: Broken sh(1)?

On Tue, 14 Dec 1999 14:30:59 +0100, Marcel Moolenaar wrote: > #!/bin/sh -ev > cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386 \ > PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ > /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\ > /usr/games:/usr/local/bin:/usr

Re: Broken sh(1): A more specific example

On Tue, 14 Dec 1999 14:48:51 +0100, Marcel Moolenaar wrote: > #!/bin/sh > PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ > /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\ > /usr/games:/usr/local/bin:/usr/X11R6/bin:/home/marcel/bin ls > ls What do you think the s

Broken sh(1)?

Hi, Try the following shell script (taken from a buildworld): #!/bin/sh -ev cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386 \ PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\ /usr/games:/usr/local/bin:/usr/X11R6/bi

Broken sh(1): A more specific example

Just try: #!/bin/sh PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:\ /usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:\ /usr/games:/usr/local/bin:/usr/X11R6/bin:/home/marcel/bin ls ls I get: scones% ./y.sh COPYRIGHT etc share CVS

Re: syscons extension: "propellers"

> > One potential drawback is that it would probably bloat the > syscons code slightly. > > - Donn > Uhh... "slightly"? - Dave R. - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: syscons extension: "propellers"

On Tue, 14 Dec 1999, Donn Miller wrote: > Oliver Fromme wrote: > > > Actually, I was thinking about that myself. But the problem > > is that the code is very closely integrated into the existing > > syscons code (with a lot of #ifdef's, of course). > > I think another way (instead of ifdefs) w

Re: syscons extension: "propellers"

"Jordan K. Hubbard" wrote: > Indeed, so I'd also suspected and more the reason to do so, > right? It would make possible many other types of "dashboard" > controls as well. Skins for syscons! I can see it now! Haha! > [he laughs hysterically as several burly guys in white medical > gowns leap

Re: Speaking of moving files (Re: make world broken building fortunes )

On Mon, 13 Dec 1999, Louis A. Mamakos wrote: > So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with > just the root file system mounted? How about removing awk from MAKEDEV so life isn't so hard to recover when you use a 3.3 fixit floppy after removing /dev and not making eno

Re: syscons extension: "propellers"

On Tue, 14 Dec 1999 13:56:45 +0200, Sheldon Hearn wrote: > YES! This comes up at least once a month on the -questions mailing > list. :-) I should have been more specific. People are dead keen on these two features: 1) dump an ascii capture of the screen to a file. 2) dump t

Re: syscons extension: "propellers"

Oliver Fromme wrote: > Actually, I was thinking about that myself. But the problem > is that the code is very closely integrated into the existing > syscons code (with a lot of #ifdef's, of course). I think another way (instead of ifdefs) would be to provide some hooks into syscons, so that the

Re: syscons extension: "propellers"

On Tue, 14 Dec 1999 12:40:34 +0100, Oliver Fromme wrote: > By the way, is there interest in giving the "Print Screen" > key an appropriate meaning, i.e. capturing a screenshot? YES! This comes up at least once a month on the -questions mailing list. :-) Ciao, Sheldon. To Unsubscribe: send

Re: syscons extension: "propellers"

> I have never programmed a KLD before (though I will have a > look into this when I have some spare time left), but it is > my understanding that KLDs are appropriate for parts of the > kernel which can be reasonably easy separated from the rest > of the kernel. This is not the case for the prop

Re: syscons extension: "propellers"

> By the way, is there interest in giving the "Print Screen" > key an appropriate meaning, i.e. capturing a screenshot? > I have a few patches for this to implement that, I'd just > have to clean the code up and write a bit of documentation. > The GIF on the above webpage was created that way (alo

Re: syscons extension: "propellers"

Jordan K. Hubbard wrote in list.freebsd-current: > > Just in case somebody is curious, here's a screenshot: > > http://www.fromme.com/propellers/ > > That looks very interesting... It's just screaming for some kind of > mechanism which allows you to kldload the propeller code in as an > ex

Re: join the mailing-list

Not this way. Send email to "[EMAIL PROTECTED]" with the following two lines in the body of the message: subscribe freebsd-current subscribe cvs-all You should consider this action very carefully as you will start receiving approximately 200 messages each day. I would suggest that you only su

Re: make world broken building fortunes

Peter Wemm wrote: > > I wonder if we should move fortune to usr.bin? It's hardly a game and I'm > way beyond tired of it being left out of standard paths... > (ie: "/bin:/usr/bin[:/usr/local/bin]") After letting this go through my head for a day (it probably isn't important anymore :-), I think

Re: sysinstall: is it really at the end of its lifecycle?

At 1:49 AM -0800 1999/12/14, Jordan K. Hubbard wrote: > Sure, I can hear you yelling at those > novices from here: "JUST SWITCH TO THE OTHER VTY AND *LOOK*, YOU > CHEESEHEADS!", but it's never that simple. Yup, this is me. Been there, done that many t

Re: RELEASE timelines

Yes 2.x went on for too long but I was counting 2.2.x as the equivalent of 3.x due to the change in the release schedule (mainly just a change in the numberring). The thing that worries me is the bad reputation that comes from releasing not quite ready releases. Basically the real way to run Fre

Re: syscons extension: "propellers"

> Just in case somebody is curious, here's a screenshot: > http://www.fromme.com/propellers/ That looks very interesting... It's just screaming for some kind of mechanism which allows you to kldload the propeller code in as an extention rather than linking it into the kernel. :) - Jordan To U

Re: syscons extension: "propellers"

I wrote in list.freebsd-current: > I have (long time ago) written some extensions to syscons, and > finally decided to clean them up, document and submit them. Just in case somebody is curious, here's a screenshot: http://www.fromme.com/propellers/ Regards Oliver -- Oliver Fromme, Leibniz

Re: sysinstall: is it really at the end of its lifecycle?

> As far as the successor to sysinstall goes, I think it would be > nice to have both a console version and an X version, with some X > tookit such as Lesstif or Qt, or Tcl/Tk. It could be a lot like > RedHat's "linuxconf", where you can use it as both an installer > or system administration tool

Re: sysinstall: is it really at the end of its lifecycle?

At 2:36 AM -0500 1999/12/14, Donn Miller wrote: > I saw in CUBFM (the newsgroup) where a couple of people wanted to > do a GUI menu-based interfaced to the kernel configuration (as > opposed to editing a file by hand). I don't think this would be > too hard at all, but I wondered what the ex

Re: sysinstall: is it really at the end of its lifecycle?

"Jordan K. Hubbard" wrote: > All true, I'm afraid. All I can say is that efforts to revive the > effort to replace sysinstall are underway and we're even trying to > throw some money-shaped darts at the problem in hopes that we'll hit > something. I'm cautiously pessimistic, so we'll see. :)

  1   2   >