FreeBSD bugmaster | 4 Apr 13:06 2011
Picon

freebsd-embedded@...

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
p misc/151696  embedded   [nanobsd] [patch] nanobsd.sh doesn't run "make_conf_bu
o misc/151695  embedded   [nanobsd] [patch] Enhance tools/nanobsd/fill_pkg.sh
o misc/136889  embedded   [nanobsd] [patch] nanobsd error reporting and other re
o misc/52256   embedded   [picobsd] picobsd build script does not read in user/s
o kern/42728   embedded   [picobsd] many problems in src/usr.sbin/ppp/*  after c

5 problems total.

Lev Serebryakov | 11 Apr 09:34 2011
Picon

Does somebody work on NanoBSD?

Hello, Freebsd-embedded.

  Does somebody work on NanoBSD? It was not MFCed for long time on one
hand, and on other hand, support of NANO_LABEL, added to CURRENT, is completely
broken and almost useless. Even my bugfix about make.conf (PR 151696,
SVNrev 215070) is only committed to CURRENT, but is not MFCed and is
not closed.

--

-- 
// Black Lion AKA Lev Serebryakov <lev@...>

Olivier Cochard-Labbé | 11 Apr 09:51 2011

Re: Does somebody work on NanoBSD?

2011/4/11 Lev Serebryakov <lev@...>:
> Hello, Freebsd-embedded.
>
>  Does somebody work on NanoBSD? It was not MFCed for long time on one
> hand, and on other hand, support of NANO_LABEL, added to CURRENT, is completely
> broken and almost useless.
>

Hi Lev,

I'm using the NANO_LABEL support, and I didn't have any problem.
What's your label problem with nanobsd precisely ?

Regards,

Olivier
http://bsdrp.net
Lev Serebryakov | 11 Apr 10:53 2011
Picon

Re: Does somebody work on NanoBSD?

Hello, Olivier.
You wrote 11 апреля 2011 г., 11:51:09:

>>  Does somebody work on NanoBSD? It was not MFCed for long time on one
>> hand, and on other hand, support of NANO_LABEL, added to CURRENT, is completely
>> broken and almost useless.
> I'm using the NANO_LABEL support, and I didn't have any problem.
> What's your label problem with nanobsd precisely ?
  (1) Copied out "upgrade" image has always ${NANO_LABEL}s1 label, and
needs manual mdconfig+tunefs before dumping on second code partition

  (2) updatep2 script uses sed 's/${NANO_DRIVE}s1/${NANO_DRIVE}s2/'
script, and if NANO_LABLE is in use (which sets NANO_DRIVE to
"ufs/labels1") sed complains.

--

-- 
// Black Lion AKA Lev Serebryakov <lev@...>

Olivier Cochard-Labbé | 11 Apr 11:07 2011

Re: Does somebody work on NanoBSD?

2011/4/11 Lev Serebryakov <lev@...>:
> Hello, Olivier.
> You wrote 11 апреля 2011 г., 11:51:09:

>  (1) Copied out "upgrade" image has always ${NANO_LABEL}s1 label, and
> needs manual mdconfig+tunefs before dumping on second code partition
>
>  (2) updatep2 script uses sed 's/${NANO_DRIVE}s1/${NANO_DRIVE}s2/'
> script, and if NANO_LABLE is in use (which sets NANO_DRIVE to
> "ufs/labels1") sed complains.
>

OK, I didn't see this problem because I'm using my own upgrade script
(I've merged update1 and update2 in one script):
http://bsdrp.svn.sourceforge.net/viewvc/bsdrp/trunk/Files/usr/local/sbin/upgrade

You could try to adapt it to your needs.

Regards,

Olivier
FreeBSD bugmaster | 11 Apr 13:06 2011
Picon

freebsd-embedded@...

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
p misc/151696  embedded   [nanobsd] [patch] nanobsd.sh doesn't run "make_conf_bu
o misc/151695  embedded   [nanobsd] [patch] Enhance tools/nanobsd/fill_pkg.sh
o misc/136889  embedded   [nanobsd] [patch] nanobsd error reporting and other re
o misc/52256   embedded   [picobsd] picobsd build script does not read in user/s
o kern/42728   embedded   [picobsd] many problems in src/usr.sbin/ppp/*  after c

5 problems total.

Warner Losh | 11 Apr 16:29 2011

Re: Does somebody work on NanoBSD?


On Apr 11, 2011, at 1:34 AM, Lev Serebryakov wrote:

> Hello, Freebsd-embedded.
> 
>  Does somebody work on NanoBSD? It was not MFCed for long time on one
> hand, and on other hand, support of NANO_LABEL, added to CURRENT, is completely
> broken and almost useless. Even my bugfix about make.conf (PR 151696,
> SVNrev 215070) is only committed to CURRENT, but is not MFCed and is
> not closed.

I have been working on it, but not actively merging it or tracking bugs...

I think I need to spend a little time on house-keeping.

Warner

Warner Losh | 11 Apr 16:30 2011

Re: Does somebody work on NanoBSD?


On Apr 11, 2011, at 1:51 AM, Olivier Cochard-Labbé wrote:

> 2011/4/11 Lev Serebryakov <lev@...>:
>> Hello, Freebsd-embedded.
>> 
>>  Does somebody work on NanoBSD? It was not MFCed for long time on one
>> hand, and on other hand, support of NANO_LABEL, added to CURRENT, is completely
>> broken and almost useless.
>> 
> 
> Hi Lev,
> 
> I'm using the NANO_LABEL support, and I didn't have any problem.
> What's your label problem with nanobsd precisely ?

I'd like to know the problem as well since FreeNAS uses it without any problems at all.  I don't believe
"completely broken" based on my first-hand experience, so maybe a better description of the problem
would help me fix it.

Warner

Warner Losh | 11 Apr 16:31 2011

Re: Does somebody work on NanoBSD?


On Apr 11, 2011, at 2:53 AM, Lev Serebryakov wrote:

> Hello, Olivier.
> You wrote 11 апреля 2011 г., 11:51:09:
> 
>>>  Does somebody work on NanoBSD? It was not MFCed for long time on one
>>> hand, and on other hand, support of NANO_LABEL, added to CURRENT, is completely
>>> broken and almost useless.
>> I'm using the NANO_LABEL support, and I didn't have any problem.
>> What's your label problem with nanobsd precisely ?
>  (1) Copied out "upgrade" image has always ${NANO_LABEL}s1 label, and
> needs manual mdconfig+tunefs before dumping on second code partition
> 
>  (2) updatep2 script uses sed 's/${NANO_DRIVE}s1/${NANO_DRIVE}s2/'
> script, and if NANO_LABLE is in use (which sets NANO_DRIVE to
> "ufs/labels1") sed complains.

That hardly qualifies as completely broken.

Those are bugs, and I'll look at fixing them.

Warner

Warner Losh | 11 Apr 16:32 2011

Re: Does somebody work on NanoBSD?


On Apr 11, 2011, at 3:07 AM, Olivier Cochard-Labbé wrote:

> 2011/4/11 Lev Serebryakov <lev@...>:
>> Hello, Olivier.
>> You wrote 11 апреля 2011 г., 11:51:09:
> 
>>  (1) Copied out "upgrade" image has always ${NANO_LABEL}s1 label, and
>> needs manual mdconfig+tunefs before dumping on second code partition
>> 
>>  (2) updatep2 script uses sed 's/${NANO_DRIVE}s1/${NANO_DRIVE}s2/'
>> script, and if NANO_LABLE is in use (which sets NANO_DRIVE to
>> "ufs/labels1") sed complains.
>> 
> 
> OK, I didn't see this problem because I'm using my own upgrade script
> (I've merged update1 and update2 in one script):
> http://bsdrp.svn.sourceforge.net/viewvc/bsdrp/trunk/Files/usr/local/sbin/upgrade

I also think that FreeNAS has its own script, which I though had been merged to head.

Warner


Gmane