Search results

The first message in this thread was posted on Friday. Saturday: https://lists.freebsd.org/pipermail/freebsd-questions/2016-October/273948.html Sunday: https://lists.freebsd.org/pipermail/freebsd-drivers/2016-October/001940.html

Well, that is on using lpr and lpd. Those are the real, original commands that CUPS copied incompatibly and then used the same names. I don't use CUPS for the same reason I don't use inkjet printers: when I want to print something, I want it to print right now, not start a session of debugging...

The CUPS thing is an article, not in the Handbook. There are many users of CUPS, but so far none have submitted up-to-date setup instructions to be included in the printing chapter of the Handbook.

Please do not do set CFLAGS or COPTFLAGS. They lead to mysterious failures and prevent ports that can use real optimizations from using them.

This is the default, probably best to leave it alone.

What is the program?

The time to consider the consequences of doing something is before doing it.

Another option: boot partitions are not required to be first on the disk. So it should be possible to delete swap partitions and recreate them just a tiny bit smaller, or use some free space at the end of the disk. Make your boot partition 512K, no bigger, but no smaller. The small bit of...

This can easily become a flame war, but I'll make some comments in the hope they will be useful as a view from the other side. I'm a FreeBSD documentation committer, experienced with the DocBook markup, have modified the build system, and worked on getting a usable modern translation system for...

!! as input is fine. This is doing it on output. The upstream csh or tcsh mailing list would probably be the place to ask, though.

cat /mnt/win/r/win-xp/windows-xp.gz.* | gzip -dc can be replaced with gzip -dc /mnt/win/r/win-xp/windows-xp.gz.* I think this can also be replaced with zcat /mnt/win/r/win-xp/windows-xp.gz.* I would suggest testing the output partition with file before overwriting it with dd. Also, look at...

First question: why awk? Why not one of the scripting languages that are more powerful? Your system almost certainly has Perl installed, and probably Python. Maybe Ruby. All of these can make it much easier to deal with strings.

It seems like a bug, but I don't know. If !! was included as part of the script, it would make more sense, but just echoing it in output is questionable. If it was being expanded as part of a variable, even. But it was output, not input.

This is very dangerous. Install another drive, and ada0 is not the one you expected. Also, UUOC and writing scripts for csh. Using triple "shriek stops" did uncover a bug, so I'll not mention it otherwise. The bug happens on 10-stable also. Please enter a bug report at...

For some applications, avoiding the round-trip overhead of a filesystem could be a real advantage. But it's nice to have an auto-clearing /tmp too.

tmpfs is faster than a UFS filesystem.

Please don't count on that. We need more help with documentation.

Sorry, don't have time to give more than a cursory response at this point, in no particular order... CVS has not been used for years, so if you see anything suggesting that, it is far out of date and needs to be updated. Wiki documentation is almost always a nightmare. I've told people, only...

...What do you mean? Spaces are allowed in filenames. It's a terrible idea, but it works.

Whoa, that is a strange conclusion. A USB image, which is just a hard drive image, works the same way ISO files work with VirtualBox. An actual physical USB stick is not involved.