Re: rm -R
Wjy are we syill having this conversation? The problem (and its solution) have been raised for at least 39 years. To specify a file, directory, device, whatever, whose leaf name begins with a `-', name it using a leading `./' as in: whatever ./-S That will work for all programs, even those that do not support -- to terminate flags. Furthermore it will support glob patterns. Now was that so difficult? -- dt ___ 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"
xrandr cropping my window
Preamble: % cvt 1600 1280 # 1600x1280 59.92 Hz (CVT 2.05M4) hsync: 79.51 kHz; pclk: 171.75 MHz Modeline "1600x1280_60.00" 171.75 1600 1712 1880 2160 1280 1283 1290 1327 -hsync +vsync Running the following: xrandr --auto xrandr --newmode "1600x1280_60.00" 171.75 1600 1712 1880 2160 1280 1283 1290 1327 -hsync +vsync xrandr --addmode VGA1 "1600x1280_60.00" xrandr --output VGA1 --mode "1600x1280_60.00" yields: Default gamma for IRGB image is 2.20 Compressing colormap ...no improvment [sic] Clipping image...(Adding border)...done Building XImage...done It does accomplish most of what I want, but indeed added a black border at the top of the display. The root window has geometry 1600x1280+0+0, however the area that's visible on the display is approximately 1520x1200. This means that when maximizing a window, the bottom and left edges are not displayed. Are there adjustments I can make to get my full screen? -- david ___ 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"
where's ppmtoxpm
I have searched for ppmtoxpm in ports and in FreeBSD Search Services to no avail. ppmtoxpm converts a portable pixmap into an X11 pixmap. Is there a freebsd equivalent or alternative? -- david ___ 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"
Attaching a monitor via vga
I have a thinkpad t61p running freebsd9.0. The window size is 1680x1050 -- a reasonable size -- but the screen itself is 38cm. (15") which is irritatingly small for my old eyes. So I want to attach an external monitor via a vga cable, which I have been doing with my RedHat thinkpad A31P for years. I tried attaching Asus VE228H (1920x1080) but it would display only part of the window (the top-left corner). I get a similar behaviour with a Samsung SyncMaster. When I tried to xinit with the monitor attached, it displays an even smaller part of the screen. (On my previous thinkpad with a Samsung, to get a reasonable full window I had to unplug the vga, start xinit, and then plug in the vga, but I can live with that.) My questions: 1) What can I do to display the whole window on an external monitor? 2) Is there a monitor out there that would better support such use? 3) Would a Samsung T220HD 22" which claims to support 1680x1050 work, and is there someone in Toronto who sells it and would let me test it? (Craigs list doesn't qualify). -- david ___ 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: `ls -l` shows size of file other than of the folder?
What you have are sparse files. The size listed by ls -l is the
length of the files as if all the file from start to end contain data,
but unix allows one to seek beyond the end of a file and add more data,
thus leaving unused blocks. A common example of sparse files
is the *.pag file in a dbm database as created by Ken (Thompson).
The ls -s flag will show you how many real blocks are used.
The program stat(1) will also show you the number of blocks used.
The following creates a file with a size of 102402 (a gig),
that actually contains only 2 chars.
#include
main()
{
fwrite("a", 1, 1, stdout);
fseek(stdout, 100*1024, SEEK_END);
fwrite("b", 1, 1, stdout);
}
cc foo.c ; ./a.out > ,z ; ls -ls ,z
You can od ,z
Old codger story from the distant past (circa 1975):
When we were using rk05s as our disks, we had to watch
for programs that used to fill-in the holes as we often
had files that had sizes that were bigger than the amount
of storage on an rk05 (5 Meg). Yes people used to live
that way.
>From the not so distant past (1985): The Andrew File system
at CMU used to fill in the holes as it copied files from the
file servers to the local host, and back again -- yh.
-- david
On Wed, Jun 13, 2012 at 4:23 PM, Peter Vereshagin wrote:
> Hello.
>
> I have the directory in the file system with 2 regular files each of which
> is
> sized as 700M according to 'ls -l'. But the torrent client and 'du -s' and
> 'ls
> -l's 'total' show that the directory size is 300M.
>
> How can that be? Are there different file sizes stored on a ufs1 in
> their
> metadata?
>
> ot the least how could I see the 'real' size of each of those files, both
> ~150M
> actulally, with a system command?
>
> Thank you.
>
> --
> Peter Vereshagin (http://vereshagin.org) pgp: A0E26627
> ___
> 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-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
changes to ioctl has me flumoxed
To support my line editor I used to use: sgtty.c_lflag = ISIG; sgtty.c_iflag = BRKINT | IGNPAR | IXON | ICRNL; sgtty.c_oflag &= (ONLCR | OPOST | TAB3); sgtty.c_cc[VMIN] = 1; sgtty.c_cc[VTIME] = 1; iotcl(0, TCSETAW, &sgtty); but this no longer appears to work in that input lines are repeated and the writes to reflect chanes are not done. What should I be changing in the above, or what do I need to add? -- david ___ 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"
