i am thinking there is a flaw in the ANSI code,
and this program demonstrates this 'flaw'. when
the 'inverse' attribute is set on the ANSI color
string, the 'clear to EOL' ANSI string does so
without respect to the 'inverse' attribute.
for example:
NORMAL
Foreground=White
Background=Red
CLEAR-TO
FBSD 4.9R
is there anyway to route PC speaker sounds to my sound card?
specifically, my PC speaker is fried, and i would like to
hear "ytalk" beeps thru my sound card ...
thanks (please copy any replies off-list).
___
[EMAIL PROTECTED] mailing list
http
FBSD 4.10
$ burncd -s4 -f/dev/cdrom erase
erasing CD, please wait..
burncd: ioctl(CDRIOCBLANK): Device busy
everyone seems to have this problem, and i have had it myself
for years. most times, powering off/on fixes it - but if that
is a satisfactory fix for FBSD - i may as well use MS Windows.
FBSD 4.10
CREATIVE CDRW
acd0: CD-RW at ata1-master PIO4
after rebooting and power down and spending more time trying to
trick the CDRW into doing something, i finally tried:
$ burncd -f /dev/acd0 erase file.iso
the 'file.iso' seemed to force 'burncd' to
do something - eg - make the CD light bli
FBSD 4.10
keywords: burncd cdrw 700 650 device busy
i have had seemingly inconsistent problems/errors with 'burncd',
and i exhausted myself on it the past few days trying to prepare
a bunch of CD sets.
to possibly prevent others from struggling, this is some
information i have found which may be
say i have 2 scripts, scriptA and scriptB.
scriptA
---
#!/bin/sh ./scriptB 1 2 3
scriptB
---
#!/bin/sh
echo 0:$0
echo 1:$1
echo 2:$2
echo 3:$3
--
$ ./scriptA
$0:./scriptB
$1:1
$2:2
$3:3
--
according to execve(2), only a single [arg] should be recognized:
#! interpreter [arg]
this does seem to be an ambiguous area.
it seems more sane to allow arguments
to a script given to an interpreter on the
shebang line, passing everything after
"#!/interpreter [arg]" off for
"eval" or "sh -c" type parsing.
i don't know how it breaks anything to load execve's argv[]
with everythin
> > it seems more sane to allow arguments to a script given to an
> > interpreter on the shebang line, passing everything after
> > "#!/interpreter [arg]" off for "eval" or "sh -c" type parsing.
>
> This is something that can be bth good and bad though. As you have
> pointed out, if a limited sort
minor correction/addition to previous post:
instead of "infinitely recursive", i should've
said that it would break things if "script"
re-exec's the same file with a
different interpreter.
--
> #!/bin/sh
> . script
this won't work if "script" is going to do something
before exec'ing
i would like to know if "USB auto-connect" "Universal Mass Storage"
drivers plan to be fully functional at the end of the 4.x FBSD
release development. it is my experience that the drivers
are functionally broken in many instances, and it is my
understanding that these are published "standards",
> the umass(4) drivers work perfectly for me and my digital camera and
> smartmedia cardreader.
>
> what isn't working for you?
>
> -Adam
i had an Olympus D-150, it only worked once per boot/mount
(would not mount after a umount unless kernel was rebooted),
currently i have a Toshiba PDR-M25, w
i would like to know if there exists any fix for my problem here:
problem: apps like XV and MPEG_PLAY refused to open dialogs/windows
in any "virtual window" other than the one containing the "origin"
in window managers that support them (VTWM in my case).
this really sucks, since
FBSD 4.7R
-
the following appears to be different behavior than i have
experienced in the past, and somewhat unusual. please reply
off list as well if you reply.
$ startx &
is the command above supposed to operate like ^Z (suspend)?
i would not think so. i would think that such commands
FBSD-4.7R
on other BSD's, and with ftp(1), 'cd x*' will cd
to the 1st match. FBSD used to work this way
as well a few minor versions ago.
these days it crashes with 'too many arguments'
if there is more than one match. i 'object'
to this behavior :) i would like to report
it as a bug ... is t
> > the method used by FBSD 2.2.7 seems the most sane to me,
> > where execve's argv[] is loaded by each whitespace
> > seperated element after the shebang,
> > then by command line options.
> >
> > 1. it is flexible.
> > 2. it functions intuitively.
> > 3. i don't think it breaks less flexible
> Maybe your ISP is blocking port 22 after all. nmap will tell you.
>
> -mackan
can nmap (which i don't have installed) tell me more
than telnet - as far as a where a specific IP/port packet
is being blocked/dropped?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questi
> > is there any way to determine which machine along
> > a route is dropping packets destined for a specific
> > IP/port combination?
> >
> > i can't SSH to my gateway from machines elsewhere
> > on the internet, but i can ssh to it on a local net.
> >
> > i can ssh to other machines elsewhere on
> > > Maybe your ISP is blocking port 22 after all. nmap will tell you.
> > >
> >
> > can nmap (which i don't have installed) tell me more
> > than telnet - as far as a where a specific IP/port packet
> > is being blocked/dropped?
> >
>
> If you mean where along the path it is getting dropped, no.
can someone tell me how to stop FreeBSD (4.11) from
turning off my monitor (after whatever preset timeout
there is)?
it's messing my monitor up because it takes my monitor
about an hour to stabilize the display after being
turned off - and i can't afford a new monitor right now.
until it is "warme
FBSD 4.8
i hope this isn't a question based on extreme
ignorance - i haven't programmed in C in a
long time, and i don't have another machine
to test this on. i can't understand why
the output of the following code produces
"ints" when given variables of type "char",
so it looks like a bug to me
i am trying to develop terminal I/O based code,
and found myself meandering down a path
to acquire terminal knowledge (i don't
need to be told of SLang/ncurses/...).
i can't readily find an answer to this, but
i am assuming DEC terminals don't scroll left/right?
i've never used a "terminal", so i
http://www.freebsd.org/mailto.html
Questions regarding FreeBSD should be addressed to the FreeBSD
Questions mailing list, [EMAIL PROTECTED]
Mailing lists are the primary support channel for FreeBSD users, with
numerous mailing lists covering different topic areas. Several
non-Engli
> [EMAIL PROTECTED] wrote:
> [ ... ]
> > the basis for this question was to determine if it was
> > feasible to write a portable FBSD application and/or library
> > without external dependencies.
>
> You can write portable ANSI-C code using the STDIO routines, without external
> dependencies upon
> You don't think you're alone because you've Googled a lot?
heh :)
> > namely, i am not happy with the current selection of text editors
> > (i find joe(1) to be very good, but it's got some problems and
> > is aging without good development),
> 136-sec# ls /usr/ports/editors | wc -l
>
Re:Starting with Unix (Score:4, Insightful)
by spitzak (4019) on Sunday April 27, @01:18PM (#5819797)
(http://www.cinenet.net/~spitzak)
Terminal driver design is certainly a stupid part of Unix. Back when this was
written there certainly was a serious mess of terminals which would actually
fail no
i am just trying to understand. there are things i don't like, and want to do
better. i don't know where else to learn, i do search and read and study
whatever i can. i do read with intent to learn. it appears to come down to
an argument of:
support everything ever made in the world
or otherwis
i was downloading 7.0-RELEASE,
and found the following MD5 errors:
doc/
ERROR: MD5 (doc.cc) = a83976995e055dbe67030397902c5ab9
MD5SUM MD5 (doc.cc) = 662363b086db1164eb922024428df2df
ERROR: MD5 (install.sh) = 0ddd67ac6a0ca00e0131f63bcde9b145
MD5SUM MD5 (install.sh) = a1f597bcc955e069fd6679ea4a543d
i have an ML6000 (no floppy) and have downloaded
the 4.11 mini-iso image, and burned it to a CD-RW.
CPU: VIA C3 Nehemiah (666.55-MHz 686-class CPU)
after rebooting, the CD is found, and a boot
attempt is made. within 5 seconds, the kernel
locks up after about 3 seconds of the
kernel data+234238
i just installed 4.6-RELEASE, and notice that
the '2>&-' sh (FBSD) construct seems to be broken.
i am going thru all my scripts having to change
it to /dev/null ...
i figure it's not realistic to assume a bug this
obvious would make it to release stage, so my
question is - is something else going
> > i just installed 4.6-RELEASE, and notice that
> > the '2>&-' sh (FBSD) construct seems to be broken.
> > i am going thru all my scripts having to change
> > it to /dev/null ...
> >
> > i figure it's not realistic to assume a bug this
> > obvious would make it to release stage, so my
> > quest
> > i just installed 4.6-RELEASE, and notice that
> > the '2>&-' sh (FBSD) construct seems to be broken.
> > i am going thru all my scripts having to change
> > it to /dev/null ...
> In what way is it broken?
> If the construct is generally used for hiding errormessages, one
> should probably r
> > > > i just installed 4.6-RELEASE, and notice that
> > > > the '2>&-' sh (FBSD) construct seems to be broken.
> > > > i am going thru all my scripts having to change
> > > > it to /dev/null ...
> > > If the construct is generally used for hiding errormessages, one
> > > should probably replace
32 matches
Mail list logo
