On Jun 23, 2012, at 12:11 PM, Devin Teske wrote:
>
> On Jun 22, 2012, at 5:27 AM, Clayton Milos wrote:
>
[snip]
>> Also it said that my user add failed but it was actually added as uid 1005.
>
> I'm working on this one. I'm changing the routines to allow the UNIX pw(8)
> errors to filter thr
On Jun 22, 2012, at 5:27 AM, Clayton Milos wrote:
>> 5. Same for vlan16. For vlan9 is shows right 'IEEE 802.1Q VLAN network
>> interface'.
>> It should work same way for vlan1-vlan4095 interfaces at least.
>>
>
> I'd like to know if the sysctl MIB's for describing networ
On Jun 22, 2012, at 3:44 PM, Devin Teske wrote:
>
> On Jun 22, 2012, at 3:32 PM, Devin Teske wrote:
>
>>
>> On Jun 22, 2012, at 5:27 AM, Clayton Milos wrote:
>>
>>>
>>> When selecting user account expiry the calendar starts at 1 January 1970. I
>>> understand that this is when Unix time star
On Jun 22, 2012, at 3:32 PM, Devin Teske wrote:
>
> On Jun 22, 2012, at 5:27 AM, Clayton Milos wrote:
>
>>
>> When selecting user account expiry the calendar starts at 1 January 1970. I
>> understand that this is when Unix time started but it would be nice for it
>> to start from the current d
On Jun 22, 2012, at 5:27 AM, Clayton Milos wrote:
>
> When selecting user account expiry the calendar starts at 1 January 1970. I
> understand that this is when Unix time started but it would be nice for it
> to start from the current date.
>
This was on-purpose because there is a discrepancy
> 5. Same for vlan16. For vlan9 is shows right 'IEEE 802.1Q VLAN network
interface'.
> It should work same way for vlan1-vlan4095 interfaces at least.
>
I'd like to know if the sysctl MIB's for describing network interfaces
is reliable. Maybe I'll keep the static list as a fal
22.06.2012 15:39, Devin Teske wrote:
5. Same for vlan16. For vlan9 is shows right 'IEEE 802.1Q VLAN network
interface'.
It should work same way for vlan1-vlan4095 interfaces at least.
>>>
>>> I'd like to know if the sysctl MIB's for describing network interfaces is
>>> reliab
On Jun 22, 2012, at 12:53 AM, Eugene Grosbein wrote:
> 22.06.2012 14:37, Devin Teske пишет:
>
>>> 5. Same for vlan16. For vlan9 is shows right 'IEEE 802.1Q VLAN network
>>> interface'.
>>> It should work same way for vlan1-vlan4095 interfaces at least.
>>>
>>
>> I'd like to know if the sysctl
22.06.2012 14:37, Devin Teske пишет:
>> 5. Same for vlan16. For vlan9 is shows right 'IEEE 802.1Q VLAN network
>> interface'.
>> It should work same way for vlan1-vlan4095 interfaces at least.
>>
>
> I'd like to know if the sysctl MIB's for describing network interfaces is
> reliable. Maybe I'l
On Jun 22, 2012, at 12:07 AM, Eugene Grosbein wrote:
> 22.06.2012 10:50, Ron McDowell пишет:
>
>>> Again, thank you very much for testing this new software.
>>> P.S. Due to the large codebase comprising bsdconfig, ample precautions
>>> should be taken. I've not noticed any negative behavior in
22.06.2012 10:50, Ron McDowell пишет:
>> Again, thank you very much for testing this new software.
>> P.S. Due to the large codebase comprising bsdconfig, ample precautions
>> should be taken. I've not noticed any negative behavior in months of usage,
>> but just be warned.
>>
>> P.P.S. I don't
On 6/21/12 5:32 PM, Devin Teske wrote:
Hi everybody,
I've published a new port (sysutils/bsdconfig) so that we can get some testing on the
replacement for sysinstall's [post-installation] "Configure" menu.
We're on a tight schedule, so if you have the time and/or energy your timely
efforts wi
Sorry, forgot to mention…
The port will only install/work on 9.0 or higher.
Testing needed on FreeBSD 9.0-R (or higher) and/or PC-BSD 9.0-R (or higher).
--
Devin
On Jun 21, 2012, at 3:32 PM, Devin Teske wrote:
> Hi everybody,
>
> I've published a new port (sysutils/bsdconfig) so that we can
Hi everybody,
I've published a new port (sysutils/bsdconfig) so that we can get some testing
on the replacement for sysinstall's [post-installation] "Configure" menu.
We're on a tight schedule, so if you have the time and/or energy your timely
efforts will be GREATLY appreciated in helping to g
14 matches
Mail list logo
