On Sun, Sep 9, 2012 at 8:00 PM, Warren Block wrote:
> On Sun, 9 Sep 2012, Kevin Oberman wrote:
>
>> On Sun, Sep 9, 2012 at 6:49 PM, Warren Block wrote:
>>>
>>> On Sun, 9 Sep 2012, Warren Block wrote:
>>>
On Sun, 9 Sep 2012, Kevin Oberman wrote:
> I added a label to my root fs some t
On Sun, 9 Sep 2012, Kevin Oberman wrote:
On Sun, Sep 9, 2012 at 6:49 PM, Warren Block wrote:
On Sun, 9 Sep 2012, Warren Block wrote:
On Sun, 9 Sep 2012, Kevin Oberman wrote:
I added a label to my root fs some time ago. I really prefer the gpt
label and I have added it, but I can't figure o
On Sun, Sep 9, 2012 at 6:49 PM, Warren Block wrote:
> On Sun, 9 Sep 2012, Warren Block wrote:
>
>> On Sun, 9 Sep 2012, Kevin Oberman wrote:
>>
>>> I added a label to my root fs some time ago. I really prefer the gpt
>>> label and I have added it, but I can't figure out how to remove the
>>> ufs la
On Sun, 9 Sep 2012, Warren Block wrote:
On Sun, 9 Sep 2012, Kevin Oberman wrote:
I added a label to my root fs some time ago. I really prefer the gpt
label and I have added it, but I can't figure out how to remove the
ufs label.
I boot single user and run 'tunefs -L "" /dev/ada1p2' but I get
On Sun, 9 Sep 2012, Kevin Oberman wrote:
I added a label to my root fs some time ago. I really prefer the gpt
label and I have added it, but I can't figure out how to remove the
ufs label.
I boot single user and run 'tunefs -L "" /dev/ada1p2' but I get an
"unable to write superblock" error. Thi
Hi,
On Sun, 9 Sep 2012 17:47:43 -0700
Kevin Oberman wrote:
> I added a label to my root fs some time ago. I really prefer the gpt
> label and I have added it, but I can't figure out how to remove the
> ufs label.
>
> I boot single user and run 'tunefs -L "" /dev/ada1p2' but I get an
> "unable t
I added a label to my root fs some time ago. I really prefer the gpt
label and I have added it, but I can't figure out how to remove the
ufs label.
I boot single user and run 'tunefs -L "" /dev/ada1p2' but I get an
"unable to write superblock" error. This is before mounting the drive
RW, but it is
I'm porting existing code from Linux where a connect() to an AF_UNIX socket
that exists, but does not have a listener, fails with ECONNREFUSED. This is
quite agreeable with the comparable scenario in AF_INET, with a connection
attempt to a port without a listener on it. So the same code handl
C. P. Ghost wrote:
> On Sun, Sep 9, 2012 at 1:26 PM, Helmut Schneider
> wrote:
> > Currently I'm updating ports and src twice a day so I will keep
> > using svn for both.
>
> While you certainly can, isn't it a bit excessive to update so
> frequently? Remember, it's not just fetching the source
On Sun, Sep 9, 2012 at 1:26 PM, Helmut Schneider wrote:
> Currently I'm updating ports and src twice a day so I will keep using
> svn for both.
While you certainly can, isn't it a bit excessive to update so frequently?
Remember, it's not just fetching the sources and ports, you must also
compile
On Sun, 9 Sep 2012 11:26:50 + (UTC), Helmut Schneider wrote:
> Polytropon wrote:
>
> > On Sun, 9 Sep 2012 10:37:03 + (UTC), Helmut Schneider wrote:
> > > Hi,
> > >
> > > I'm running a custom kernel so I (guess I) need svn in future to
> > > fetch sources instead of cvsup. Should I still u
Polytropon wrote:
> On Sun, 9 Sep 2012 10:37:03 + (UTC), Helmut Schneider wrote:
> > Hi,
> >
> > I'm running a custom kernel so I (guess I) need svn in future to
> > fetch sources instead of cvsup. Should I still use portsnap then
> > for ports or also fetch them via svn?
>
> Ports and syste
On Sun, 9 Sep 2012 10:37:03 + (UTC), Helmut Schneider wrote:
> Hi,
>
> I'm running a custom kernel so I (guess I) need svn in future to fetch
> sources instead of cvsup. Should I still use portsnap then for ports or
> also fetch them via svn?
Ports and system sources are managed independently
Hi,
I'm running a custom kernel so I (guess I) need svn in future to fetch
sources instead of cvsup. Should I still use portsnap then for ports or
also fetch them via svn?
Thanks, Helmut
___
freebsd-questions@freebsd.org mailing list
http://lists.freeb
14 matches
Mail list logo