Re: switching bsdlabel's label
Jerry McAllister escreveu: On Wed, Jan 21, 2009 at 10:45:28AM -0200, Eduardo Meyer wrote: On Tue, Jan 20, 2009 at 4:42 PM, Jerry McAllister jerr...@msu.edu wrote: On Tue, Jan 20, 2009 at 03:36:34PM -0200, Eduardo Meyer wrote: On Tue, Jan 20, 2009 at 2:13 PM, Patrick M. Hausen hau...@punkt.de wrote: Hello, On Tue, Jan 20, 2009 at 01:24:27PM -0200, Eduardo Meyer wrote: I have a certain disk where da0s1a and da0s1d are inverted. By some reason someone labelled root as 'd' and home as 'a'. Can I just bsdlabel -n da0s1 savedabel.txt Edit savedlabel.txt, switch and restore? (bsdlabel -R da0s1 savedlabel) Why not simply use bsdlabel -e da0s1? Because I didnt know about that? ;-) Thank you for the hint. However I still have the same doubt. Since basically its the same task, Is it safe do relabel this way? Hmmm. Is there stuff written on the disk. Is root stuff really written on da0s1d and /home stuff really written on da0s1a? Does the system boot from it OK? Or is it just that the mounts are switched. The mount points are not written in to the label. That comes after booting. If it boots, I wonder if it really is switched on the partitions or if it is just that the partitions are mounted backwards (probably due to editing /etc/fstab incorrectly). jerry Hello Patrick, thanks again. Yes, label is switched. Yes there really are stuff on the partitions. No, I dont boot from da0s1d. It is a disk for migration. But the one who partitioned was fooled by Sysinstall which creates the first label on extra disks as 'd' and the last from the allowed 7 as 'a'. Therefore this server is still booting on the original disk (ad6s1a) and everything else is mounted in the new one (da0s1), everything but root. What sysinstall does is assume that the 'a' partition will be used for a root mount and the 'b' partition will be used for swap. Sinc 'c' is reserved, it starts with 'd'. Then, if you later add an 'a' it will end up being later (higher offset) than the 'd'. I suppose it might confuse a person, but otherwise it is no problem and probably would be best to just leave it that way. You really only need to use the mount point anyway most of the time. So, if the mount point addresses the partition you want to with that name, then you should have no problem. You could switch it around using bsdlabel, but I don't think the risk would be worth the negligible gain. But, do as you wish. jerry Kind regards, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 i...@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 Hello, Yes, you can do this change anytime you want, since (1) da0s1* are unmounted and (2) disk is clean. Therefore I suggest you are in single user mode. If you feel unsure, backup the current label scheme with disklabel da0s1 -n da0s1.disklabel.bk You can restore anytime with the Rescue Disk. Go ahead, no problem. Sometimes you will really have problem booting from a disk if root is not on label 'a'. I believe it can be workarounded, but your will is safe, go ahead and switch the labels. You can always remember the person who did this from sysinstall that sysinstall will label as 'a' if the mount point is root (/). Therefore if someone wants to use sysinstall for labelling in production, and wont mount on / since / has the current root, one can always fool sysinstall, (C)reating the partition, using / as mpoint and mater redefining the (M)ount point to somewhere else, say, to /mnt. I always relabel this way, never had a problem. TinyBSD sometimes relabels this way too, for some PC Engines Wrap boards. Go ahead. -- Patrick Tracanelli Tel.: (31) 3516-0800 316...@sip.freebsdbrasil.com.br http://www.freebsdbrasil.com.br Long live Hanin Elias, Kim Deal! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
MFC Request
Is it possible to have traceroute MFC'd for 7.1? I would like to have -a and -A switchs (ASN Path mapping) available. Thank you :) -- Patrick Tracanelli ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Script-friendly (parseble) ps(1) output?
Eduardo Meyer escreveu: [...] Now my next problem, do the sabe with sockstat %sockstat | head -4 USER COMMANDPID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS freebsdsupportsshd 57255 3 tcp4 172.16.0.225:22 172.16.0.69:63583 freebsdsupportsshd 57255 4 stream - ?? root sshd 57253 3 tcp4 172.16.0.225:22 172.16.0.69:63583 So I have the USER and COMMAND column merged in a single string, because username is large. Again, space can not be used as a separator, but hopefully only the patterns with - will have space if not a column separator, easier to parse. But sockstat have no formatting option to be issued like -o from ps(1). Measing in the very first sockstat output, I dont know what to do... :( You wont be able to parse it. I believe sockstat was written when username was limited to 8 chars. Therefore, it will count until the 9th position to print another space. I dont know if patching is an option for you, but you can truncate the username printing up to 8 chars. This is the huge patch which will make your output look better and get fully parseable: --- sockstat.c.orig 2007-06-16 17:24:55.0 -0300 +++ sockstat.c 2008-10-30 21:57:05.0 -0200 @@ -586,7 +586,7 @@ if ((pwd = getpwuid(xf-xf_uid)) == NULL) pos += xprintf(%lu, (u_long)xf-xf_uid); else - pos += xprintf(%s, pwd-pw_name); + pos += xprintf(%.8s, pwd-pw_name); while (pos 9) pos += xprintf( ); pos += xprintf(%.10s, getprocname(xf-xf_pid)); -- Patrick Tracanelli FreeBSD Brasil LTDA. Tel.: (31) 3516-0800 [EMAIL PROTECTED] http://www.freebsdbrasil.com.br Long live Hanin Elias, Kim Deal! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
UPEK/TouchChip Biometric Device problem
Hello all,
I have used the mentioned devices on FreeBSD 5.4 in the past, and they
worked just fine, but now I get problems with the same device, on top of
6.2-STABLE and also 7.0-CURRENT.
From `usbdevs -v`, I get:
Controller /dev/usb2:
addr 1: full speed, self powered, config 1, UHCI root hub(0x),
Intel(0x), rev 1.00
port 1 addr 2: full speed, power 100 mA, config 1, Biometric
Coprocessor(0x2016), STMicroelectronics(0x0483), rev 0.01
port 2 powered
I have security/bsp_upektfmess, security/pam_bsdbioapi and
security/bioapi installed. It is a 6.2-STABLE system from 2 hours ago.
Listing bsp devices, I get:
# bbdm -l bsp
UUID {----}
Example Vendor libbioapi_dummy100.so (BioAPI v1.1 Dummy BSP)
UUID {263a41e0-71eb-11d4-9c34-12403700}
BioAPI Consortium libpwbsp.so (BioAPI Password BSP)
UUID {5550454b-2054-464d-2f45-535320425350}
UPEK, Inc. libtfmessbsp.so (TouchChip TFM/ESS Fingerprint BSP)
Backend configurations:
# bbdm -l birdb
Installed BIRDB modules
filedb Filebacked database (b-tree)
plainPlain text file
And now, the problem:
# bbdm -b {5550454b-2054-464d-2f45-535320425350} -m filedb -c eksffa
bbdm: Failed to initate BSP {5550454b-2054-464d-2f45-535320425350}
And on /var/log/messages as well as dmesg, I get:
All threads purged from ugen1.1
All threads purged from ugen1.2
All threads purged from ugen1.3
What is this about threads purged? Also, the port want libintl.so.6
while 6.2-STABLE has libintl.so.8. I have tried 1) linking .8 to .6 and
also copied .6 from another system (also, 6.2-STABLE) to the current
one. Didnt work both way. Same behavior, exactly.
On 7.0-CURRENT things are worse. libpthread is not found, and the same
command core dumps. Anyway, 6.2-STABLE is more important to me right
now, since I need this device to work on FreeBSD for an ongoing project,
but if a solution to 7.0 happens first my work can move to that version.
Can anyone help me?
Thank you.
--
Patrick Tracanelli
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Clamav-90_2 Lockup with freebsd 6.2
Had a similar behavior here, but with other MTA (qmail, clamdscan getting used from simscan). After raising MaxThreads from 10 (default) to 40 CPU usage got back to its normal consuming level. No idea if this info can help, but that was my recent experience. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: possible ifconfig / wi bug?
There have been patches floating around for a while to do tx rate control in the driver instead (in which case this info would be available) but they were never committed because of reported bugs. It might be time to just commit the code anyway (to HEAD) in order to force the bug(s) to be resolved. I have used this port of NetBSD's rssadapt, and I have not noticed bugs (maybe it just works fine on my enviroments, but not with other's), using Prism (Senao mini-pci). http://bsd.mikulas.com/wifi/wi-rssadapt-RELENG_6-20051014.patch Would be nice to see it in HEAD with potential MFC soon after (if) bugs get found/corrected. -- Patrick Tracanelli ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bruteforce
Jordan Sissel wrote: On 4/11/06, Daniel Gerzo [EMAIL PROTECTED] wrote: Hello Dmitriy, Tuesday, April 11, 2006, 7:04:37 PM, you typed the following: On Tue, Apr 11, 2006 at 10:58:48AM +0200, Matteo 'egon' Baldi wrote: Hy, I'm triing to find a solution to bruteforce attack, mostly on port 22, without moving services on different ports. try to use /usr/ports/security/sshit maybe security/bruteforceblocker If you're looking for something with a more generalized approach, check out sysutils/grok. It comes with examples that block brute force efforts, and can do much more. Doesnt open sshd itself has a feature which blocks or imposes a delay upon a number of failed logins from the same address? -- Patrick Tracanelli ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: away
Joao Barros wrote: On 3/30/06, Adam Retter [EMAIL PROTECTED] wrote: Who attacked him, can we not give them a kicking ;-) At most a kick on IRC since the person in question is also a valid FreeBSD developer. I read most of -current, -stable, -hackers, -cvsall as well as some other FreeBSD lists and sometimes I read someone's comment and think: That was totally unnecessary... But people are all not the same and we have our good days and our bad days. I guess David was on a bad day when Dag wrote what he wrote, on a bad day himself. I have been accompanying David and Dag's work and both are important and needed and have their credit for, no doubt about it. David, Dag has done the more difficult part: recognizing and apologizing. From there, forgiving is easy ;-) Can't we all just code along? :-D I completly do agree with every single statement Joao has made. It could have been kept on private mailing list. From what it looks like for people like me, when-possible contributor and every-day-user, It seems to be just a simple work discussion, like those ones which usually happen one day or one other in everywhere there is work getting done by more than one person, a cooperative working-style discussion on what is good and what can be done in different (hopefully better) way. Accepting and interpreting suggestions as well as suggesting on a non-rude manner is something that everyone one day fail, in their busy heavy days. No big deal, It is human nature. Anyway, everyone who follows cvs-all@ is very thankfull for what David has done everyday in the system, and probably will appreciate a lot more if Mr. Xu decide to keep doing the good work, improving what he has noted himself that should be improved and work together with others to improve things that more than one brain could probably get better results than only a single one. Hope you stay. Osho in one of his books usually say that apologizing is a difficult decision, apologizing honestly is even more difficult and rare. And do not accepting the honest apollogies is a severe decision and as such, comes with a lot of consequences. -- Patrick Tracanelli ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ifconfig hidessid not hiding SSID on 802.11b with PRISM 2.5 based card
I have set hidessid option to an Intersil PRISM 2.5 based cart, acting as hostap, and the ssid stills gets broadcasted, aparently. Other FreeBSD systems and the Windows software supplied by the vendor can find the SSID while scanning. I would like to know if hidessid should hide it in ordinary scans like those ones, and how to test it better to see if ssid stills broadcasted in the beacons, if it is possible (say, any debug option or tool). Thanks! -- Patrick Tracanelli ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TinyBSD Call For Testers
Hello Marten, Thanks for your input. Yesterday sysutils/tinybsd was updated to reflect fetching the new 0.2 TinyBSD which has some improvements related to lib depends, specially pam as it was not functional on tinybsd (opie related problems) in FreeBSD 6 like it was in RELENG_5 before. Also, new entries were added to the kernel (commented, by default) with the new atheros entries (ath rate is probably what is causing your problem, uncomment it on the new 0.2 tinybsd to build your system under FreeBSD 6). Also, your change on ttys will probably be interesting for other users too. It makes me think that it is probably time to maintain a separated etc/ customized tree under tinybsd development dirs, in a PicoBSD fashion. In fact it is already added to the TODO listing for TinyBSD. I believe it is a better way than changing anything under etc/ without the embedded system developer explicity will. Please, if you get the same (or new) problems under FreeBSD 6 w/ TinyBSD 0.2, send a note. -- Patrick Tracanelli FreeBSD Brasil LTDA. (31) 3281-9633 / 3281-3547 sip://[EMAIL PROTECTED] http://www.freebsdbrasil.com.br Long live Hanin Elias, Kim Deal! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TinyBSD Call For Testers
Norbert Koch wrote: Hello, thank you for your posting. Can you explain, how it compares to minibsd [https://neon1.net/misc/minibsd.html]? Norbert It is similar to minibsd in the copy proccess, but different in the configuration and image creation stages. TinyBSD does not heavily depend on chroot enviroment, it works directly in a work directory, where files copying, kernel build and hier(7) definitions are used in such an usual FreeBSD building enviroment, including mtree definitions in /etc/mtree/, using make DESTDIR and make DISTRIBUTION whenever it is possible. In fact it is pretty much closer to NanoBSD in the whole proccess, while only similar to minibsd in the copy idea. -- Patrick Tracanelli FreeBSD Brasil LTDA. (31) 3281-9633 / 3281-3547 sip://[EMAIL PROTECTED] http://www.freebsdbrasil.com.br Long live Hanin Elias, Kim Deal! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Possible exploit in 5.4-STABLE
[skip] to attach the binary, but I'll do it anyway because I don't have anything else but that and a readme file. It didn't seem to work (out of the box) with 5.4-RELEASE though. This is a translation from babelfish: Plain replacement of standard su for FreeBSD. It makes it possible to become any user (inc. root) with the introduction of any password. For this necessary to neglect su with the option -!. with the use of this option does not conduct ravine- files. Was tested on FreeBSD 5.4-STABLE. My apologies if I am sending in something completely useless and not important, but I figured it wouldn't hurt just to make sure. Cheers, The attached file needs to be setuid to root, so, someone needed to have increased privileges before, in order to install this prg. In this case a one-line C program w/ root setuid would do the same job. -- Patrick Tracanelli patrick @ freebsdbrasil.com.br Long live Hanin Elias, Kim Deal! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
