Re: recovery from terminated make installworld?
Freddie Cash writes: > On Thu, Mar 18, 2010 at 1:07 PM, Justin Hibbits wrote: > >> On Thu, Mar 18, 2010 at 4:03 PM, Anton Shterenlikht > >wrote: >> >> > I was in the single user mode doing 'make installworld' >> > when the system froze and I had to cold reboot. >> > Now in single user mode I get to: >> > >> > Enter full pathname of shell or RETURN for /bin/sh: >> > /libexec/ld-elf.so.1: /lib/libc.so.7: invalid file format >> > /libexec/ld-elf.so.1: /lib/libc.so.7: invalid file format >> > Enter full pathname of shell or RETURN for /bin/sh: >> > >> > Is there a way to recover? >> > Or do I have to reinstall from scratch? >> >> Try /rescue/sh (or tcsh). It's all statically linked, so you should be >> able >> to recover from there. >> >> And if that doesn't work, try a LiveFS CD. > > And, if all else fails, you can do a minimal install overtop. You'll lose > all your /etc settings, but will get a bootable system again. A lot of the time, an "upgrade" binary install will do the job, with less risk to your /etc directory. I had a problem like this not that long ago, thanks to the new kernel crashing (but not until I'd had time to start the installworld). Going back to the old kernel and copying in the libraries that didn't work was enough to get me up enough to retry the upgrade with a GENERIC kernel. I don't generally recommend running -current to anybody unless they have some comfort with recovering from these kinds of problems... ___ 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: bzip2recover isn't compiled/installed during build/install world (STABLE & CURRENT)
Nuno Teixeira <[EMAIL PROTECTED]> writes: > I noted that bzip2recover isn't installed during build/installworld. I > think it may be something related with it makefile. > > This happens on both STABLE and CURRENT brach. > > I someone could correct this, I apreciate that. I don't think it's a mistake. It isn't needed or used for the regular system operation, so there's no need for it to be in the base system. If you want it, installing the port is a trivial way of getting it into your system. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unable to boot 5.0-R CD error
Stephen Cravey <[EMAIL PROTECTED]> writes: > I'm getting an error when trying to boot any of the 5.0-RELEASE cd's > something like: > > CD Loader 1.01 > Building txxx boot loader arguments > Could not find primary volume descriptor > > > and then it dies there. txxx is illegible in my notes, but somehow I don't > think that is significant. When booting from floppy, I have to install > additional drivers from the driver floppy to be able to install from CD. > > The device line from dmesg after installation is: > > acd0: CDROM at ata1-master PIO3 > > I have a vague recollection of a problem similar to this sometime in the > 4.x tree, but specifics totally escape me. If you can boot from floppy, do that. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why panic(9) ?
[Replies redirected.] Boris Kochergin writes: > All modern operating systems? Maybe some niche ones, like the ones > that run on Mars rovers, have made progress towards formal > verification and are believed not to crash given correctly-functioning > hardware. The Mars rovers run on VxWorks. Which is a system I like, but it isn't anything like formally verifiable. And it certainly does the equivalent of FreeBSD panic() under some circumstances. ___ 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: "authenticated tftp"
Maxim Konovalov <[EMAIL PROTECTED]> writes: > On Fri, 25 Jul 2003, 13:22-0400, Robert Watson wrote: > > > > > Yeah, seems like an oxy-moron, but this is a legitimate question, I > > promise. My linksys wireless router requires me to disable the admin > > password on it to tftp a firmware update to it--however, the Windows tftp > > client that Linksys ships appear to support some form of "Oh yeah, and > > here's a password". It probably really doesn't make a difference > > security-wise, but it would be a lot more convenient to update wireless > > routers if our tftp client spoke whatever extension they use to carry the > > password. Does anyone know anything about that protocol extension, or if > > there are existing tweaks to add it to our tftp? (I saw nothing in the > > man page). If there's a pointer to the on-the-write bits, I can always > > stick it in myself, but I have yet to find one. > > There are several tftp extension that NetBSD folk integrated to their > tftpd/tftp recently. IIRC they were > > 2347 TFTP Option Extension. G. Malkin, A. Harkin. May 1998. (Format: > 2348 TFTP Blocksize Option. G. Malkin, A. Harkin. May 1998. (Format: > 2349 TFTP Timeout Interval and Transfer Size Options. G. Malkin, A. > > I know nothing about auth extension yet but the protocol is quite > simple (trivial :-)) and if you get a dump of udp session between the > router and windows tftp client it would be easy incorporate this one. Just to explain further what Maxim is pointing out here: the authentication option, whatever it is, is *not* a standard, unlike the ones he listed. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cdparanoia in the ports fails.
"Sweetleaf" <[EMAIL PROTECTED]> writes: > I am trying to get cdparanoia from the port to compile but am running > into the following: > > ===> Building for cdparanoia-3.9.8_5 > cd interface && gmake all > gmake[1]: Entering directory > `/usr/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface' > gmake libcdda_interface.a CFLAGS="-O -O -mcpu=pentiumpro" > gmake[2]: Entering directory > `/usr/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface' > cc -O -O -mcpu=pentiumpro -c scan_devices.c > cc -O -O -mcpu=pentiumpro -c common_interface.c > cc -O -O -mcpu=pentiumpro -c cooked_interface.c > cooked_interface.c: In function `cooked_read': > cooked_interface.c:204: error: storage size of `arg' isn't known > cooked_interface.c:215: error: `CDIOCREADAUDIO' undeclared (first use in > this function) > cooked_interface.c:215: error: (Each undeclared identifier is reported > only once > cooked_interface.c:215: error: for each function it appears in.) > gmake[2]: *** [cooked_interface.o] Error 1 > gmake[2]: Leaving directory > `/usr/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface' > gmake[1]: *** [lib] Error 2 > gmake[1]: Leaving directory > `/usr/ports/audio/cdparanoia/work/cdparanoia-III-alpha9.8/interface' > gmake: *** [all] Error 2 > *** Error code 2 > > Stop in /usr/ports/audio/cdparanoia. > > > system: > > freebsd 5-current > > ports 5-current Well, no, the latest cdparanoia port is cdparanoia-3.9.8_6. That fixed the problem you're seeing. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: AW: 5.1. does not boot afte installation
I'm moving this to -CURRENT, as 5.x is *not* the stable branch. Also, please don't top-post. "Hutterer Robert" <[EMAIL PROTECTED]> writes: > Disabling ACPI in BIOS has no effect. Still no reboot > Disabling in the /boot/loader.conf also. No reboot > Disabling in BIOS and loader.conf. No reboot Did you try all of the suggestions in the release errata? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: swap on Irix (overcommiting, etc.)
Mikhail Teterin writes: > Sorry. I'm just repeating what Ladavac Marino wrote in > <55586e7391acd211b973c1100276179...@r-lmh-wi-100.corpnet.at>: > > LM: Please note that memory overcommit architectures are a > LM: rather common optimization; FreeBSD is one of them. They > LM: do, however, break the ISO/ANSI C conformance (strictly > LM: speaking). > > Since there was no immediate (nor later) rebuttal, I assumed, that > everyone quietly agreed... Absolutely not. It is *definitely* okay for system conditions outside the realm of the C spec to effect the execution of "conforming" programs. Otherwise, having a system shutdown interrupt the program would be enough to make the system non-conforming. Heck, the *existence* of kill(1) and SIGKILL would be enough to make for a non-conforming C environment. The system running short on virtual memory (whether it be by having a user program touch memory it had previously allocated, or by having a new user log in, or a new sendmail daemon starting up) fits squarely into that category. How (and when) you assign backing store to virtual memory is a *very* interesting topic, but the ISO C compliance issue is a red herring, even to the most pointlessly pedantic language lawyers. Be well. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: periodic script in base system to run csup
Alex Kozlov writes: > On Fri, Jul 16, 2010 at 04:27:39PM +0200, Gabor Kovesdan wrote: >> Em 2010.07.16. 16:23, Alex Kozlov escreveu: >> > On Fri, Jul 16, 2010 at 03:58:33PM +0200, Gabor Kovesdan wrote: >> > >> > Thousands pc simultaneously try to access cvsup servers? >> > Sound like a ddos to me. >> Yes, this was the only concern and that's why I started this discussion. > And because its periodic, We can't use portsnap solution (random delay > before csup start). It's not completely impossible; periodic could spin off a separate shell for it, with a random delay. It's not clear what the best way to deal with the output would be, although several approaches present themselves. It would be a lot more complicated than Gabor's approach, though. ___ 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: $DISPLAY not set
[Replies redirected to a more appropriate list.] Paul Cartwright writes: > I have installed freeBSD & have it running. I was trying to install MATE > & KDE4, but I'm getting an error. > everytime I try to run exec startkde it logs me out with this message: > > $DISPLAY is not set or cannot connect to xserver > > > echo $DISPLAY says > DISPLAY: undefined variable > > I was using this guide to set everything up: > https://cooltrainer.org/a-freebsd-desktop-howto/#with-radeon-intel-or-otherwise > > am I missing something? Well, you're missing the FreeBSD documentation, which is a lot better than a random Google result. https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x11.html Or you might want to try PCBSD (www.pcbsd.org) which will require a lot less understanding of what is going on (at the cost, as usual, of giving you a lot less choice, at least initially). The "exec startkde" is supposed to go in your .xinitrc file, in which case you would start X with the "startx" command. > I do have an /etc/X11/xorg.conf, I did do the X -configure. Usually unnecessary, and not a great idea unless it is necessary. ___ 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: request for crypto hardware...
John-Mark Gurney writes: > I have some plans to improve the opencrypto framework in FreeBSD later > this year. This will require invasive changes to the various drivers. > So, I'd like to line up hardware/volunteers before then. > > If you would like to see your hardware tested and verified to work > with the new changes, please contact me w/ either a donation of > hardware, money to purchase hardware, or if you have hardware, that > you volunteer to test changes. > > I currently have the following hardware: > aesni > > I do not have the following hardware: > hifn > ubsec > padlock (VIA C3, C7 and Eden) I have a mini-ITX VIA C3 board (EPIA ML, fairly early model) sitting around doing nothing. I could probably cobble together a power supply, RAM, and so on to put around it as a testing system, but I'd be happy to ship it to you if you'd like. It's a pretty nice board, actually; I'd probably have turned it into a firewall by now if its support for SSDs were a little better. My home server has a Via C7, and I'd be happy to test on that if it can be done without leaving the house without Internet access for days. > cesa (Marvell, missing man page) > glxsb (AMD Geode LX, such as Sokris Net5501, missing man page) I think I've got access to a dev board with one of these chips. I haven't seen it lately, but I'm sure I can dig it out if necessary. > safe (SafeNet) > sec (Freescale, missing man page) > cryptocteon (Cavium Octeon, missing man page) > nlmsec (mips/nlm/dev/sec/nlmsec.c, missing man page) > rmisec (mips/rmi/dev/sec/rmisec.c, missing man page) ___ 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: HELP: Howtwo create a passwd-suitable hash for usage with psswd -H 0?
Allan Jude writes:
> On 2016-02-18 10:29, O. Hartmann wrote:
>> I'm now down to a small C routine utilizing crypt(3). But this is not what I
>> intend to have, since I want to use tools from the FBSD base system.
>>
>> I build images of a small appliance in a secure isolated environment via
>> NanoBSD. I do not want to have passwords in the clear around here, but I also
>> do not want to type in everytime an image is created, so the idea is to have
>> passwords prepared as hashes in a local file/in variables. Therefore, I'm
>> inclined to use the option "-H 0" of the pw(1) command to provide an already
>> and clean hash (SHA512), which is then stored in /etc/master.passwd.
>>
>> It is really funny: passwd or pw take passwords via stdin (-h 0 with pw) and
>> they "generate" somehow the hashed password and store that in master.password
>> - but I didn't find any way to pipe out the writing of the password to the
>> standard output from that piece of software. Why? Security concerns I forgot
>> to
>> consider?
>>
>> I found lots of articles and howtos to use pipes producing the required
>> password hashes via passwd, chpasswd or pw, but they all have one problem: I
>> have to provide somehow the cleartext password in an automated environment.
>>
>> Maybe there is something missing ...
>>
>> oh
>> ___
>
> pw is using crypt() to turn the raw password into the password hash you
> see in master.passwd.
>
> The sha512 tool cannot do this, as that is 'sha512' (designed to be as
> fast as possible), and what crypt() uses is 'sha512crypt' (designed to
> be purposefully slow, does 5,000 sha512s by default, but is tunable by
> setting rounds=1$ as a prefix to the salt when calling crypt)
>
> crypt("mypassword", "$6$rounds=1$usesomesillystri");
>
> Results in:
>
> $6$rounds=1$usesomesillystri$CtNyZlpTyzaFTivUi7CCBYAoRBZXxSz1qnnGOAb0tXB4irc9/ro10S1a3X2JWTNa1tsMZwIprG/H1o3TKOrDt0
>
> NetBSD has a command for generating hashes on the command line, pwhash(1)
>
> I have wanted to bring something like that over for a while, but looking
> at the source for pwhash I decided I'd want to start from scratch.
"openssl passwd", maybe?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: which "include" being used?
paradox writes: > Why build the world uses /usr/include ? > why not use "include" from the /obj/...include ? First it builds the toolchain, including the include files (as well as the compiler, etc.). To do this, it has to use the system include files. Once that is done, it uses the newly built tools and not the system ones. > issue to "build world" with loss of multiple files at /usr/include/ You'll need to restore them some other way to be able to run buildworld. Assuming you build and install the world successfully, you will then have a correct set of files in /usr/include. ___ 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: CVS removal from the base
Tom Evans writes: > On Sat, Dec 3, 2011 at 3:24 PM, Max Khon wrote: >> CVS != csup. >> >> I wonder how many people will express their sentiments about CVS when >> they really mean cvsup/csup. > > I wasn't going to jump onto this bikeshed, as CVS will not be going > anywhere any time soon, I am sure. > > I use cvs, rather than csup. I use cvsup to fetch CVS archives to > /home/ncvs, and check out ports from there, as described in > development(7). > > If ports were no longer delivered via CVS, you may have had a point > about removing CVS from base - but they are not. Max Khon was the one who posted the original message in the thread. That message explicitly stated that moving ports and doc away from CVS was a prerequisite for removing CVS from base. As far as I've noticed, no one has challenged that. I'm trying to think of a way to fit the previous paragraph into the bikeshed metaphor, but I'm coming up with nothing. ___ 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: Rebuild of xfce4-session
Derek Tattersall writes: > I am trying to rebuild xfce4-session on 10.0 as of r255478. It fails > with /usr/local/lib/libiconv.a missing from libtool. Does anybody have > a clue as to what to do at this point? That library comes from libiconv, not libtool. Sounds like your installation of converters/libiconv is damaged. Probably not related to the version of FreeBSD you're running. ___ 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: nslookup gave misleading results?
Eitan Adler writes: > On Wed, Oct 16, 2013 at 1:42 AM, Kevin Oberman wrote: >> nslookup(1) was deprecated about a decade ago because it often provides >> misleading results when used for DNS troubleshooting. It generally works >> fine for simply turning a name to an address or vice-versa. > > Can you give a bit more detail on this? In what ways did it give > misleading results? A couple of different reasons cited by ISC for why they deprecated it a long time ago: nslookup bundled an internal resolver library, and so it wouldn't always give the same results as other utilities. Also, it always ignored some of the host configuration. -- Lowell Gilbert ___ 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: reproducible panic every day at 03:02, probably triggered by daily periodic scipts - help
Glen Barber writes: > On Thu, Mar 06, 2014 at 07:49:42AM -0800, Anton Shterenlikht wrote: >> >Can you go into /etc/periodic/daily and execute those scripts one by >> >one? You should be able to narrow down which one is the culprit. >> >> unfortunately I cannot reproduce the panic >> this way. What I did was: >> >> # cd /etc/periodic/daily >> # for file in `ls` >> do >> echo $file >> ./$file >> done >> >> I run it twice, I could see all scripts >> executing one after another, >> but no panic. >> Perhaps something else is happening at >> the same time as daily scripts? >> But I cannot find what. >> > > It can also be one of the scripts in /etc/periodic/security. > > Can you retry your test in that directory, as well? "periodic daily" would be a slightly better test... ___ 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: /usr/src: svn status: svn: E200030: sqlite[S1]: near "1": syntax error
"O. Hartmann" writes: > I get this weird error in /usr/src with the port devel/subversion: > > root@thor: [ports] svn st > svn: E200030: sqlite[S1]: near "1": syntax error > > Using /bin/svn everything is clear. > > What happened here? > > OS is > > FreeBSD 11.0-CURRENT #0 r265433: Tue May 6 13:37:15 CEST 2014 amd64 Did you try "svn cleanup"? I'm not sure what /bin/svn is, but I suspect it's relatively lightweight (not keeping the backing database), in which case it's not relevant. ___ 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: Problems building FreeBSD 9.2 on FreeBSD 10
Craig Rodrigues writes: > On Tue, Jun 17, 2014 at 1:05 PM, Simon J. Gerraty wrote: >> >> On Tue, 17 Jun 2014 11:35:42 -0700, Craig Rodrigues writes: >>>Do you know if there is some sort of patch that can be applied to >>>FreeBSD stable/9 sources so that it can be built on a FreeBSD >>>10/stable, or FreeBSD CURRENT >>>host with bmake? >> >> You would likely need to apply many of the changes made in 10. >> IIRC stable/9 has just enough bmake support to be able to build/install >> bmake itself, so that ports can use it. >> >> I'm not sure how many people would appreciate making such changes to >> stable/9 at this point. > > Most users would not care about building stable/9 on a stable/10 host. > There are only a few people care about being able to do that. > People who use poudriere to build a jail to build ports would care. Couldn't they just build the base in that same jail? ___ 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: did tar(1) loose xz compression support in 11?
"Chris H" writes: >> On 8/26/14 11:05 AM, Chris H wrote: >>> Greetings, >>> I'm currently testing 11. My build / install is from about 2 days ago. >>> I generally use xz compression, when creating archives. But when I >>> attempt the following: >>> >>> tar -cvJ --options xz:9 -f ./archive-name.tar.xz ./file >>> >>> it returns the following: >>> >>> tar: Undefined option: `xz:9' >>> >>> This has always worked in previous versions. Has the syntax changed, >>> and the man(1) pages just haven't caught up? >> >> I use: >> tar -cJ --options xz:compression-level=1 >> .. on head. Are you using the right syntax? > Apparently not. Using your example works as expected. > RELENG_8, and RELENG_9 use short-hand; > tar -cvJ --options xz:9 > > Why/when the change to long-hand? Seems a shame. Now I > get to modify all my scripts, and such. :P Altho I > don't suppose it'd be a big deal to back out (revert) the > changes made to tar(1). :) I can't find any changes that would make the syntax change. At least, not in quite a long while. Therefore, this change may not be intentional. However, I looked at the the manual page from 9.3, and its description of the features looks the same as on the latest HEAD, and *doesn't* look like leaving out a "key" (in this case, "compression-level") is ever compliant. You might try the latest (or older) libarchive from the ports, and compare its behaviour. Also, there are a number (amusingly many, in fact) of other ways of specifying these parameters that may be more convenient for you, so another look throught the tar(1) manual might save you a few minutes. Good luck. ___ 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: head && auditdistd
Matthias Apitz writes: > El día Tuesday, May 14, 2013 a las 07:20:02AM -0700, Justin Hibbits escribió: > >> You should run 'mergemaster -p' before installworld, as that would add any >> necessary new users to the file. > > I see no need to run 'mergemaster' if one installs world and kernel into > an empty mount point (device). There is nothing to merge. Fine, if that provides a sufficiently complete system for your needs. That must be a pretty unusual set of needs, though. I'm interested: what do you do with a system that is complete except for not including /etc? ___ 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: 14.1-R rc.conf/ifconfig netmask issue was really hard to figure out
"Poul-Henning Kamp" writes: > Defaulting to a /8 netmask for 192.168.x.y does not make *any* sense ever. Well, not in the last 30 years or so, anyway.
