-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>ive been working on a pair of test boxes today, and 2 daemons in a
row,
>have installed from ports without the .sh on the end of their
startup
>script.
>
>ive done tons of installs on these test boxes, what am i all of a
>sudden
>doing wrong? the onl
Jonathan Horne wrote:
well if its an official change in procedure, i have no problem with
adapting. the reason it raised my eyebrow today, aside from happening on
2 boxes at the same time, same daemons, but vsftpd did the same thing last
weekend when i compiled the port after latest cvsup. vsf
Jonathan Horne wrote:
"Jonathan Horne" <[EMAIL PROTECTED]> writes:
ive been working on a pair of test boxes today, and 2 daemons in a row,
have installed from ports without the .sh on the end of their startup
script.
ive done tons of installs on these test boxes, what am i all of a sudde
> "Jonathan Horne" <[EMAIL PROTECTED]> writes:
>
>> ive been working on a pair of test boxes today, and 2 daemons in a row,
>> have installed from ports without the .sh on the end of their startup
>> script.
>>
>> ive done tons of installs on these test boxes, what am i all of a sudden
>> doing wro
"Jonathan Horne" <[EMAIL PROTECTED]> writes:
> ive been working on a pair of test boxes today, and 2 daemons in a row,
> have installed from ports without the .sh on the end of their startup
> script.
>
> ive done tons of installs on these test boxes, what am i all of a sudden
> doing wrong?
Not
ive been working on a pair of test boxes today, and 2 daemons in a row,
have installed from ports without the .sh on the end of their startup
script.
ive done tons of installs on these test boxes, what am i all of a sudden
doing wrong? the only thing im doing different is (what i thinkn is just)
