Re: Something rotten in ports (was Re: package building failure irritation)
On Sat, 13 Mar 2010 23:31, xorquewasp@ wrote: 'Lo, On 2010-03-13 20:40:32, jhell wrote: Not that this is a solution to your problem but it might be a possibility for you to consider, but a couple years back I dropped using make package(-recursive) and just scripted out making backup packages using something like the following. I particularly like this solution! I might just go ahead and implement this here, including the signing. Thanks. xw No Problem. Your welcome. -- jhell ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [patch] small fix to stop gcc warning for lib/libstand/assert.c
Garrett Cooper schrieb am 2010-03-14: > On Sat, Mar 13, 2010 at 9:24 PM, Doug Barton > wrote: > > On 03/13/10 05:52, Alexander Best wrote: > >> hello, > >> this patch fixes the following gcc warning: > > For all such issues, please file a PR first so it doesn't get lost. > > When > > you get the PR confirmation back, feel free to alert the list to > > its > > existence. >Yes, please submit a proper PR for this because it's a code bug; > FYI, your solution isn't complete though (it's close): ah ok. thanks for the hint. just wanted to spare linimon from dealing with such minor prs. ;) > ABORT(3) FreeBSD Library Functions Manual > ABORT(3) > NAME > abort -- cause abnormal program termination > LIBRARY > Standard C Library (libc, -lc) > SYNOPSIS > #include > void > abort(void); > Please be explicit and add stdlib.h. adding stdlib.h isn't going to work since stand.h is used to declare function prototypes which are also in stdlib.h. adding stdlib.h will cause gcc to complain about multiple definitions. stand.h e.g. has it's own printf and some other stuff. cheers. alex > Thanks, > -Garrett ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [patch] small fix to stop gcc warning for lib/libstand/assert.c
On Sun, Mar 14, 2010 at 4:12 AM, Alexander Best wrote: > Garrett Cooper schrieb am 2010-03-14: >> On Sat, Mar 13, 2010 at 9:24 PM, Doug Barton >> wrote: >> > On 03/13/10 05:52, Alexander Best wrote: >> >> hello, > >> >> this patch fixes the following gcc warning: > >> > For all such issues, please file a PR first so it doesn't get lost. >> > When >> > you get the PR confirmation back, feel free to alert the list to >> > its >> > existence. > >> Yes, please submit a proper PR for this because it's a code bug; >> FYI, your solution isn't complete though (it's close): > > ah ok. thanks for the hint. just wanted to spare linimon from dealing with > such minor prs. ;) > >> ABORT(3) FreeBSD Library Functions Manual >> ABORT(3) > >> NAME >> abort -- cause abnormal program termination > >> LIBRARY >> Standard C Library (libc, -lc) > >> SYNOPSIS >> #include > >> void >> abort(void); > >> Please be explicit and add stdlib.h. > > adding stdlib.h isn't going to work since stand.h is used to declare function > prototypes which are also in stdlib.h. adding stdlib.h will cause gcc to > complain about multiple definitions. stand.h e.g. has it's own printf and some > other stuff. Excellent point -- which means that any and all blanks in libstand could and should be filled in with equivalents in libc, i.e. you need to make sure that abort(3) has a proper function definition in libstand. Cheers, -Garrett ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: How to slow down SATA to 1.5 GBit/s ?
In article <106070878026...@192.168.2.69> you write: >Hi, Hi! > >Gary Jennejohn wrote: >> I'm using ahci with two ATA/IDE DVD drives and they work as long as I >> have "device ata" in my kernel config. That's all I need. > >So i will probably need that for the IDE DVD-ROM >drive that is built in too. > Yeah I think so (I don't have ide drives on this box anymore...) There is code in head now and (I think) stabe/8 to use cam for `regular' (i.e. non-ahci) ata devices too, but I haven't played with that yet as ahci(4) now works pretty well for me (this box is on stable/8.) > >Juergen Lock wrote: >> thanks for trying to help improving libburn! :) > >Well, i am its active developer since a while. >Any problems with it are probably my fault. > :) >Nevertheless, its FreeBSD SCSI transport is not >originally by me. So i lack specific knowledge. >(There are two alternative transport adapters: >sg-freebsd originally by Alexander Nedotsukov, >sg-libcdio for upcomming libcdio-0.83 .) > > >> http://www.freebsd.org/cgi/query-pr.cgi?pr=138789 > >I will test. >This was BD-R, not BD-RE, i assume ? > That 15GB disc was BD-RE actually. >A leadout track. Sounds very CD-ish. >With DVD and BD one should rather go for READ >DISC INFORMATION and READ TRACK INFORMATION. > Hmm you might want to followup on the PR with that hint... > >> Well if you didn't create a swap partition during install then you >> don't have one. :) > >Not to have one seems to be an advantage now. >I don't remember to have been asked. Well you'd have created it in the label editor, I don't think sysinstall specifically asks for it. > But with >4 GB of RAM i might simply have answered 'no'. > :) > >> the saved state of a panic'd kernel, > >I assume for reporting my kernel panics i have to >install a development kernel ? Actually I _think_ GENERIC gets built with debug info by default these days, look for /boot/kernel/*.symbols files to check. Of course it may still make sense to build a custom kernel with ddb enabled etc too, see: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html Here is a config you could use: snip include GENERIC ident MYKERNEL nooptions WITNESS #optionsWITNESS # # The INVARIANTS option is used in a number of source files to enable # extra sanity checking of internal structures. This support is not # enabled by default because of the extra time it would take to check # for these conditions, which can only occur as a result of # programming errors. # #optionsINVARIANTS # # The INVARIANT_SUPPORT option makes us compile in support for # verifying some of the internal structures. It is a prerequisite for # 'INVARIANTS', as enabling 'INVARIANTS' will make these functions be # called. The intent is that you can set 'INVARIANTS' for single # source files (by changing the source file or specifying it on the # command line) if you have 'INVARIANT_SUPPORT' enabled. Also, if you # wish to build a kernel module with 'INVARIANTS', then adding # 'INVARIANT_SUPPORT' to your kernel will provide all the necessary # infrastructure without the added overhead. # #optionsINVARIANT_SUPPORT # # # Compile with kernel debugger related code. # options KDB # # Print a stack trace of the current thread on the console for a panic. # options KDB_TRACE # Don't enter the debugger for a panic. Intended for unattended operation # where you may want to enter the debugger from the console, but still want # the machine to recover from a panic. # options KDB_UNATTENDED # # Enable the ddb debugger backend. # options DDB # # Enable the remote gdb debugger backend. # options GDB # Size of the kernel message buffer. Should be N * pagesize. options MSGBUF_SIZE=(40960*4) snip >(Switching off-and-on a stuck USB drive is > obviously not a healthy thing to do.) > Hehe. >Well, i plan to install another FreeBSD from >scratch to try reproducing drive concurrency >problems which i experienced first and which >vanished after installing the ports of xfburn >and xorriso. >First drives got stuck when disturbed while >burning CD. Now the offender gets blocked until >the vulnerable drive state ends. >Those ports triggered a cascade of other ports. >So i have no idea which one might have tweaked >the configuration (or whathever happened). > Hmm not sure what happened there... Oh I do remember one issue: Burning usually doesn't work when hald is running, I suspect burning tools would have to tell it to stop polling the drive at least while they are writing a disc... > >> Btw there also is siis(4) [...] for >> SiliconImage sata controllers. >> [...] sas controllers > >If somebody has such hardware then i would be >interested to hear whether it works with libburn. >Anybody is invited to ask for support. > Actually I do have siis(4) here too, will have to test that someday... > >Have a n
Re: How to slow down SATA to 1.5 GBit/s ?
Hi, > > A leadout track. Sounds very CD-ish. > > With DVD and BD one should rather go for READ > > DISC INFORMATION and READ TRACK INFORMATION. Juergen Lock wrote: > Hmm you might want to followup on the PR with that hint... First i should become a less clueless newbie and get all my own stuff sorted out. Then i will probably take over the plight of ports maintainership from J.R. Oldroyd. Then i might study the sources of FreeBSD to find out what can be improved about DVD or BD. Only then i plan to become perky and tell other people what they should do. :)) > > (Switching off-and-on a stuck USB drive is > > obviously not a healthy thing to do.) > Hehe. It would be quite annoying if the machine had any other job than serving as OS example. > > First drives got stuck when disturbed while > > burning CD. Now the offender gets blocked until > > the vulnerable drive state ends. > [...] > Oh I do remember one issue: Burning usually doesn't work when hald > is running, I am not aware to have noticed it on FreeBSD. # ps -ax | fgrep hald 974 1 R+ 0:00.00 fgrep hald The machine runs headless resp. in console mode. No X, no desktop. So probably no hald. The current behavior is quite like Alexander predicted it for FreeBSD back in 2006. It resembles the one of older SuSE Linuxes. The initial behavior, before i installed ports, was rather frightening. The drives got stuck when i accessed them while a CD was burned. I had to shutdown -p and re-power in order to revive the SATA burner. USB power cycling did not cause a panic but the drive did not show up as /dev/cd* any more. A warm reboot helped. So this is on my long todo list for inspection. > Actually I do have siis(4) here too, will have to test that someday... With xorriso you would get a nice backup program. :)) The port is a bit outdated. GNU xorriso-0.5.0 should compile on FreeBSD out of the box. It is a standalone package with minimal external dependencies. Well suited for a test. With a SATA drive at ata i need rw-permissions for these device files: acd, pass, cd, xpt. The port of xfburn generously (or daringly) writes into /etc/devfs.rules : # rules for grip and xfburn support add path 'acd*' mode 0666 add path 'cd*' mode 0666 add path 'pass*' mode 0666 add path 'xpt*' mode 0666 Have a nice day :) Thomas ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [patch] small fix to stop gcc warning for lib/libstand/assert.c
On Sun, Mar 14, 2010 at 01:12:14PM +0100, Alexander Best wrote: > ah ok. thanks for the hint. just wanted to spare linimon from dealing with > such minor prs. ;) It's much more efficient for the project to have them in GNATS. I tend to triage PRs with the TV on, so it's not like the trivial ones are a great burden. mcl ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [patch] small fix to stop gcc warning for lib/libstand/assert.c
Mark Linimon schrieb am 2010-03-14: > On Sun, Mar 14, 2010 at 01:12:14PM +0100, Alexander Best wrote: > > ah ok. thanks for the hint. just wanted to spare linimon from > > dealing with > > such minor prs. ;) > It's much more efficient for the project to have them in GNATS. > I tend to triage PRs with the TV on, so it's not like the trivial > ones > are a great burden. haha...ok. multitasking at its best. ;) > mcl ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Something rotten in ports (was Re: package building failure irritation)
On Sat, Mar 13, 2010 at 08:40:32PM -0500, jhell wrote: > Rather simple way to go about creating final packages and from some > earlier emails to the list there was word of some directories not being > included in final built packages due to empty directories or something > like that so be careful when/if considering something like this. I believe you are talking about ports/144164 which was about RC scripts not being included in a package when using package-noinstall. This is currently in the hands of portmgr. It will have to wait until 7.3 is out, at the earliest. -- WXS ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Drop cache
How I can drop cache memory of my FreeBSD ? I search a lot about this and don't find anything. In Linux i usualy use this command: sync; echo 3 > /proc/sys/vm/drop_caches I need it for experiments. Thanks. Thadeu Knychala Tucci ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
