headers
Rene Schickbauer | 1 May 2008 01:31
Favicon

Re: introduction

Hi, James!

> I'm working on the embedded FreeBSD project; I find embedded development to
> be difficult and extremely enjoyable. It covers a lot of bases, while also
> hearkening back to days when there were fewer resources available on any
> system, so that I feel like I'm working in an environment from the late
> seventies or early eighties. Which means I feel retro cool without actually
> being limited in resources in the real world.

Welcome! Just the project i need (having multiple Soekris-Boxes myself ;-)

I'm currently hacking around on my Soekris-Box to use the Error-Led for
displaying fault conditions (which is much more usefull than using it to
send more code). It's currently only a proof-of-concept at the moment, but
if it can aid your project, send me an email :-)

LLAP & LG
Rene

--

-- 
---------------------- OmniCode 0.1.6 -----------------------
sxy cm169 esO sp= Ag1976 anE hda ZoS Rl! Kd! MBINTJ UFGreg&Sid IN10 AdC&N
PrPerl(8)&C(7)&C++(7)&LUA(8)&PHP(8)&C#(4)&SQL(8)&BSLUA(9)
----------- Omnicode http://www.gadgeteer.net/omnicode/ -----------
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1  Visit <http://www.ebb.org/ungeek/> to decode
GCS/CM d--(-) s:- a C++(+++)$>++++ UBLAHC*+++(++++)$>++++
P+++(++++)$>+++++ L+(++)>$ !E---(-) W+++$ N+(++) <at>  o+(++) <at> 
K? w+++(++)$>--- !O- M++>$ V-(--) PS+ PE Y+ PGP+ t+ 5 X-
R- tv-- b++(+++) DI-- D+ G++ e- h r? y+
(Continue reading)

Permalink | Reply | 0 comments |
headers
Murty, Ravi | 1 May 2008 01:49
Picon
Favicon

RE: maybe_preempt_in_ksegrp

Sorry I wish I was part of the development effort. I am just coming on
board with FreeBSD work.

I guess ksegrps were implemented for the purpose of PROCESS_SCOPE
threads and like you said avoiding a process from hogging the CPU.

If every thread in the system has it's own ksegrp (SYSTEM_SCOPE) I don't
see this call (maybe_preempt_in_ksegrp) ever getting called :).

Thanks
ravi

-----Original Message-----
From: Julian Elischer [mailto:julian <at> elischer.org] 
Sent: Wednesday, April 30, 2008 3:52 PM
To: Murty, Ravi
Cc: freebsd-hackers <at> freebsd.org
Subject: Re: maybe_preempt_in_ksegrp

Murty, Ravi wrote:
> Julian,
> 
> Apologies for sticking to 6.x, I checked and looks like this function
> and several others are out in 7.x. It's just that we've been using 6.x
> for a while and continue to look at it. :)
> 
> 
> Coming back, I was thinking of the problem the other way around. The
> thread gets put on the ksegrp runq, but we don't know if it gets put
at
(Continue reading)

Permalink | Reply | 1 comment |
headers
Julian Elischer | 1 May 2008 02:11

Re: maybe_preempt_in_ksegrp

Murty, Ravi wrote:
> Sorry I wish I was part of the development effort. I am just coming on
> board with FreeBSD work.
> 
> I guess ksegrps were implemented for the purpose of PROCESS_SCOPE
> threads and like you said avoiding a process from hogging the CPU.
> 
> If every thread in the system has it's own ksegrp (SYSTEM_SCOPE) I don't
> see this call (maybe_preempt_in_ksegrp) ever getting called :).

which is why the default was process scope.

> 
> Thanks
> ravi
> 
> 
> -----Original Message-----
> From: Julian Elischer [mailto:julian <at> elischer.org] 
> Sent: Wednesday, April 30, 2008 3:52 PM
> To: Murty, Ravi
> Cc: freebsd-hackers <at> freebsd.org
> Subject: Re: maybe_preempt_in_ksegrp
> 
> Murty, Ravi wrote:
>> Julian,
>>
>> Apologies for sticking to 6.x, I checked and looks like this function
>> and several others are out in 7.x. It's just that we've been using 6.x
>> for a while and continue to look at it. :)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Giorgos Keramidas | 2 May 2008 04:11
Picon
Favicon
Gravatar

Re: indent(1) support for gcc(1) 0b prefix

On Sun, 27 Apr 2008 02:01:53 +0200, Max Laier <max <at> love2party.net> wrote:
> On Saturday 26 April 2008 23:35:57 Romain Tartière wrote:
>> Hello FreeBSD hackers!
>>
>> I'm using avr-gcc from the ports and relying on the 0b prefix notation
>> for binary constants, that is:
>>
>> 	foo = 0b00101010;
>>
>> Thanks to /usr/ports/devel/avr-gcc/files/patch-0b-constants this is
>> possible :-)
>>
>> But I would like to use indent(1) to reformat contributed code
>> automatically. Unfortunately, the 0b notation is not supported by that
>> program, and the resulting code looks like this:
>>
>> 	foo = 0 b00101010;
>>
>> ... then compilation fails, bla bla bla...
>
> I can't think of a case (outside of "0x...." context) where "...0b..."
> would be valid C code, let alone better formated as "...0 b...".
> Hence I see no harm in adding your patch to the base indent(1).
>
> Does anyone have an example where "...0 b..." is valid C code?

The only case I can think of is when the "b..." is an existing macro,
i.e. something like:

     1  #include <stdio.h>
(Continue reading)

Permalink | Reply | 2 comments |
headers
Tim Kientzle | 2 May 2008 06:16
Picon
Favicon

Re: indent(1) support for gcc(1) 0b prefix

>>>But I would like to use indent(1) to reformat contributed code
>>>automatically. Unfortunately, the 0b notation is not supported by that
>>>program, and the resulting code looks like this:
>>>
>>>	foo = 0 b00101010;
>>>
>>>... then compilation fails, bla bla bla...
>>
>>I can't think of a case (outside of "0x...." context) where "...0b..."
>>would be valid C code, let alone better formated as "...0 b...".
>>Hence I see no harm in adding your patch to the base indent(1).
>>
>>Does anyone have an example where "...0 b..." is valid C code?
> 
> The only case I can think of is when the "b..." is an existing macro,
> i.e. something like:
> 
>      1  #include <stdio.h>
>      2
>      3  #define b0101   + 3

In all of these cases, though, adding a space between the '0' and
the 'b' changes the meaning, so is wrong.  Indent can
change/insert whitespace, but should never do so in a way that
changes the meaning of the program.  In all of these cases,
having indent recognize "0b..." as a single token is the
correct behavior.

So I don't see any point in having this recognition be
tunable.  indent already has too many switches.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Martin Schütte | 2 May 2008 22:51
Favicon

Improving Syslog

Hello,
I am taking part in this year's Google Summer of Code for NetBSD and 
want to implement the upcoming IETF Syslog standards for BSD's 
syslogd(8). The most important improvements will be an extended message 
format, TLS network transport, and digital signatures.

I hope these new functions will later be ported to benefit all BSD 
variants (as their syslogds are similar).
So everyone interested is invited to take a look at the project pages 
now and then. Naturally any feedback is welcome.

The official project's homepage is at 
http://netbsd-soc.sourceforge.net/projects/syslogd/
and for developing I maintain a Trac at 
http://barney.cs.uni-potsdam.de/trac/syslogd/

--

-- 
Martin
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
Permalink | Reply | 11 comments |
headers
Xin LI | 2 May 2008 23:26

Re: Improving Syslog


Martin Schütte wrote:
| Hello,
| I am taking part in this year's Google Summer of Code for NetBSD and
| want to implement the upcoming IETF Syslog standards for BSD's
| syslogd(8). The most important improvements will be an extended message
| format, TLS network transport, and digital signatures.
|
| I hope these new functions will later be ported to benefit all BSD
| variants (as their syslogds are similar).
| So everyone interested is invited to take a look at the project pages
| now and then. Naturally any feedback is welcome.
|
| The official project's homepage is at
| http://netbsd-soc.sourceforge.net/projects/syslogd/
| and for developing I maintain a Trac at
| http://barney.cs.uni-potsdam.de/trac/syslogd/

That's cool.  Is there any commit-mail style stuff that we can subscribe
so we can gradually incorporate your work into FreeBSD?

Cheers,
--
Xin LI <delphij <at> delphij.net>	http://www.delphij.net/
FreeBSD - The Power to Serve!
Permalink | Reply | 1 comment |
headers
Sanjeev Kumar.S | 3 May 2008 10:41
Picon
Favicon

Re: Saving entire console sessions

Thank you this serves my purpose very well.

Pranav Peshwe <pranavpeshwe <at> gmail.com> wrote: On Thu, Apr 24, 2008 at 5:57 PM, Sanjeev Kumar.S 
wrote:

> Hi,
>    Is there any way to save entire console
>    sessions ?
>    Screen asks me to copy and paste what
>    I want. I don't want to do that I need to save
>     entire sessions. like a start till I do a exit or
>      quit the application. Is there a utility like
>    that ?
>

Did you try enabling logging for a screen window ? `screen -L` may be of
help.

Best regards,
Pranav

--------------------------------------------------------------------------
Blessed are the pessimists, for they take backups!!
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

       
---------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sanjeev Kumar.S | 3 May 2008 10:42
Picon
Favicon

Re: Saving entire console sessions

Sorry, did not mean to. Thank you very much for the suggestion.
Suits my requirement very well.

Regards,
Sanjeev.

Rink Springer <rink <at> FreeBSD.org> wrote: Hi,

On Thu, Apr 24, 2008 at 05:27:36AM -0700, Sanjeev Kumar.S wrote:
>     Is there any way to save entire console 
>     sessions ?
>     Screen asks me to copy and paste what 
>     I want. I don't want to do that I need to save 
>      entire sessions. like a start till I do a exit or
>       quit the application. Is there a utility like 
>     that ?

Please, don't hijack the thread next time :-) Either way, have a look at
script(1) - I think that is what you are looking for.

Regards,

--

-- 
Rink P.W. Springer                                - http://rink.nu
"Anyway boys, this is America. Just because you get more votes doesn't
 mean you win." - Fox Mulder
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Anthony Pankov | 3 May 2008 10:30
Picon

Re: Improving Syslog

Hello Martin,

It is not pleasant to me that most comprehensible unix subsystem -
syslog - will grow to multipurpose monster.

More pleasant to here about careful redesign of syslogd that make
available various plugins|additional daemons each of which adds
well-defined functionality.

I dislike many features living in one binary file. Especially when
this binary will do one thing for me - write messages to file.

Sorry, but when i imagine one more software to scrub from cool
features i become more sad.

Saturday, May 03, 2008, 12:51:32 AM, you wrote:

MS> Hello,
MS> I am taking part in this year's Google Summer of Code for NetBSD and 
MS> want to implement the upcoming IETF Syslog standards for BSD's 
MS> syslogd(8). The most important improvements will be an extended message 
MS> format, TLS network transport, and digital signatures.

MS> I hope these new functions will later be ported to benefit all BSD 
MS> variants (as their syslogds are similar).
MS> So everyone interested is invited to take a look at the project pages 
MS> now and then. Naturally any feedback is welcome.

MS> The official project's homepage is at 
MS> http://netbsd-soc.sourceforge.net/projects/syslogd/
(Continue reading)

Permalink | Reply | 4 comments |

Gmane