to users that it be the default, with "rm"
reserved for special, extreme cases, then I think you will get the
desired result, with zero breakage of existing scripts & conventions.
Greg Shenaut
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ever
exec /your/program
The shell's environment will be exported to your program's environment.
Greg Shenaut
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
how to format drives, install
distributions & packages, and so on.
This "boot console" floppy would only need to change to support new
hardware, and there could even be boot-source-specific versions
of it. Once you had one that worked on a specific type of PC,
you cou
s to a high degree, because it is a good idea.
Has it ever been suggested to create one or more "dependencies"
ports (or more to the point, packages)? I think it might be pretty
useful to have something like that so that all of the "prerequisites"
c
to the environment. It only sets them in the
>local shell. Try the above where 'fred' is
> #!/bin/sh
> printenv
>and you'll see what I mean.
Try using the "set -a" command before reading rc.conf and
it will work:
#!/bin/sh
set -a
. /etc/rc.conf
exec yourprog
Greg Shenaut
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
rom within a C program.
One off the wall way:
#!/bin/sh
set -a
. /etc/rc.conf
exec /your/program
Greg Shenaut
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In message <[EMAIL PROTECTED]>,
David Nicholas Kayal cleopede:
>Shouldn't 0xff result in 5v outputs?
Sure, but in general you may get more information by using an
alternating bit pattern (aa/55), that's all.
Can you print from this port?
Greg Shenaut
To Unsubscribe:
random thought, it may not help here, but aa/ff are generally
more useful than all 1's or all 0's.
Greg Shenaut
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
read is extremely wrong of
>that is actually happening.
Too bad "strcmp" wasn't named "strdiff"--just think of all the hassle
that would have prevented over the years...
Greg Shenaut
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ned on.
> T1 line from TELCO was shorted to house ground.
> House wiring was NOT grounded, so house wiring found ground through T1!
Another one I've seen is that the building air conditioners all get
turned off at the end of the workday, and it takes a certain amount
of time be
his has actually been an issue for ages, most commonly seen with
>doubles. take a look at the thread at
Has any "real world" program ever been significantly affected by
this "problem"?
Greg Shenaut
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
k the limitation was that you couldn't
map a small piece of memory & share it among processes, only all
text or all data, but I admit my memory is almost gone, and I don't
remember PDP/11 architecture all that well either.
Greg Shenaut
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
wever, I do see the value in making it easier to have a faster,
more memory-intensive kernel, so why not just provide a "turbo
kernel" in the standard root distribution along with the current
"generic kernel"? Shoot, I think even casual, non kernel-configuring
users might be interest
lines? I'm thinking of the impact of realloc and memcpy
on speed.
Greg Shenaut
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
avoid the exploit. The system in our lab that was hacked
a while back was running 3.2, so the exploit definitely works on it.
Greg Shenaut
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
at most (not quite all) character sets in which 0xa0
is defined at all use it for unbreakable space. (But it is not
defined in 7-bit ASCII, which is the FreeBSD default.)
Greg Shenaut
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In message <[EMAIL PROTECTED]>, Giorgos Keramidas cleopede:
>Greg Shenaut <[EMAIL PROTECTED]> wrote:
>>
>> Just out of curiosity, what would be an instance where you have
>> wanted a space in a filename and wouldn't have been satisfied with
>> 0xa0 i
In message <[EMAIL PROTECTED]>, Giorgos Keramidas cleopede:
>Greg Shenaut <[EMAIL PROTECTED]> wrote:
>>
>> I just throw out the idea--as for where to enforce such a convention,
>> I agree that the file-system definition may not be the best place,
>> but
In message <[EMAIL PROTECTED]>, void cleopede:
>On Tue, Oct 02, 2001 at 07:19:37AM -0700, Greg Shenaut wrote:
>>
>> Is there any reason why the "unbreakable space" (0xa0) shouldn't be
>> the only kind of space character used/allowed in filenames?
>
ace in the middle, or not?
Is there any reason why the "unbreakable space" (0xa0) shouldn't be
the only kind of space character used/allowed in filenames?
Greg Shenaut
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
In message <200109301318.44290@EO>, Bart Kus cleopede:
>On Sunday 30 September 2001 12:47, Greg Shenaut wrote:
>> Well, setitimer has a maximum rate of 100 Hz, with a slop factor
>> sometimes much greater than 10 ms. This was the result of some
>> recent testing on a
one at a time, then
maybe the speaker port on the motherboard (a programmable counter-timer)
would be more reliable. Another idea is to use a fifo'ed UART's data out
line and fiddle with the baud rate to vary the speed of the pulses. And
one final idea is to use a (possibly port-po
22 matches
Mail list logo
