p5-XML-SAX and portupgrade
There is an update of p5-XML-SAX in the ports, /usr/ports/UPDATING says: 20120512: AFFECTS: users of textproc/p5-XML-SAX AUTHOR: cr...@freebsd.org p5-XML-SAX (X-S) was split into p5-XML-SAX-Base (X-S-B) and p5-XML-SAX for version 0.99. Since X-S-B now installs some files formerly installed by X-S the package for X-S must be deinstalled before updating X-S. # pkg_delete -fx p5-XML-SAX # portmaster textproc/p5-XML-SAX (users of pkgng can substitute pkg_delete with pkg delete) But what is the instruction for users of portupgrade ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: CSH prompt
On Sun, 13 May 2012 08:16:51 -0600, Reed Loefgren wrote:
> On 05/13/12 07:25, Polytropon wrote:
> > On Sun, 13 May 2012 14:56:31 +0200, Jos Chrispijn wrote:
> >> In cshell I use this prompt: set prompt = "%B[%@]%b %m[%/]> "
> >> The problem I face now is that if I use this prompt with symbolic links,
> >> the presented location is displaying the symbolic link rather than the
> >> real directory name.
> >> Is there a way of preventin this?
> > Yes, a very ugly way which I just found out:
> >
> > alias precmd 'set WD=`pwd`; set prompt = "%B[%@]%b %m[$WD]> "'
> >
> > Example:
> >
> > [3:21pm] r56[/]> cd /sys
> > [3:21pm] r56[/usr/src/sys]> _
> >
> > It redefines the whole prompt at any command that could
> > affect the current working directory (not only "cd" can
> > do that). This is needed as any call to `pwd` stored into
> > a variable will only affect $prompt once - this is when
> > it's set, only at this time $WD would be evaluated. So
> > that's why this strange command. :-)
> >
> > Oh, and I just improved it. How about this?
> >
> > alias precmd 'set prompt = "%B[%@]%b %m[`pwd`]> "'
> >
> > Much better. :-)
>
> I've butchered it further, but thanks for doing the *real* work:
>
> user:
> alias precmd 'set prompt = "\n%{\033[32m%}%m [%h] [%@]%b%{\033[0m%}
> [`pwd`]$ "'
>
> root:
> alias precmd 'set prompt = "\n%{\033[31m%}%m [%h] [%@]%b%{\033[0m%}
> [`pwd`]$ "'
Allow me a final note:
It's "normal" to denote non-root access with % (for csh) or $ (for
sh, bash and many others), and root access with #. You can easily
configure that to be automatically instead of $ if you like.
Example:
set promptchars = "%#"
set prompt = "%n@%m:%~%# "
For root, # will appear at the end, and % for non-root. Of course,
you can easily apply this to your setting if you like, and you can
define other characters if needed (e. g. "$#" or ">#").
Even though in your prompt shown above, root is shown by red color,
that important attribute _might_ be missing when using a non-color
terminal or a misconfigured emulator, so the user might not be
aware of the immense power currently active (as no user name is
shown in the prompt). Maybe this inspiration is useful to you.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: p5-XML-SAX and portupgrade
On 2012-05-14 10:16, n dhert wrote: There is an update of p5-XML-SAX in the ports, /usr/ports/UPDATING says: 20120512: AFFECTS: users of textproc/p5-XML-SAX AUTHOR: cr...@freebsd.org p5-XML-SAX (X-S) was split into p5-XML-SAX-Base (X-S-B) and p5-XML-SAX for version 0.99. Since X-S-B now installs some files formerly installed by X-S the package for X-S must be deinstalled before updating X-S. # pkg_delete -fx p5-XML-SAX # portmaster textproc/p5-XML-SAX (users of pkgng can substitute pkg_delete with pkg delete) But what is the instruction for users of portupgrade ? Susbstitude "portmaster" with "portupgrade" is my guess. Armin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
what software can support that UPS ?
seems like it is very badly made USB interface, all class data is empty, ugen1.3: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0101 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0008 idVendor = 0x0403 idProduct = 0xe520 bcdDevice = 0x0400 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 FreeBSD gives only ugen interface. what (if any) software support that? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: what software can support that UPS ?
/usr/ports/sysutils/apcupsd ? On 05/14/2012 14:06, Wojciech Puchar wrote: seems like it is very badly made USB interface, all class data is empty, ugen1.3: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0101 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0008 idVendor = 0x0403 idProduct = 0xe520 bcdDevice = 0x0400 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 FreeBSD gives only ugen interface. what (if any) software support that? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" -- No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: what software can support that UPS ?
/usr/ports/sysutils/apcupsd ? ? - so what to give as device? /dev/ugen1.3? set UPSCABLE usb UPSTYPE usb not set DEVICE as specified in comments for USB devices. can't find UPS. tried setting DEVICE to /dev/ugen1.3 - no avail. tried /usr/ports/sysutils/nut selected "EVER" driver, and set up /dev/ugen1.3 as port - driver fails. from what i found in linux groups it should work as USB HID device. but uhid doesn't attach. On 05/14/2012 14:06, Wojciech Puchar wrote: seems like it is very badly made USB interface, all class data is empty, ugen1.3: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0101 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0008 idVendor = 0x0403 idProduct = 0xe520 bcdDevice = 0x0400 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 FreeBSD gives only ugen interface. what (if any) software support that? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" -- No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Building FreeBSD to install or update in two DESTDIRs
I would like to build FreeBSD to install in two places: regular hard drive and also on a USB stick, probably 8 GB. USB stick install would be for backup, in case something goes awry with a later update, then I have something to fall back on; could also install tools such as gdisk to use on hard drive. I tried make installkernel and make installworld, but those didn't fully work right the second time, with DESTDIR=/mnt (USB stick main partition). REALLY can't help you without any info attached. As from your description it just have to work and you did all fine. anyway i usually just do installs to DESTDIR=/something, then tar.gz it up, and untar whenever i need (but separately tar.gz for /boot/kernel subdir) use --unlink option when untarring on live system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: avrdude and arduino
This is the command I'm using: %sudo avrdude -F -v -v -v -v -c arduino -p ATMEGA328P -P /dev/cuaU0 -U flash:w:flash.hex This is what I use for Duemilanove sudo avrdude -V -F -c stk500v1 -p m168 -b 19200 -P /dev/cuaU0 -U flash:w:flash.hex (Arduino) maybe stupid question but why do you use sudo for it? can't you just set up devd.conf to set right owner to /dev/cuaU0, or even better make link like /dev/atmel -> /dev/yourdevice - so no matter how many usb serial devices you connect it will always have same name? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: what software can support that UPS ?
Wojciech Puchar writes: > > /usr/ports/sysutils/apcupsd ? > > ? - so what to give as device? /dev/ugen1.3? > set > > UPSCABLE usb > UPSTYPE usb My BackUPS RS 500 works fine using those and a empty "DEVICE" field. It is possible this is a new/redesigned model that Apcupsd does not handle correctly. (APC is famous for not having a consistant interface, even model lines.) If so, you should post to the apcupsd mailing list where these kind of things get prompt attention. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: avrdude and arduino
On Mon, May 14, 2012 at 3:25 PM, Wojciech Puchar wrote: >>> This is the command I'm using: >>> >>> %sudo avrdude -F -v -v -v -v -c arduino -p ATMEGA328P -P /dev/cuaU0 -U >>> flash:w:flash.hex >> >> >> This is what I use for Duemilanove >> sudo avrdude -V -F -c stk500v1 -p m168 -b 19200 -P /dev/cuaU0 -U >> flash:w:flash.hex (Arduino) > > > maybe stupid question but why do you use sudo for it? can't you just set up > devd.conf to set right owner to /dev/cuaU0, or even better make link like > /dev/atmel -> /dev/yourdevice - so no matter how many usb serial devices you > connect it will always have same name? Yes, I'll do it when I use the Arduino the next time (it's been a while since the last time). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: dlink dwl-122g e1 on 9-stable, working only partially? (or not at all?)
On Sun, 13 May 2012 23:09:34 -0600 PseudoCylon wrote: > > -- > > > > Message: 11 > > Date: Sun, 13 May 2012 01:21:30 +0200 > > From: "Christopher J. Ruwe" > > Subject: Re: dlink dwl-122g e1 on 9-stable, working only partially? > > (or not at all?) > > To: freebsd-questions@freebsd.org > > Message-ID: <20120513012130.64d78...@dijkstra.cruwe.de> > > Content-Type: text/plain; charset=US-ASCII > > > > On Sat, 12 May 2012 14:49:18 +0200 > > "Christopher J. Ruwe" wrote: > > > >> Currently I am fighting with (against?) a dlink dwl-g122 usb wlan > >> dongle. The casing is claiming the thing to be of H/W-version E1, > >> F/W-version 5.00, which I interpret as hardware and firmware. > >> > >> I am running 9-stable (FreeBSD ritchie.cruwe.de 9.0-STABLE FreeBSD > >> 9.0-STABLE #8 r235064: Fri May 11 21:32:52 CEST 2012 > >> c...@ritchie.cruwe.de:/usr/obj/usr/src/sys/RITCHIE amd64) and > >> admittedly, dwl-g122 is not included in the hw-compatibility list > >> for 9.0. > >> > >> I am also aware that others have been unsuccessful, though some > >> time back, to get dlw-g122 e running > >> (http://forums.freebsd.org/showthread.php?t=27123). > >> > >> However, I am somewhat successful in getting the dongle recognized > >> by if_run.ko, though not to work as I would like to: > >> > >> dmesg gives then > >> > >> [...] > >> ugen0.3: at usbus0 > >> run0: on > >> usbus0 run0: MAC/BBP RT3070 (rev 0x0201), RF RT2020 (MIMO 1T1R), > >> address b8:a3:86:97:c1:ec ieee80211_load_module: load the > >> wlan_amrr module by hand for now. wlan0: Ethernet address: > >> b8:a3:86:97:c1:ec run0: firmware RT2870 ver. 0.236 loaded > >> ieee80211_load_module: load the wlan_amrr module by hand for now. > >> wlan0: Ethernet address: b8:a3:86:97:c1:ec > >> I have no explanation for the multiple occurrences, I have been > >> trying for some time now, though. > >> > > Was wlan_amrr compiled into kernel? Nope, using the module. BTW, loading the if_run module gives ieee80211_load_module: load the wlan_amrr module by hand for now. Did exactly that, i.e., loaded the wlam_amrr by hand. Do you think I might fare better by using in-kernel drivers instead of modules? > >> > >> sudo ifconfig wlan0 create wlandev run0 wlanmode hostap > >> sudo ifconfig wlan0 inet 192.168.3.1 netmask 255.255.255.0 ssid > >> bsdap channel - > >> > > If you want to use WPA, you need to run > # /etc/rc.d/hostapd onestart Amongst other things, I also did that. > > > OK, update on the situation: I can get wlan to work in AP-mode, I > > must not enable WPA, though. Having enabled hostapd for one time > > kills my wlan and requires a complete reboot. > > > > Did it panic? Can you post back trace? No, it did not panic. After trying to enable wpa, the systems becomes very sluggish on the network side and recovers upon pulling the dongle. I interpret that as some kind of crashing the driver. I would be happy to provide a back trace, I do not know how, though. Where do I need to look to learn that? Thanks and cheers, Christopher ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: what software can support that UPS ?
UPSCABLE usb UPSTYPE usb My BackUPS RS 500 works fine using those and a empty "DEVICE" field. how your UPS shows in dmesg? It is possible this is a new/redesigned model that Apcupsd does not handle correctly. (APC is famous for not having a consistant interface, even model lines.) If so, you should post to the apcupsd mailing list where these kind of things get prompt attention. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Problem with newvers.sh in FreeBSD 8.3-RELEASE (amd64)
Hi, I have used FreeBSD since 2002, first on i386-arch-machines and from October 2010 on an (Intel i5 750) amd64-arch-machine. On this new computer, a Dell Precision T1500, I now have three operating systems on /dev/ada1s1-3: FreeBSD 8.1-RELEASE, FreeBSD 8.2-RELEASE and FreeBSD 8.3-RELEASE. Only the last release have the problem described in the following text. For the first time I got a problem after a kernel is recompiled. Below one can see that what now, after a recompilation should be FreeBSD 8.3-RELEASE #1 still is #0, and with a faulty date/time stamp. The number after the hash mark is not updated, neither is the date/time in these kernel messages. What is wrong? newvers.sh? = Misc info msgs about this problem === # $FreeBSD: src/sys/conf/newvers.sh,v 1.83.2.15.2.4 2012/04/08 05:09:40 kensmith Exp $ % ll /boot | grep kernel drwxr-xr-x 2 root wheel 31232 10 Maj 17:22 kernel drwxr-xr-x 2 root wheel 31232 9 Maj 14:49 kernel.old (I am a Swedish FreeBSD user, hence 'Maj' instead of May) % sysctl -a | grep kern.version kern.version: FreeBSD 8.3-RELEASE #0: Mon May 7 20:00:37 CEST 2012 % uname -a FreeBSD alice.nodomain.nowhere 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Mon May 7 20:00:37 CEST 2012 root@alice.nodomain.nowhere:/usr/src/sys/amd64/compile/ALICE amd64 == I compared by diff /usr/src/sys/conf/newvers.sh with the same file in FreeBSD 8.2 and found some differences. I saved newvers.sh in FreeBSD as ORIG_newvers.sh and copied the newvers.sh from FreeBSD 8.2 to FreeBSD 8.3. Edited the two lines REVISION="8.3", "RELEASE=8.3-RELEASE" and recompiled. It worked, so now I get the correct answers: % sysctl -a | grep kern.version kern.version: FreeBSD 8.3-RELEASE #2: Sun May 13 21:16:37 CEST 2012 % uname -a FreeBSD alice.nodomain.nowhere 8.3-RELEASE FreeBSD 8.3-RELEASE #2: Sun May 13 21:16:37 CEST 2012 root@alice.nodomain.nowhere:/usr/src/sys/amd64/compile/ALICE amd64 Best Regards, Conny Andersson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
freebsd.asia
Hello, I want to make a gift to the FreeBSD project and give your domain freebsd.asia. Who should I contact? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
AFS install
Hi, I installed AMD64 FreeBSD 8.3 on a new machine a couple of days ago. It seems fine so far. This afternoon I tried to install OpenAFS 1.6.0 on it from /usr/ports/net/openafs The configure ran happily and I didn't notice any errors. But, the make died soon after starting with the following complaints. make: don't know how to make ./param.amd64_fbsd_83.h. stop *** Error code 2 Stop in /usr/ports/net/openafs/work/openafs-1.6.0. ** Error code 1 I presume that means that it does not know about FreeBSD 8.3 yet. I rummaged around in the README it left in the ../work directory and saw a bunch of AMD64 versions up to 8.1 (and even 9.0) but not 8.2 or 8.3. I noticed in the Makefile where it says: IGNORE= Supports FreeBSD 8.0 and later I am not sure how that plays in it. I am definitely not a make hacker. Anyway, is there a good tinker to get past this or do I have to wait until something gets updated in the port? Or, did I just do something stupid? By the way, I need just the client. I do not intend to start a server or a cell on this machine. I just need to talk to the cell at work. Is there a way of only installing the client? (I think the client is the biggest part, but still, do not need the server part hanging around if it would work happily that way) Thanks for any help, jerryJerry McAllisterjerr...@msu.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Building FreeBSD to install or update in two DESTDIRs
> What exactly went wrong? Setting DESTDIR is the correct way to do this > sort of thing. You only need to set it when running the installworld or > installkernel steps though -- there's nothing that gets compiled into > /usr/obj which prevents you from installing into a different than normal > tree. > I use this sort of construct frequently for updating jails, or when > managing boot environments. > > /usr/src/UPDATING doesn't say how to update for two DESTDIRs on the > > same build. > For each different DESTDIR, just repeat the installworld, installkernel, > check-old, delete-old* steps setting DESTDIR=/some/where > on the make command line. > The equivalent for mergemaster is to add '-D /some/where' to the > commandline. > Cheers, > Matthew > -- > Dr Matthew J Seaman MA, D.Phil. I guess after the first installkernel, to default location, I should immediately make installkernel again, this time with DESTDIR=/mnt? Better to "make buildkernel" and "make installkernel" as two separate steps, rather than "make kernel"? After rebooting single-user, do "mergemaster -p", then "mergemaster -p -D /mnt", and then "make installworld" and immediately following that, "make installworld DESTDIR=/mnt" ? After that, I would do "mergemaster -i" followed by "mergemaster -i -D /mnt"? And then make delete-old followed by "DESTDIR=/mnt make delete-old"? Would I need to do "make distribution"? First time, "make installkernel DESTDIR=/mnt" only installed part. I installed to USB stick only after fully upgrading on main installation, finally copied /boot/kernel directory, and that USB stick is now bootable. So now I know how to make a USB stick bootable with GPT. Maybe some of the files were cleaned out? It is surely useful to have a rescue backup, considering the possibility of an update going awry on the main installation. Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: AFS install
Hi Jerry, On Mon, 14 May 2012, Jerry McAllister wrote: Hi, I installed AMD64 FreeBSD 8.3 on a new machine a couple of days ago. It seems fine so far. This afternoon I tried to install OpenAFS 1.6.0 on it from /usr/ports/net/openafs The configure ran happily and I didn't notice any errors. But, the make died soon after starting with the following complaints. make: don't know how to make ./param.amd64_fbsd_83.h. stop *** Error code 2 Stop in /usr/ports/net/openafs/work/openafs-1.6.0. ** Error code 1 I presume that means that it does not know about FreeBSD 8.3 yet. That's right; the OpenAFS build system has lots of history behind it, which means that it is not particularly elegant at handling this sort of thing. I rummaged around in the README it left in the ../work directory and saw a bunch of AMD64 versions up to 8.1 (and even 9.0) but not 8.2 or 8.3. I noticed in the Makefile where it says: IGNORE= Supports FreeBSD 8.0 and later I am not sure how that plays in it. I am definitely not a make hacker. Anyway, is there a good tinker to get past this or do I have to wait until something gets updated in the port? Or, did I just do something stupid? No fault on your end; I need to push in updates for 8.3 and 10.0 support but have been busy with schoolwork. For now, if you're up for a little bit of tinkering, you could go in to /usr/ports/net/openafs and 'make clean && make extract', then: cd work/openafs-1.6.0/src/config && cp param.amd64_fbsd_82.h param.amd64_fbsd_83.h and continue with the usual make install, etc., in /usr/ports/net/openafs/. If that still does not compile/run, please send me the build log (or dmesg -a output if a runtime failure) and I will look at it. By the way, I need just the client. I do not intend to start a server or a cell on this machine. I just need to talk to the cell at work. Is there a way of only installing the client? (I think the client is the biggest part, but still, do not need the server part hanging around if it would work happily that way) The upstream OpenAFS build system is not condusive to just building the client; I have asked about this. It is fairly easy to just build the server, but since my interest was mostly in the client I did not add an option for doing so. Thanks for the report, and sorry to have been so slow at catching up to 8.3/10.0. -Ben Kaduk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
