Re: shells/bash port, add a knob which symlinks to /bin/bash ?
On 9/13/14, 11:39 AM, Nathan Whitehorn wrote: On 09/13/14 11:32, Craig Rodrigues wrote: If adding an optional knob to the bash port which is OFF by default to do this is a no-go, would having an optional port like what Brooks Davis mentioned be allowed which creates the symlink and updates /etc/shells? -- I'd point out that the perl ports have exactly such an option already (putting links in /usr/bin, in this case). The CUPS port does too. -Nathan Should really be a standalone package. -Alfred ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: shells/bash port, add a knob which symlinks to /bin/bash ?
On Sun, Sep 14, 2014 at 10:44 AM, Alfred Perlstein bri...@mu.org wrote: On 9/13/14, 11:39 AM, Nathan Whitehorn wrote: Should really be a standalone package. It's not exactly the same, but the lang/python2 port for example is a meta-port which creates symlinks such as /usr/local/bin/python2 - python2.7. So the precedent of having a metaport which creates symlinks is there. What folks have been complaining about in this thread is having symlinks in the base system directories such as /bin. My personal feeling is that we should look at this on a case-by-case basis and allow these types of ports, such as for /bin/bash but I'm sure others will disagree. -- Craig ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: shells/bash port, add a knob which symlinks to /bin/bash ?
On 9/14/14, 3:22 PM, Craig Rodrigues wrote: On Sun, Sep 14, 2014 at 10:44 AM, Alfred Perlstein bri...@mu.org mailto:bri...@mu.org wrote: On 9/13/14, 11:39 AM, Nathan Whitehorn wrote: Should really be a standalone package. It's not exactly the same, but the lang/python2 port for example is a meta-port which creates symlinks such as /usr/local/bin/python2 - python2.7. So the precedent of having a metaport which creates symlinks is there. What folks have been complaining about in this thread is having symlinks in the base system directories such as /bin. Why do you care what people are complaining about? Just make the port. :) My personal feeling is that we should look at this on a case-by-case basis and allow these types of ports, such as for /bin/bash but I'm sure others will disagree. We already allow such ports, for example a bunch of kmods install into /boot/kernel or /boot/modules. There are always exceptions to rules and for good reasons! find . -name pkg-plist | xargs grep -A 3 '^@cwd /$' -- Craig ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: shells/bash port, add a knob which symlinks to /bin/bash ?
On Sep 12, 2014, at 14:38, Bryan Drewery bdrew...@freebsd.org wrote: No (as portmgr). Ports should not be touching the base system like this. Let's NOT go backwards and add a /bin/bash. In fact the /usr/bin/perl one will be removed soon as well. If we can actually eliminate ports touching /usr and / (not including /usr/local and /var) then we gain a very large memory optimization for package building by being able to ro null-mount these to the build jails. There's no reason for bash (and perl) to be exceptions to the 24000 other ports that install to /usr/local/bin. I can think of dozens of other ports that will fall into the same arguments being made here, but it does not mean it is the right thing for FreeBSD. If you want to install the symlink on your system feel free to do it. I install a static bash to /bin/bash on mine and only because I prefer bash shell and want it in / for single-user mode. That's my personal choice though. The proper fix is to fix scripts to be portable and use #! /usr/bin/env bash rather than /bin/bash. We install all packages to PREFIX=/usr/local by default. Why should a bin symlink be an exception? There's no suggestion for symlinking includes or libraries which also hit users often. Hi Bryan, I understand portmgr’s reasoning for removing these knobs as it improves “portability” (builds and runtime won’t depend on broken code), but I see the merits of making a separate package for Linux “compatibility” for the various items that people have brought up (mostly the LDAP issue and the vendor/legacy script portability issue). Plus it makes the barrier for entry lower, and less of a reason for Linux users to complain about how FreeBSD is different from Linux. Adding these as options to the port(s) won’t work for various reasons, two of which came to mind are: 1. People should be able to install packages from FreeBSD.org instead of having to roll their own ports with custom options. 2. It’s best not to build other packages on unportable (/bin/bash) behavior. Thanks! -Garrett PS I don’t agree with Fedora/FreeDesktop’s push to move everything to /usr (I think it’s a wee bit radical, to say the least, and seems like it’s optimizing the wrong thing), but it’s something to keep in mind as this non-portable decision may start working its way into upstream ports: https://fedoraproject.org/wiki/Features/UsrMove . signature.asc Description: Message signed with OpenPGP using GPGMail
Re: shells/bash port, add a knob which symlinks to /bin/bash ?
On Sat, Sep 13, 2014 at 08:39:17PM +0100, Dreamcat4 wrote:
Right, well here is another one:
The missing symlink for /etc/ssl/cert.pem
There is no reason it should not be in
${prefix}/etc/ssl/cert.pem
Except that the folder etc/ssl/ only exists in base.
Without this symlink, then SSL certs aren't found by the 'fetch'
command and many significant websites these days can't work without
SSL. For example github.com (there are others).
fetch has been fixed to read the one from localbase first.
regards,
bapt
pgpbciUiZWTKp.pgp
Description: PGP signature
SOEKRIS kernel crash
I've compiled a SOEKRIS kernel which I'm booting with Crochet-BSD. It's reliably crashing on boot, with the below message. The kernel revision is 271600, and the kernel config is here: https://github.com/kientzle/crochet-freebsd/blob/master/board/Soekris/conf/SOEKRIS11 Event timer RTC frequency 32768 Hz quality 0 attimer0: AT timer at port 0x40 on isa0 Timecounter i8254 frequency 1189161 Hz quality 0 Event timer i8254 frequency 1189161 Hz quality 100 uart0: 16550 or compatible at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 uart0: console (9600,n,8,1) uart1: 16550 or compatible at port 0x2f8-0x2ff irq 3 on isa0 Timecounters tick every 1.000 msec interrupt storm detected on irq5:; throttling interrupt source Elan-mmcr driver: MMCR at 0xc37ff000. Elan-mmcr Soekris net45xx comBIOS ver. 1.33 20080103 Copyright (C) 2000-2007 random: unblocking device. ada0 at ata0 bus 0 scbus0 target 0 lun 0 ada0: SanDisk SDCFX-016G HDX 7.03 CFA-0 device ada0: Serial Number AJZ061813191928 ada0: 16.700MB/s transfers (PIO4, PIO 512bytes) ada0: 15259MB (31250432 512 byte sectors: 16H 63S/T 31002C) ada0: Previously was known as ad0 panic: Bio not on queue bp=0xc2ab74c0 target 0xc0c0f43c KDB: stack backtrace: db_trace_self_wrapper(c0b3e6fa,c2a01800,c2689be4,c061fdf1,c2a01830,...) at db_trace_self_wrapper+0x2d/frame 0xc2689bb8 kdb_backtrace(c0b39cc6,c0c11408,c0b26e7a,c2689c70,c0b26e7a,...) at kdb_backtrace+0x30/frame 0xc2689c1c vpanic(c0c112a8,100,c0b26e7a,c2689c70,c2689c70,...) at vpanic+0x80/frame 0xc2689c40 kassert_panic(c0b26e7a,c2ab74c0,c0c0f43c,0,c28d9c40,...) at kassert_panic+0xe9/frame 0xc2689c64 g_bioq_first(c0c0f454,0,c0b26c3c,5c,0,...) at g_bioq_first+0x63/frame 0xc2689c80 g_io_schedule_up(c28d9c40,0,c0b27089,60,c2689cf4,...) at g_io_schedule_up+0x94/frame 0xc2689cb4 g_up_procbody(0,c2689d08,c0b3335e,3c9,0,...) at g_up_procbody+0x9d/frame 0xc2689ccc fork_exit(c0703210,0,c2689d08) at fork_exit+0x7f/frame 0xc2689cf4 fork_trampoline() at fork_trampoline+0x8/frame 0xc2689cf4 --- trap 0, eip = 0, esp = 0xc2689d40, ebp = 0 --- KDB: enter: panic [ thread pid 13 tid 19 ] Stopped at kdb_enter+0x3d: movl$0,kdb_why db bt Tracing pid 13 tid 19 td 0xc28d9c40 kdb_enter(c0b39f64,c0b39f64,c0b26e7a,c2689c70,c0b26e7a,...) at kdb_enter+0x3d/frame 0xc2689c1c vpanic(c0c112a8,100,c0b26e7a,c2689c70,c2689c70,...) at vpanic+0xcb/frame 0xc2689c40 kassert_panic(c0b26e7a,c2ab74c0,c0c0f43c,0,c28d9c40,...) at kassert_panic+0xe9/frame 0xc2689c64 g_bioq_first(c0c0f454,0,c0b26c3c,5c,0,...) at g_bioq_first+0x63/frame 0xc2689c80 g_io_schedule_up(c28d9c40,0,c0b27089,60,c2689cf4,...) at g_io_schedule_up+0x94/frame 0xc2689cb4 g_up_procbody(0,c2689d08,c0b3335e,3c9,0,...) at g_up_procbody+0x9d/frame 0xc2689ccc fork_exit(c0703210,0,c2689d08) at fork_exit+0x7f/frame 0xc2689cf4 fork_trampoline() at fork_trampoline+0x8/frame 0xc2689cf4 --- trap 0, eip = 0, esp = 0xc2689d40, ebp = 0 --- db -- A better world shall emerge based on faith and understanding - Douglas MacArthur ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Driver-specific debugging in buildkernel?
I want to build a kernel with debugging for a specific device, rather than for everything. Device of interest is re (Ethernet driver), also rsu (USB wlan adapter). I looked in Makefiles, also NOTES files, found some DEBUG options but nothing really general that could be applied to any desired device in kernel or module. Then I would need to know how to find this debugging information. Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
