Search results

Contextually, yes. However, and maybe it's because I only use bash as my shell, by itself the ? character is usable as a file name. [root@sigma ~]# ? su: ?: command not found When assigned to an alias: [root@sigma ~]# alias ... alias ?='cat /etc/motd; alias' ... The result looks like this...

I deal with routers/switches a lot. It's second nature to utilize the question mark to get a list of commands, like so: Router# ? command This is a command help Displays help info ...etcIt would be useful if this were implemented in some way with default shell aliases. I prefer bash...

In context, yes. That's why I mentioned the scripts provided could certainly be reduced. Unfortunately I lack the /bin/sh skills to accomplish that. Also want to add portmaster to the list of fluid management. Personally I sincerely appreciate everyone's work that goes into improving the...

Just to demonstrate why I'm asking the OP question: Where is psearch (wasn't specified)? Ah, use make search name=psearch to discover where the port is... ironically having to spend more time making the search query, waiting for the result, and cd'ing to the port directory, than getting work...

I like to get to the specified port without having to recall/dig/search/cd (type type type) to which location that port may be in. For this purpose, I created a local tool that instantly assists me in this fashion: [root@sigma ~]# port ncdu [root@sigma /usr/ports/sysutils/ncdu]# port apache...

Thought this might be a bump for the PR department, you know, since comparatively ports are kinda remotely the App store of command line OS. It'd be fun!

>> portsdb -Fu /var/ports/INDEX-10.bz2 100% of 1800 kB 612 kBps 00m03s done [Updating the portsdb <format:bdb_btree> in /usr/ports ... - 25036 port entries found...

Re: pkg update failure Thanks, that was a good lead - the errors have been cleared. I deleted the packagesite line from /usr/local/etc/pkg.conf However, builds would seem to silently end without actually building. I went over to ports-mgmt/portmaster, then make install clean to see if that...

When attempting to update bash due to the recent vulnerabilities, bash requires ports-mgmt/pkg to be updated first. When updating ports-mgmt/pkg via portupgrade or a make install from ports, it fails the build upon installation: ---> Deinstalling 'pkg-1.2.7' ---> Preserving...

It looks like that did the trick. I now have all my files back and the filesystem is reporting proper disk space usage.

I was hoping to avoid booting to single-user mode. Sidetracking for a moment; if there was one thing I'd like to see different about FreeBSD, it'd be being able to do these types of things without rebooting, including resetting kern.securelevel for freebsd-update's, etc. Alright...

I have a USB flash drive that is reporting errors in phases 1 and 4 of fsck. When unmounted or mounted, in read-only or read-write mode, with several combinations of CLI options, this USB flash drive refuses to cooperate. Basically fsck can not get past thinking the drive is in read-only mode -...

I think you may have missed the point of the new installation environment. At this stage, when least configured, unexpected issues should be minimized. Updating is usually a great action to take at this step. With respect to your solid stance on targeting dutiful FreeBSD systems administrators...

Earlier in the year when FreeBSD 9.1 was just being released, I excitedly got to work building a new development server. A couple months ago, I rebuilt my gateway server with a clean 9.1 image, although re-installing several times while testing various things in a fresh new environment. In both...

Ditto.

Looks good, thanks for the info. Staying updated is easy now!

I'm looking for comments / suggestions to improve my general updating script. Its purpose is to maintain system updates, ports, 3rd-party, keep things clean and well behaved. Manual verification of /usr/ports/CHANGES is, well, manual. ;) I also diff the ports list output just to report any...

Considered it, but I think the job is done. Going over each port required by hand seems to be the safer route.

Great information everyone. I like one-look views and concise usefulness to eliminate confusion. FreeBSD9.1's new installer seems to reflect this - very nice. This basic script now tells me the important details of a port immediately. #!/bin/sh ## Purpose: Gives information about a port...

Sharing something I just came across, which has made my life a great deal more pleasant. Rewritten into .bashrc format. ## reveals dependencies of a /usr/ports package alias depends='make pretty-print-run-depends-list' Does what: [root@sigma /usr/ports/lang/rubinius]# depends This port...