On Fri, Jan 18, 2013 at 12:10 AM, Waitman Gobble wrote:
> Hi,
>
> I have a PCI Express card with VIA VL800 chipset which seems to work OK
> with a Seagate drive, so I presume the interface is working.
>
> If I boot with a SanDisk ImageMate S11202 plugged into the USB 3.0 card,
> the display shows
Hi,
svn-export has now been rewritten in Python 3. Here's a quick list of
changes/features:
* threads have been replaced with forks (and remain optional)
* new option to set svn binary
* new option to generate shell script instead of using internal calls
* no subshell invocation
* only svn binary
> From owner-freebsd-questi...@freebsd.org Fri Jan 18 17:30:31 2013
> Date: Fri, 18 Jan 2013 18:26:54 -0500
> From: Fbsd8
> To: FreeBSD questions
> Subject: sh script code to get file size.
>
> In a script in am working on I need to find out the allocated
> size of a sparse file.
> The only comm
Hi!
On my home network I noticed that wireless transfer slows down a lot
over time. It starts at reasonable internet speed of 300kB/s or
something but after 2h of using the network it barely gets more than
20kB/s across. Rebooting helps, as does kicking the kernel
module/interface and recreating (
On 2013-01-17 21:32 -0700
Warren Block wrote:
>A working version in any language would be great. A better version in
>Python would be nice, too, but it's the working part that's important.
There's a difference between "working" and "working on a random system with
unexpectedly disabled features
On 18 January 2013 15:08, Bob Willcox wrote:
> Is there a way to repair a GPT partition table that has gotten corrupted
> (following a system hang during heavy I/O to a ZFS filesystem)?
>
> I now get these errors whenever I boot the system:
>
> GEOM: da0: corrupt or invalid GPT detected.
> GEOM: d
Hi,
On Fri, 18 Jan 2013 14:08:25 -0600
Bob Willcox wrote:
> Is there a way to repair a GPT partition table that has gotten
> corrupted (following a system hang during heavy I/O to a ZFS
> filesystem)?
>
I would use a hex editor. Of course, try it out on another disk before
working on that disk.
On Fri, 18 Jan 2013, Fbsd8 wrote:
In a script in am working on I need to find out the allocated
size of a sparse file.
The only command that comes to mind is "ls -lh"
The "du -h" command is not appropriate because it will show
the occupied size and not the allocated size.
I don't know how to pa
Chris Hill wrote:
On Fri, 18 Jan 2013, Fbsd8 wrote:
In a script in am working on I need to find out the allocated
size of a sparse file.
The only command that comes to mind is "ls -lh"
The "du -h" command is not appropriate because it will show
the occupied size and not the allocated size.
I d
In a script in am working on I need to find out the allocated
size of a sparse file.
The only command that comes to mind is "ls -lh"
The "du -h" command is not appropriate because it will show
the occupied size and not the allocated size.
I don't know how to parse out to the position in the ou
On 18/01/2013 23:26, Fbsd8 wrote:
> In a script in am working on I need to find out the allocated
> size of a sparse file.
> The only command that comes to mind is "ls -lh"
> The "du -h" command is not appropriate because it will show
> the occupied size and not the allocated size.
>
> I don't know
In the last episode (Jan 18), Fbsd8 said:
> In a script in am working on I need to find out the allocated
> size of a sparse file.
> The only command that comes to mind is "ls -lh"
> The "du -h" command is not appropriate because it will show
> the occupied size and not the allocated size.
>
> I d
In a script in am working on I need to find out the allocated
size of a sparse file.
The only command that comes to mind is "ls -lh"
The "du -h" command is not appropriate because it will show
the occupied size and not the allocated size.
I don't know how to parse out to the position in the outpu
Hi folks,
I am seeing a problem when copying large files via SMB/Samba from a
FreeBSD 8.0-based system (with Samba 3.6.6 and ZFS etc) where
eventually Windows drops the connection.
However, it seems, based on three captures I have, that what has
happened is that FreeBSD has not supplied any data
Is there a way to repair a GPT partition table that has gotten corrupted
(following a system hang during heavy I/O to a ZFS filesystem)?
I now get these errors whenever I boot the system:
GEOM: da0: corrupt or invalid GPT detected.
GEOM: da0: GPT rejected -- may not be recoverable.
Fortunately,
On Friday 18 January 2013 16:58:11 RW wrote:
> You can carry on using 3.5 on any current release. The problem is when
> it's eventually removed from ports, updating other ports may result in
> dependency problems.
I'm already starting to experience some problems which I assume are due to
incomp
On Tue, Jan 15, 2013 at 10:57 PM, Eitan Adler wrote:
> Hi all.
>
>
> Running FreeBSD 9.1-Release, I am seeing some absurd hangs (10 minutes
> or more to open a file) with SIGINFO informing me that the process is
> stuck on zio->io_cv.
>
> Does anyone have any suggestions for what I want to look a
On Fri, 18 Jan 2013, Polytropon wrote:
On Fri, 18 Jan 2013 16:37:43 +0100, Ralf Mardorf wrote:
Do the following directories have to be "more" empty?
...
If you have copied everything you might need from /usr/local
(e. g. config files in /usr/local/etc) you can remove the
whole directory subtr
On Fri, 18 Jan 2013, Ralf Mardorf wrote:
I wonder how to set a variable to automatically "answer" ok.
In this case it might be interesting to check all configurations.
I use this in /usr/local/etc/portmaster.rc:
# Do not create temporary backup packages before pkg_delete (-B)
NO_BACKUP=Bopt
#
On Fri, 18 Jan 2013 01:25:03 + (GMT)
Georg Reilinger wrote:
> As a consequence, I can see myself do two possible things, to have a
> system
>
> running with KDE 3.5 once again:
>
> 1. Go back to an older release of FreeBSD and install KDE 3.5 from
> the
>
that's pointless
> 2. To be hon
On Fri, 18 Jan 2013 17:03:33 +0100, Ralf Mardorf wrote:
> On Fri, 18 Jan 2013 16:59:55 +0100, Ralf Mardorf
> wrote:
>
> > I stopped by Ctrl + C, add --no-confirm to the command and run it again.
> >
> > To read this mail I had to use the archive, Opera can't display received
> > emails at the
On Fri, 18 Jan 2013 16:59:55 +0100, Ralf Mardorf
wrote:
I stopped by Ctrl + C, add --no-confirm to the command and run it again.
To read this mail I had to use the archive, Opera can't display received
emails at the moment ;).
Thank you!
Oops, I should read more carefully, this doesn't
I stopped by Ctrl + C, add --no-confirm to the command and run it again.
To read this mail I had to use the archive, Opera can't display received
emails at the moment ;).
Thank you!
Regards,
Ralf
___
freebsd-questions@freebsd.org mailing list
http:
On Fri, 18 Jan 2013 10:42:29 -0500, Fbsd8 wrote:
> When dir-path contains data over 7G in size pax issues this error msg,
>
> pax: file is to large for cpio format ./dir-path
>
> How do I correct this?
Maybe by patching or rewriting cpio. :-)
>From "man cpio", the BUGS section contains:
On Fri, 18 Jan 2013 16:37:43 +0100, Ralf Mardorf wrote:
> Do the following directories have to be "more" empty?
>
> root@freebsd:/root # ls -hAl /usr/local/bin
> total 0
> root@freebsd:/root # ls -hAl /usr/local/sbin
> total 0
> root@freebsd:/root # ls -hAl /usr/local/lib
> total 12
> drwxr-xr-x
I use pax this way.
cd dir-path
pax -wzX -x cpio -f path-file-name .
The period at end of above command is part of the command.
When dir-path contains data over 7G in size pax issues this error msg,
pax: file is to large for cpio format ./dir-path
How do I correct this?
_
On 18 January 2013 05:20, Fabian Keil wrote:
> A common recommendation is to disable atime for all datasets where
> it isn't needed as it can cause lots of unnecessary write operations.
Good call. I thought I had already disabled atime updating but it turns out
that some datasets had this proper
On Fri, 18 Jan 2013 15:26:12 + (GMT), Georg Reilinger wrote:
> -- Excuse me... you're joking, right? I assume you have a plentycore
> -- processor with Gigs of RAM, and already two shells show a problem?
> -- That sounds totally wrong.
>
> Is that sarcasm or irony?
I'm not sure. :-)
It just
On Fri, 18 Jan 2013 05:50:51 +0100, Polytropon wrote:
"man portmaster"
root@freebsd:/root # portmaster --list-origins > ~/installed-port-list
root@freebsd:/root # portsnap fetch update
root@freebsd:/root # portmaster -ty --clean-distfiles
root@freebsd:/root # portmaster --check-port-dbdir
del
-- Excuse me... you're joking, right? I assume you have a plentycore
-- processor with Gigs of RAM, and already two shells show a problem?
-- That sounds totally wrong.
Is that sarcasm or irony?
Von: Polytropon
An: Georg Reilinger
CC: "freebsd-questions@fre
On Fri, 18 Jan 2013, Ralf Mardorf wrote:
I had to do a "portsnap fetch update" to compile icedtea-web and run into a
dependency hell. Most apps can't be launched anymore. When I deinstall,
recompile the new versions and install them, I have tons of dependencies for
each app.
portsnap fetch u
On Fri, 18 Jan 2013 15:19:24 +0100, Albert Shih wrote:
> Hi all,
>
> I would like to known how I can create a root-account (uid=0, login not=root)
> but I want this account accessible only on the console. Not from ssh but
> event not from su (other than root).
Add a new account with UID 0 (comp
Hi all,
I would like to known how I can create a root-account (uid=0, login not=root)
but I want this account accessible only on the console. Not from ssh but
event not from su (other than root).
The purpose is to put some trivial password for this account, because those
server run on
vmware a
On 01/18/13 02:29, Fbsd8 wrote:
The man page for tar command says there a 4 different compress types you
can use, xz, bzip, bzip2 and gzip.
bzip and bzip2 are synonyms I believe.
Which one is the fastest and compresses the most?
The general rule for compression is that fast and high compres
Eitan Adler wrote:
> On 17 January 2013 07:52, Fabian Keil wrote:
> > Eitan Adler wrote:
> > I don't think there are any laptops with "large amounts of RAM"
> > as far as ZFS is concerned.
>
> Haha okay: 8GB of RAM.
>
> >> It is taking me 45 minutes to make 5 commits to git. Something is
> >
Hello.
2013/01/17 21:32:08 -0700 Warren Block => To Xyne :
WB> On Fri, 18 Jan 2013, Xyne wrote:
WB>
WB> > I'm the author of svn-export. I haven't really touched the code since I
wrote
WB> > it in 2009 and back then I tended to write most things in noobish Perl.
I shouldn't name your 2009 Perl
Hi,
I have a PCI Express card with VIA VL800 chipset which seems to work OK
with a Seagate drive, so I presume the interface is working.
If I boot with a SanDisk ImageMate S11202 plugged into the USB 3.0 card,
the display shows messages about the SanDisk device, appears to properly
identify it, a
37 matches
Mail list logo
