Negro League Baller Recalls the Era, You Gotta Have Balls, Entrepreneurs, Recipes, Blogs...
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN
HTMLHEADTITLEThe Urban Shopper | May 2013/TITLE
META content=text/html; charset=iso-8859-1 http-equiv=Content-Type
STYLE type=text/css
!--
style1 {
font-size: 10px;
color: #66;
}
a:link {
text-decoration: none;
}
a:visited {
text-decoration: none;
}
a:hover {
text-decoration: underline;
}
a:active {
text-decoration: none;
}
--
/STYLE
META name=keywords
content=african-american woman, african american, recipes, negro league
baseball, jackie robinson, derek jeter, magic johnson, tasers, cremation,
overdosing help, blackberry z10, urban blogs, fashion, beauty
META name=description
content=May 2013 issue of TheUrbanShopper.com features watercolor artist
P. Smallwood, negro league baseball player, recipes, blackberry z10 review,
help for overdosing, tasers for women
META name=GENERATOR content=MSHTML 9.00.8112.16476/HEAD
BODY leftMargin=0 topMargin=0 bgColor=#ff marginheight=0
marginwidth=0!-- ImageReady Slices (static.jpg) --
TABLE style=MARGIN: 0px auto id=Table_01 border=0 cellSpacing=0
cellPadding=0
width=750 align=center height=1101
TBODY
TR
TD width=256IMG alt=
src=http://www.theurbanshopper.com/newsletter/2013/May/static_01.png;
width=249 height=295/TD
TD rowSpan=3 colSpan=4IMG alt=Negro League Player Recalls Era
src=http://www.theurbanshopper.com/newsletter/2013/May/static_4.png;
width=500 height=504/TD
TD width=4IMG alt=
src=http://www.theurbanshopper.com/newsletter/2013/May/spacer.gif;
width=1 height=295/TD/TR
TR
TDIMG alt=
src=http://www.theurbanshopper.com/newsletter/2013/May/static_03.png;
width=249 height=197/TD
TDIMG alt=
src=http://www.theurbanshopper.com/newsletter/2013/May/spacer.gif;
width=1 height=197/TD/TR
TR
TD rowSpan=3IMG alt=
src=http://www.theurbanshopper.com/newsletter/2013/May/static_04.png;
width=249 height=200/TD
TDIMG alt=
src=http://www.theurbanshopper.com/newsletter/2013/May/spacer.gif;
width=1 height=12/TD/TR
TR
TD colSpan=4IMG alt=
src=http://www.theurbanshopper.com/newsletter/2013/May/static_05.png;
width=500 height=65/TD
TDIMG alt=
src=http://www.theurbanshopper.com/newsletter/2013/May/spacer.gif;
width=1 height=65/TD/TR
TR
TD rowSpan=2 colSpan=4IMG alt=
src=http://www.theurbanshopper.com/newsletter/2013/May/static_06.png;
width=500 height=156/TD
TDIMG alt=
src=http://www.theurbanshopper.com/newsletter/2013/May/spacer.gif;
width=1 height=123/TD/TR
TR
TD
style=WIDTH: 249px; BACKGROUND:
url(http://www.theurbanshopper.com/newsletter/2013/May/bg_static_07.png)
no-repeat; HEIGHT: 210px
rowSpan=2
TABLE border=0 cellSpacing=0 cellPadding=0 height=200
TBODY
TR
TDIMG style=MARGIN-LEFT: 10px alt=
src=http://www.theurbanshopper.com/newsletter/2013/May/logo.png;
/TD
TD style=TEXT-ALIGN: center; FONT-FAMILY: Stencil
P
style=PADDING-BOTTOM: 0px; TEXT-TRANSFORM: uppercase; MARGIN:
5px 0px 0px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; COLOR: #3dae1e;
FONT-SIZE: 16px; PADDING-TOP: 0pxkwanzaa
kitchen/P
P
style=PADDING-BOTTOM: 0px; MARGIN: 0px; PADDING-LEFT: 0px;
PADDING-RIGHT: 0px; COLOR: #111010; FONT-SIZE: 14px; PADDING-TOP: 0pxCOOKING
CONTEST/PIMG alt=
src=http://www.theurbanshopper.com/newsletter/2013/May/get_ready_07.png;
/TD/TR
TR
TD colSpan=2
TABLE border=0 cellSpacing=0 cellPadding=0
TBODY
TR
TDIMG style=MARGIN-LEFT: 5px alt=
src=http://www.theurbanshopper.com/newsletter/2013/May/img_static_07.png;
/TD
TD style=FONT-FAMILY: Verdana
P
style=PADDING-BOTTOM: 0px; MARGIN: 0px 0px 0px 5px;
PADDING-LEFT: 0px; PADDING-RIGHT: 0px; COLOR: #666; FONT-SIZE: 7px; PADDING-TOP:
0pxWe're
calling for original recipes that celebrate the spirit of
Kwanzaa/P
P
style=PADDING-BOTTOM: 0px; LINE-HEIGHT: 11px; MARGIN:
7px 0px 7px 5px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; COLOR: #303d1e;
FONT-SIZE: 7px; PADDING-TOP: 0px3
Category WinnersBRBecome a Co-PublisherBRShare in
Book
Sale/P
P
style=PADDING-BOTTOM: 0px; MARGIN: 0px 0px 10px 5px;
PADDING-LEFT: 0px; PADDING-RIGHT: 0px; COLOR: #f60a31; FONT-SIZE: 8px;
PADDING-TOP: 0pxONLINE
SUBMISSIONS ONLY/P
P
style=TEXT-ALIGN: center; PADDING-BOTTOM: 0px; MARGIN:
0px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; FONT-FAMILY: Niagara Solid; COLOR:
#454040; FONT-SIZE: 8px; PADDING-TOP: 0pxA
href=http://www.theurbanshopper.com/kwanzaa;
target=_blankFOR MORE INFO/ABRand
ls(1), rm(1) - No such file or directory even though they are there.
Hi List, There is a rather curious problem that I have, which I haven't encountered before. I make regular backups of my packages and put them onto an external usb drive, which is mounted read/write via sysutils/fusefs-ntfs. Now these backups don't exist no more and at the same time they are there. That is to say, upon issuing ls and/or rm on the command line I get rather strange results. Here are some of my outputs: mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % ls [a long list that has been cut out] zip-3.0.tbz mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % ls zip-3.0.tbz ls: zip-3.0.tbz: No such file or directory Some have files that (don't) exist have i-nodes and some haven't: mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % ls -i zip-3.0.tbz ls: zip-3.0.tbz: No such file or directory mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % ls -i linux-f10-tiff-3.8.2.tbz 2469 linux-f10-tiff-3.8.2.tbz Running rm on the folder I get No such file or directory for every single entry: mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % rm * [a long list that has been cut out] rm: linux-f10-tiff-3.8.2.tbz: No such file or directory Yet again some of the files can be test via gzip and some can't: mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % gzip -t linux-f10-tiff-3.8.2.tbz mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % echo $? 0 mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % gzip -t zip-3.0.tbz gzip: can't stat: zip-3.0.tbz: No such file or directory mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % Looks like the this part of the file system is corrupt. I also booted the drive up under Windows and got the same result. The files are there, but can't be read, overwritten or deleted. What does the list say about the above mentioned? Michael ___ 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-update question
I had an 8.2 system that I wanted to take to 8.4. First I tried upgrade to 8.4, getting (in essence) can't do that. So I upgraded 8.2 which worked giving the end-of-life warning. But seemed work. I then did an upgrade to 8.3 with: freebsd-update -r 8.3-RELEASE upgrade The first part, downloading the diffs and inspecting the system seemed ok. The install seemed ok up to the point it wanted to edit files. It wanted to edit freebsd.submit.cf and sendmail.cf neither of which had local changes and then it started wanting to delete all the files in /etc. I aborted the process when it got to rc.conf. The message was something like, deleting file hosts.allow no longer in 8.3. Happily aborting the process left the system unchanged. Aside from, what could I have done wrong? My question is should we be able to trust freebsd-update on expired systems if it says a mirror exists and then sets about doing its thing? Can this happen in the normal process of removing update 'cruft' from the mirrors? _ Douglas Denault http://www.safeport.com d...@safeport.com Voice: 301-217-9220 Fax: 301-217-9277 ___ 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(1), rm(1) - No such file or directory even though they are there.
Reference: From: Michael Bird michael_b...@yahoo.com Reply-to: Michael Bird michael_b...@yahoo.com Date: Sat, 4 May 2013 10:43:37 -0700 (PDT) Michael Bird wrote: Hi List, There is a rather curious problem that I have, which I haven't encountered before. I make regular backups of my packages and put them onto an external usb drive, which is mounted read/write via sysutils/fusefs-ntfs. Now these backups don't exist no more and at the same time they are there. That is to say, upon issuing ls and/or rm on the command line I get rather strange results. Here are some of my outputs: mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % ls [a long list that has been cut out] zip-3.0.tbz mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % ls zip-3.0.tbz ls: zip-3.0.tbz: No such file or directory Some have files that (don't) exist have i-nodes and some haven't: mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % ls -i zip-3.0.tbz ls: zip-3.0.tbz: No such file or directory mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % ls -i linux-f10-tiff-3.8.2.tbz 2469 linux-f10-tiff-3.8.2.tbz Running rm on the folder I get No such file or directory for every single entry: mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % rm * [a long list that has been cut out] rm: linux-f10-tiff-3.8.2.tbz: No such file or directory Yet again some of the files can be test via gzip and some can't: mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % gzip -t linux-f10-tiff-3.8.2.tbz mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % echo $? 0 mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % gzip -t zip-3.0.tbz gzip: can't stat: zip-3.0.tbz: No such file or directory mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % Looks like the this part of the file system is corrupt. I also booted the drive up under Windows and got the same result. The files are there, but can't be read, overwritten or deleted. What does the list say about the above mentioned? A better list to ask on: freebsd...@freebsd.org I dont know if NTFS even has I nodes, or what one might expect ls -i to sensibly return for that. Obviously your FS is broken if both FreeBSD MS are complaining, so fix it ! Either let MS fix it, or fuse-ntfs if there's a checker (cant remember) Or failing that remove files, remake the FS. I've seen other problems with both methods of accessing NTFS, only reason I use NTFS is when I Have to. Making backups I'd never call a have to use NTFS reason, so I never would for that, I'd use UFS/FFS FS ! Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with . Send plain text. No quoted-printable, HTML, base64, multipart/alternative. ___ 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(1), rm(1) - No such file or directory even though they are there.
On Sat, 4 May 2013 10:43:37 -0700 (PDT), Michael Bird wrote: Hi List, There is a rather curious problem that I have, which I haven't encountered before. I make regular backups of my packages and put them onto an external usb drive, which is mounted read/write via sysutils/fusefs-ntfs. Just to make sure I do understand what you're doing: You are saving files from a FreeBSD UFS file system to a NTFS file system? That's not a good thing(TM)(R)(C)! Explanation: THe UFS file system and this NTFS differ in how file names may be constructed (valid characters) and what file attributes are supported. The best idea to backup (!) files from FreeBSD to a different disk is to format it with UFS. If you _need_ to use NTFS, make a containter that will preserve file attributes. You can easily do this with dump (and later on use restore), but also with tar (should be sufficient). The problem you're describing sounds familiar. It has been discussed on this list some time ago. Maybe check the archives to read that discussion thread. Now these backups don't exist no more and at the same time they are there. Sorry, those don't qualify as backups (in what this term means). They can be considered an imcomplete or damaged copy (even if it's just a question of are there, but cannot be accessed). That is to say, upon issuing ls and/or rm on the command line I get rather strange results. Here are some of my outputs: mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % ls [a long list that has been cut out] zip-3.0.tbz mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % ls zip-3.0.tbz ls: zip-3.0.tbz: No such file or directory You can use fstat for that file to obtain more information: $ fstat /mnt/Programs/FreeBSD/91binaries/packages/zip-3.0.tbz Some have files that (don't) exist have i-nodes and some haven't: mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % ls -i zip-3.0.tbz ls: zip-3.0.tbz: No such file or directory mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % ls -i linux-f10-tiff-3.8.2.tbz 2469 linux-f10-tiff-3.8.2.tbz I assume this is because NTFS does not have a compatible understanding of inodes... Running rm on the folder I get No such file or directory for every single entry: mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % rm * [a long list that has been cut out] rm: linux-f10-tiff-3.8.2.tbz: No such file or directory This is correct when you consider that the required inode structures for the file system access haven't been properly constructed. Yet again some of the files can be test via gzip and some can't: mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % gzip -t linux-f10-tiff-3.8.2.tbz mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % echo $? 0 mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % gzip -t zip-3.0.tbz gzip: can't stat: zip-3.0.tbz: No such file or directory mike@machine1:/mnt/Programs/FreeBSD/91binaries/packages % So the backup (in this case: quotation marks deserved, sorry) is highly inconsistent. But gzip provides an important information: gzip: can't stat: zip-3.0.tbz: No such file or directory Cannot stat. The file status cannot be determined. This means the file system cannot be used as intended. Looks like the this part of the file system is corrupt. I also booted the drive up under Windows and got the same result. The files are there, but can't be read, overwritten or deleted. The whole NTFS is corrupt. You should not use this for backups, or at least use an encapsulation as suggested. This NTFS is known to be easily affected by errors, and it does not provide the required compatibility to store FreeBSD backups. What does the list say about the above mentioned? Do not use NTFS, especially not for backups of FreeBSD. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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
