Re: Locked out - need a little help (caution: n00b meter on high!)
: :Yeah, I was stupid. I have set the default shell to /usr/pkg/bin/bash :and started an upgrade of packages in the evening which has removed bash :as well, obviously. All would have been good if DragonFly didn't spit :out some race error (v 1.5.4 yet, was just about to start :buildworld/buildkernel for 1.6.0, of course I cannot report it :-P) :making the build processes fail somewhere, leaving me with no bash :installed but bash as default shell for my root account and regular :account as well. If I follow the instructions at :http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#FORGOT-ROOT-PW : :, then when I chsh, vi does not display things properly (will fiddle :around with this later of course, if I cannot help it any other way, I'm :just in a hurry now), so I cannot edit the info. All I could find out is :to get the bash package written to some removable medium and install it :from there. Is there some other, simpler way - perhaps involving the livecd? copy /bin/csh to /usr/pkg/bin/bash temporarily and you should be able to then fix up your shell. -Matt Matthew Dillon <[EMAIL PROTECTED]>
Re: Asynchronous Console Messages?
:Hi everyone, : :I've always been a little curious about the way the typical unix :console works. Why is it that applications must wait for text to be :displayed on the console before continuing operation? Shouldn't these :messages merely enter into a queue to be displayed whenever the system :can get to them instead of slowing things down to the maximum speed :they can be output? : :Perhaps I'm mistaken about this issue :) -- and I'm certain that if :I'm not there's a reason for it working the way it does. I wouldn't :mind knowing the reason, though! : :Best Regards, :Ben Cadieux Well, any console I/O from user processes will be buffered just like normal tty I/O, but a tty buffer is fairly small (e.g. 256 bytes or so). However, the actual interaction with the console device is going to depend heavily on whether the console is video or a serial port. A video console isn't actually an I/O device in that the cpu can't just queue data to it and have some piece of hardware handle the actual writing out to the console. The kernel has to write the data directly into video memory. Since the video memory on a PC is typically mapped either through the internal (and very slow) ISA bridge or via the PCI bus, writing to it is not as fast as writing to normal memory. Performance isn't terrible, though, since the kernel typically maps the memory with hardware caching enabled on the video mapped pages. A serial console is an I/O device and a standard user program writing to it will buffer just as it would to a normal serial port. The program will stall only if the buffer fills up. printf()'s made by the kernel are going to be synchronous no matter what because the console has to be able to handle the printf() being called from anywhere, including interrupt code. This can result in a serious slow down especially over a serial console but I don't see that we have much of a choice in the matter because vital information can be lost (e.g. just prior to a crash) if it isn't synchronous. -Matt Matthew Dillon <[EMAIL PROTECTED]>
Re: Locked out - need a little help (caution: n00b meter on high!)
On Sun, Jul 30, 2006 at 07:53:22AM -0600, Gergo Szakal wrote: > Yeah, I was stupid. I have set the default shell to /usr/pkg/bin/bash > and started an upgrade of packages in the evening which has removed bash > as well, obviously. All would have been good if DragonFly didn't spit > out some race error (v 1.5.4 yet, was just about to start > buildworld/buildkernel for 1.6.0, of course I cannot report it :-P) > making the build processes fail somewhere, leaving me with no bash > installed but bash as default shell for my root account and regular > account as well. If I follow the instructions at > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#FORGOT-ROOT-PW > > , then when I chsh, vi does not display things properly (will fiddle > around with this later of course, if I cannot help it any other way, I'm > just in a hurry now), so I cannot edit the info. All I could find out is > to get the bash package written to some removable medium and install it > from there. Is there some other, simpler way - perhaps involving the livecd? Since the n00b meter was pegged, I'm assuming you don't know about manual pages: 'man chsh' could have helped you figure this out: chsh -s /bin/sh --Peter pgp9NRgbRxBFa.pgp Description: PGP signature
Re: Locked out - need a little help (caution: n00b meter on high!)
On Sunday, July 30, 2006 06:53am, Gergo Szakal wrote: > Yeah, I was stupid. I have set the default shell to /usr/pkg/bin/bash > and started an upgrade of packages in the evening which has removed bash > as well, obviously. All would have been good if DragonFly didn't spit > out some race error (v 1.5.4 yet, was just about to start > buildworld/buildkernel for 1.6.0, of course I cannot report it :-P) > making the build processes fail somewhere, leaving me with no bash > installed but bash as default shell for my root account and regular > account as well. If I follow the instructions at > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#FORGOT-ROOT >-PW > > , then when I chsh, vi does not display things properly (will fiddle > around with this later of course, if I cannot help it any other way, I'm > just in a hurry now), so I cannot edit the info. All I could find out is > to get the bash package written to some removable medium and install it > from there. Is there some other, simpler way - perhaps involving the > livecd? Easiest would probably be "cp /bin/sh /usr/pkg/bin/bash" -Spearow
qt3-tools make error
Im trying to compile qt3-tools from pkgsrc-current and get this error. /usr/libexec/binutils215/elf/ld: cannot find -lXcursor Im not sure if this is a bug or its related to when pkgmanager made hell of lot of mess of my packages a while ago. Well anyway, can i have clues how to fix it? Cheers, Petr
Re: Locked out - need a little help (caution: n00b meter on high!)
On Sun, Jul 30, 2006 at 07:53:22AM -0600, Gergo Szakal wrote: > Yeah, I was stupid. I have set the default shell to /usr/pkg/bin/bash > and started an upgrade of packages in the evening which has removed bash > as well, obviously. All would have been good if DragonFly didn't spit > out some race error (v 1.5.4 yet, was just about to start > buildworld/buildkernel for 1.6.0, of course I cannot report it :-P) > making the build processes fail somewhere, leaving me with no bash > installed but bash as default shell for my root account and regular > account as well. If I follow the instructions at > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#FORGOT-ROOT-PW > > , then when I chsh, vi does not display things properly (will fiddle > around with this later of course, if I cannot help it any other way, I'm > just in a hurry now), so I cannot edit the info. All I could find out is > to get the bash package written to some removable medium and install it > from there. Is there some other, simpler way - perhaps involving the livecd? If chsh works, you should be able to change the login shell by # chsh -s /bin/sh without $EDITOR. Cheers.
Locked out - need a little help (caution: n00b meter on high!)
Yeah, I was stupid. I have set the default shell to /usr/pkg/bin/bash and started an upgrade of packages in the evening which has removed bash as well, obviously. All would have been good if DragonFly didn't spit out some race error (v 1.5.4 yet, was just about to start buildworld/buildkernel for 1.6.0, of course I cannot report it :-P) making the build processes fail somewhere, leaving me with no bash installed but bash as default shell for my root account and regular account as well. If I follow the instructions at http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#FORGOT-ROOT-PW , then when I chsh, vi does not display things properly (will fiddle around with this later of course, if I cannot help it any other way, I'm just in a hurry now), so I cannot edit the info. All I could find out is to get the bash package written to some removable medium and install it from there. Is there some other, simpler way - perhaps involving the livecd?
Re: Asynchronous Console Messages?
Ben Cadieux wrote: Hi everyone, I've always been a little curious about the way the typical unix console works. Why is it that applications must wait for text to be displayed on the console before continuing operation? Shouldn't these messages merely enter into a queue to be displayed whenever the system can get to them instead of slowing things down to the maximum speed they can be output? Perhaps I'm mistaken about this issue :) -- and I'm certain that if I'm not there's a reason for it working the way it does. I wouldn't mind knowing the reason, though! Best Regards, Ben Cadieux Historically, the Unix 'console' was most often a DEC Writer, ASR-3X TTY, or 'glass teletype' (ADM-3, SOROQ IQ-120, Televideo 9XX, scads of others) 'dumb' serial terminal - and these, or modern equivalents, are still supported. In our case, we use a few carefully preserved HP-200LX - easy to carry on interncontintal flights, pass though customs in paranoid countries, and usable as 130-column VT-XX terminals - with special eyeglasses.. ;-) Awaiting a hardware or software handshake (RTS/CTS, ACK/NACK, etc) OTOH, is NOT ordinarily required, and a default VGA or other 'virtual' consle doesn't necessarily even have the concept (where you can adjust it, anyway). For the most part, the initiation activities reported to the 'console' are, in fact, already being 'buffered' or otherwise free-running with respect to the underlying progress of the activity being reported. Ordinarily, these are neither constrained by the speed of the I/O device, nor stalled awaiting handshake or response - though such may be provided for, and can be useful in certain types of troubleshooting. The 'delays' are far more often those required by dependencies and sub, and sub-sub dependencies - most, but not all, of which are also reported. IOW - they won't change, regardless of the bahaviour of the console, or if it is beong pipeld to, for example, /var/log/all or /var/log/console.log instead of/as well as a console I/O animal. A few examples: - There are a great many things that must complete before a Unix system is able to leave the 'single user' mode it uses for booting and enter 'multiuser'. Mounting (or not) whatever is in ~/etc/fstab among the most obvious. - *many* of the other 'basics', such as bringing up a NIC, testing that there is a cable and a working TCP/IP connection, finding the gateway and DNS servers, etc. - must run to sucessful full/partial completion, ELSE time-out before other services will attempt to start. SSHD, for example, ordinarily implies 'multiuser' mode, AND must have a means of communication if it is to be of any use. - *most* applications require that their storage be available, so fsck'ing a large HDD can delay most anything that either lives on a given resource, or calls other applications/libraries that do so. We start massive RAID arrays separately from ~/etc/fstab in ~/etc/rc.d scripts, so as to get a server into an ssh-capable state more rapidly after a reboot - even if this means soem of its public-facing services are NOT yet available. - So too with applications that relay on other applications as prerequisites. A couple of easy ways to satisfy your curiosity on these include: - entering a non-available mount into ~/etc/fstab (thereby stalling in single-user mode, incapable of running ssh, so do this on a box you can 'reach' physically, not a remote one!) - disconnecting the CAT5 ethernet cable during bootup, and connecting it much later. Some services will find it 'late' and initialize, others will not. - specifying an unreachable network time server, thereby creating a failrly long time-out. In some cases, you can enter a when the relevant message appears and proceed more quickly - the daemon may or may not initialize later, and you may or may not proceed sucessfully to a multi-user runlevel. Note that the is not removing a console delay. It is aborting the attempt to start that particular process. Most of this behaviour is configurable in one or more places, preferably with overrides in boot, loader, or - of course - rc.conf and the content and sequencing of ~/etc/rc.d scripts. HTH, Bill Hacker
Asynchronous Console Messages?
Hi everyone, I've always been a little curious about the way the typical unix console works. Why is it that applications must wait for text to be displayed on the console before continuing operation? Shouldn't these messages merely enter into a queue to be displayed whenever the system can get to them instead of slowing things down to the maximum speed they can be output? Perhaps I'm mistaken about this issue :) -- and I'm certain that if I'm not there's a reason for it working the way it does. I wouldn't mind knowing the reason, though! Best Regards, Ben Cadieux
Re: Linux emulation and acroread 7
Hi, I got it to work, I actually had different acroread installed, and not via pkgsrc. Sorry, my fault. Petr YONETANI Tomokazu wrote: On Sat, Jul 29, 2006 at 12:58:36PM +1000, Petr Janda wrote: uname -p reports 'i386'. Problem must be somewhere in the script. I'd try the following sequences of commands to find where it's failing: [elevator] ~% sh $ type acroread /usr/pkg/bin/acroread $ sh -x /usr/pkg/bin/acroread 2>&1 |tail -n30 $ exit Cheers. walt wrote: On Fri, 28 Jul 2006, Petr Janda wrote: Linux emulation is installed, but I get this when I run acroread. [elevator] ~% acroread The OS named DragonFly version 1.7.0-DEVELOPMENT is currently not installed. acroread is just a shellscript. Reading the script leads me to suspect that 'uname -p' may print something funny on your machine. The script is looking for 'i386'.
jails starting/running from NFS completely
Hello! I did some quick tests with FreeBSD as NFS client and Linux as NFS server and it appears that they disagree on chflags. Also jailctl hates installing jails there as well. Would I have more luck with *BSD-based NFS server or is there something else about not running jails from NFS? I know that some applications are not NFS-friendly, but for simple web frontends NFS via GigE should provide decent performance. Tomaž
Re: Compaq Evo boot problem
On Fri, Jul 28, 2006 at 10:46:51AM -0400, Haidut wrote: > Yes, I followed this article and set everything to MAX PIO. It still > doesn't work and it's very annoying. BTW, to do give Dfly credit I > have to say that installing the latest FreeBSD version gives the same > error. This is a really embarassing bug for a modern operating system > to have. Of all things, the bootloader should be the most stable. And > the computer is not that old either. It's a P4 and both Linux and > Windows work on it like charm. Hmm, your problem looks more like this one: http://forums.devshed.com/bsd-help-31/installs-fine-but-won-t-boot-334343.html#post1543431 > On 7/27/06, YONETANI Tomokazu <[EMAIL PROTECTED]> wrote: > >On Thu, Jul 27, 2006 at 07:42:32PM -0400, Haidut wrote: > >> Hi all, > >> > >> I installed Dfly on a Compaq Evo desktop and when I try to boot from > >> the HDD I get several lines of cryptic messages in hex and then a line > >> withe text "BTX halted". > >> I found some posts on the Internet saying that *BSD have problem > >> booting on some Compaq machines but none of the posts offered > >> conclusive advice. Some advices were to change the HDD settings in the > >> BIOX to "MAX PIO" and I did that but still the same error. I saw a > >> post on the Dfly list from back in 2004 with the same problem but > >> nobody responded to that person. Any clues on how to fix this? > > > >Hi, the following article seems to suggest that you need to > >disable DMA for CD-ROM and other things too, not just HDD, > >did you tried that? > >http://lists.freebsd.org/pipermail/freebsd-hardware/2003-July/000418.html > > > >Cheers. > >
Re: Linux emulation and acroread 7
On Sat, Jul 29, 2006 at 12:58:36PM +1000, Petr Janda wrote: > uname -p reports 'i386'. Problem must be somewhere in the script. I'd try the following sequences of commands to find where it's failing: [elevator] ~% sh $ type acroread /usr/pkg/bin/acroread $ sh -x /usr/pkg/bin/acroread 2>&1 |tail -n30 $ exit Cheers. > walt wrote: > >On Fri, 28 Jul 2006, Petr Janda wrote: > > > > > >>Linux emulation is installed, but I get this when I run acroread. > >> > >>[elevator] ~% acroread > >>The OS named DragonFly version 1.7.0-DEVELOPMENT is currently not > >>installed. > >> > > > >acroread is just a shellscript. Reading the script leads me to suspect > >that 'uname -p' may print something funny on your machine. The script > >is looking for 'i386'. > > > > > > > > >
string missing in fonts.conf in linux runtime
There is a string missing in .../etc/fonts.conf in linux run-time. The appropriate package should have a string like: /usr/pkg/xorg/lib/X11/fonts added, for the linux gui apps to "see" at least all the default locations of fonts installed in the complete system. ---
[Fwd: cvs commit: src/etc Makefile src/sbin/brconfig Makefile brconfig.8 brconfig.c]
FYI: i've removed brconfig in -DEVEL. Be sure to switch to ifconfig before you upgrade. cheers simon Original Message Subject: cvs commit: src/etc Makefile src/sbin/brconfig Makefile brconfig.8 brconfig.c Date: Sat, 29 Jul 2006 05:11:12 -0700 (PDT) From: Simon Schubert <[EMAIL PROTECTED]> To: commits@crater.dragonflybsd.org corecode2006/07/29 05:11:12 PDT DragonFly src repository Modified files: etc Makefile Removed files: sbin/brconfigMakefile brconfig.8 brconfig.c Log: Retire brconfig. Its functionality is covered in ifconfig. Revision ChangesPath 1.122 +2 -0 src/etc/Makefile http://www.dragonflybsd.org/cvsweb/src/etc/Makefile.diff?r1=1.121&r2=1.122&f=u -- Serve - BSD +++ RENT this banner advert +++ASCII Ribbon /"\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \ signature.asc Description: OpenPGP digital signature
Re: PF version
Gergo Szakal wrote: Hello, I noticed that PF version is the one that was released with OpenBSD 3.7. Is there any chance that it will be synchronized with upstream soon? There are a few cool features in new versions that I'd like to try out on DF as well. Oh, and I would like to get rid of OBSD as well. ;-) i started with an update and already merged the openbsd sources, but this resulted in >300kb diffs which need to be checked and adjusted carefully. unfortunately my time is limited by nature and i can't multiplex myself either :) so does anybody want to take a shot? i'd help out if questions arise. cheers simon -- Serve - BSD +++ RENT this banner advert +++ASCII Ribbon /"\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \ signature.asc Description: OpenPGP digital signature
PF version
Hello, I noticed that PF version is the one that was released with OpenBSD 3.7. Is there any chance that it will be synchronized with upstream soon? There are a few cool features in new versions that I'd like to try out on DF as well. Oh, and I would like to get rid of OBSD as well. ;-)
Re: bmake xorg-xserver fails
On Fri, 28 Jul 2006 17:37:18 +0200, christian hennig wrote: I found that building CVS XFree86 failed. (http://www.xfree86.org/) A few weeks ago it said something about a null string. Since that knows nothing of DragonflyBSD, there is a high chance that no fix was made. BSD make recurses and it is not clear what it is doing. (One bug was that make was not passing debug options to itself, when recursing. Craig Carey New Zealand
