Urgent notice for you, reply now
Hi, We've set up a web office for TAKUGOLD and we want you to join. Here's a personal message from Henry Taku: " Urgent notice Please a compensation payment of $850,000.00 USD has been awarded to this email address, if you are the owner of the email address contact Mr Victor sunday Email: spstvic...@yahoo.com.ph TelNo:+22993010868 with your full name telephone No. address, age and profetion to send your payment to you immediately. Mr henry Taku Director board of WBC Payment " A web office is like a private website -- only people who join can see what's there. We can use the site to share files, pictures, and links, coordinate events, and keep everyone up-to-date on important group announcements. You don't need anything special to connect to the site; just a web browser and an Internet connection. But you do need to sign up to become a member. Here's how to join... 1. Go to http://takugold.webexone.com/register_member.asp 2. Fill out the information on the new member form using the Registration Code: dGFrdWdv 3. That's it! Just make sure that when you enter the Registration Code, you type it just like it's shown above because it is case-sensitive. Also, be sure to keep the Registration Code private because anyone who knows it can join the web office. Enjoy your web office! ___ http://Webexone.com Get everyone on the same page. SM ___ 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: oops, now: bsd question: how to record a tv stream?
On 03/14/12 13:09, Polytropon wrote:
On Tue, 13 Mar 2012 19:19:46 -0700, Gary Kline wrote:
i have heard about the "848" or whatever cards for years.
should i have my sister's technician add one? i understood
everything but your last paragraph. please do send me the
linksoffline i f you think it wise to spare the
bandwidth.
Just to make a note: This is the card I'm using. The model
name is "Haupauge WinTV" and the tuner chip is Brooktree 878.
It is well supported by FreeBSD (and has been for many years).
A "problem" may be that it is a PCI card.
The programs mplayer and mencoder can be used to address the
tuner and video-in functions of that card, as well as displaying
and storing the received content. You need a HF line to the
card (or an antenna maybe), except you provide the video feed
from a satelite receiver via video-in. In that case, you also
need to provide the audio signal from the receiver to your
sound card's line-in. With mencoder, both sources can be
"combined" and the result can be stored as a video file in
any format and container you want.
This is the card:
bktr0@pci0:0:9:0: class=0x04 card=0x13eb0070
chip=0x036e109e rev=0x11 hdr=0x00
vendor = 'Conexant (Was: Brooktree Corp)'
device = 'Bt878/Fusion 878A Mediastream Controller'
class = multimedia
subclass = video
The card provides HF-in both for TV and radio, video-in,
audio-out and... not sure what it is. :-)
You need the kernel modules loaded per
bktr_load="YES"
in /boot/loader.conf, and the card will work out of the box.
No need to manually and interactively install a "driver". :-)
The player command is something like
% mplayer tv://1 -vo x11 -ao sdl -tv driver=bsdbt848:device=/dev/bktr0
and similarly mencoder can be used (-ovc and -oac need to be
adjusted accordingly) to encode to a file.
I'm not sure how to handle TV ("antenna") input as I've always
been using a raw video feed (from VTR or camera). However, there's
documentation that may help:
http://www.mplayerhq.hu/DOCS/HTML/en/tv-input.html
It also contains an example to "record to file", which will
implement the "software video tape recoder" functionality.
Brooktrees would be nice - if you could find them. Given the move to DVB
is nearly over, there aren't many analog cards available - or need for them.
The new cards use incompatible chipsets (learnt the hard way), including
analog and especially DVB; you have to use the cx88 port to use them. Or
if you come across a different chipset ensure the card is USB based and
use webcamd.
Following all that, FBSD works beautifully as a HTPC.
___
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: oops, now: bsd question: how to record a tv stream?
On Tue, 13 Mar 2012 19:19:46 -0700, Gary Kline wrote:
> i have heard about the "848" or whatever cards for years.
> should i have my sister's technician add one? i understood
> everything but your last paragraph. please do send me the
> linksoffline i f you think it wise to spare the
> bandwidth.
Just to make a note: This is the card I'm using. The model
name is "Haupauge WinTV" and the tuner chip is Brooktree 878.
It is well supported by FreeBSD (and has been for many years).
A "problem" may be that it is a PCI card.
The programs mplayer and mencoder can be used to address the
tuner and video-in functions of that card, as well as displaying
and storing the received content. You need a HF line to the
card (or an antenna maybe), except you provide the video feed
from a satelite receiver via video-in. In that case, you also
need to provide the audio signal from the receiver to your
sound card's line-in. With mencoder, both sources can be
"combined" and the result can be stored as a video file in
any format and container you want.
This is the card:
bktr0@pci0:0:9:0: class=0x04 card=0x13eb0070
chip=0x036e109e rev=0x11 hdr=0x00
vendor = 'Conexant (Was: Brooktree Corp)'
device = 'Bt878/Fusion 878A Mediastream Controller'
class = multimedia
subclass = video
The card provides HF-in both for TV and radio, video-in,
audio-out and... not sure what it is. :-)
You need the kernel modules loaded per
bktr_load="YES"
in /boot/loader.conf, and the card will work out of the box.
No need to manually and interactively install a "driver". :-)
The player command is something like
% mplayer tv://1 -vo x11 -ao sdl -tv driver=bsdbt848:device=/dev/bktr0
and similarly mencoder can be used (-ovc and -oac need to be
adjusted accordingly) to encode to a file.
I'm not sure how to handle TV ("antenna") input as I've always
been using a raw video feed (from VTR or camera). However, there's
documentation that may help:
http://www.mplayerhq.hu/DOCS/HTML/en/tv-input.html
It also contains an example to "record to file", which will
implement the "software video tape recoder" functionality.
--
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"
Re: oops, now: bsd question: how to record a tv stream?
On Tue, 13 Mar 2012 13:02:24 -0700, Gary Kline wrote: > if it means buying a card, then, nope. i assumed that the > bits were streaming thu my cable to firefox and that thedre > was some program that could collecte these data and stash > them in, say , /tmp. i'm using linux as a desktop, and FBSD > as my server. There are download helper plugins available for Firefox that allow you to "capture" streaming content to a file. > maybed i'll find where pbs has these films stashed ... or > maybe they were only for "pledge week" Regular file downloads are something you'll hardly find on the "modern" web. But that doesn't mean you cannot turn streams into files. After all, the data _is_ trans- ferred to your computer. It's just a question to use the proper program. :-) -- 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"
Re: oops, now: bsd question: how to record a tv stream?
On Tue, Mar 13, 2012 at 04:14:52PM -0500, Josh Tolbert wrote: > Date: Tue, 13 Mar 2012 16:14:52 -0500 > From: Josh Tolbert > Subject: Re: oops, now: bsd question: how to record a tv stream? > To: freebsd-questions@freebsd.org > > On 3/13/12 4:06 PM, Gary Kline wrote: > >On Tue, Mar 13, 2012 at 12:39:38PM +1000, Da Rock wrote: > >so that's it. i messed around with mythtv last fall on my ubuntu > >distro. couldn't get anywhere and finally realized that =you need > >some kind of HARDWARE=. > > I have an HDHomeRun...The original "classic" two-tuner model, from > http://www.silicondust.com. It's a stand-alone DTV streamer. I use > it with an antenna; apparently you can get versions that work with > antennas or cablecard/cable TV as well. Works great. I use it with > Windows Media Center for scheduling recordings, but they work great > with MythTV, VLC and others for recording. Using VLC, I've recorded > some videos of a local band on a morning show that have ended up on > YouTube...I can send links if you want to see how it looks, although > that station only broadcasts in 480i. > > For what it's worth, I've successfully used three BT848/878/878+ > cards---all of which were PixelView or STB cards---in the same > machine running FreeBSD with the bktr driver and Motion to handle > surveillance-camera duties. mplayer/mencoder could only use bktr0 > cause they hard-code bktr0 in the source and seemed thoroughly > uninterested in fixing this oversight, even though the change would > be fairly minor. > > Hope that helps someone. hey, josh, you just gave me an idea. my sister is giving me a used computer that is in good shape. i have heard about the "848" or whatever cards for years. should i have my sister's technician add one? i understood everything but your last paragraph. please do send me the linksoffline i f you think it wise to spare the bandwidth. Q: i have [i think] hi-def in the used computer, so want a hi-def card yours in geezer-geeekdom, gary PS: i was a kernel hacker, a porter, and an OS TEster. pix, tv, [movies], audio are strictly over my head. > > Cheers, > > Josh > > -- > Josh Tolbert > h...@puresimplicity.net || http://www.puresimplicity.net/~hemi/ > > Security is mostly a superstition. It does not exist in nature, nor > do the children of men as a whole experience it. Avoiding danger > is no safer in the long run than outright exposure. Life is either > a daring adventure, or nothing. > -- Helen Keller > > ___ > 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" -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Voice By Computer (for Universal Access): http:/www.thought.org/vbc The 8.57a release of Jottings: http://jottings.thought.org Twenty-five years of service to the Unix community. ___ 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: Making Music / Video folders on FreeBSD visible on HD TV
On 03/14/12 03:29, Carmel wrote: Presently, I have three HD TVs, two Samsung and one Sony. On these TVs there is a menu where I can access remote devices to access music or videos. By marking the folders "shared" in Windows, these folders are available on these TVs. I have found no way to accomplish the same thing with my FreeBSD-8.2 PC. Simply using Samba and creating a shared music or video directory does not work. I contacted Samsung and they told me that they do not support architecture other than Microsoft& MAC and that I should contact whoever wrote the OS I am working with for assistance. I didn't bother with Sony since I assume I would have only gotten the same response. Ironic, considering Sony use FreeBSD for PS... might have had more success than Samsung :) There's a DLNA server in ports you could try. If anyone understands what I am talking about and has a feasible solution I would love to hear. I had considered either mapping a drive in Windows that pointed to the FreeBSD share or creating a link to it. I would prefer not to have to go that route however, even if it did work. I probably should add that this entire system is wireless with the exception of the FreeBSD machine that is hard wired to the wireless router. ___ 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: Making Music / Video folders on FreeBSD visible on HD TV
Been here ... cursed that, your TV is not seeing the folders directly at least not in the traditional sense, it is likely that it is using WMP as a DLNA server which will transcode the media in to a format that your TV can play by streaming. You solution is in ports /net/serviio You can find more information here http://www.serviio.org Do not worry that it mentions Win Mac and Linux, it does work great on FreeBSD . Regards Graeme -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Carmel Sent: 13 March 2012 17:30 To: FreeBSD Subject: Making Music / Video folders on FreeBSD visible on HD TV Presently, I have three HD TVs, two Samsung and one Sony. On these TVs there is a menu where I can access remote devices to access music or videos. By marking the folders "shared" in Windows, these folders are available on these TVs. I have found no way to accomplish the same thing with my FreeBSD-8.2 PC. Simply using Samba and creating a shared music or video directory does not work. I contacted Samsung and they told me that they do not support architecture other than Microsoft & MAC and that I should contact whoever wrote the OS I am working with for assistance. I didn't bother with Sony since I assume I would have only gotten the same response. If anyone understands what I am talking about and has a feasible solution I would love to hear. I had considered either mapping a drive in Windows that pointed to the FreeBSD share or creating a link to it. I would prefer not to have to go that route however, even if it did work. I probably should add that this entire system is wireless with the exception of the FreeBSD machine that is hard wired to the wireless router. -- Carmel carmel...@hotmail.com ___ 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"
Re: oops, now: bsd question: how to record a tv stream?
On 3/13/12 4:06 PM, Gary Kline wrote: On Tue, Mar 13, 2012 at 12:39:38PM +1000, Da Rock wrote: so that's it. i messed around with mythtv last fall on my ubuntu distro. couldn't get anywhere and finally realized that =you need some kind of HARDWARE=. I have an HDHomeRun...The original "classic" two-tuner model, from http://www.silicondust.com. It's a stand-alone DTV streamer. I use it with an antenna; apparently you can get versions that work with antennas or cablecard/cable TV as well. Works great. I use it with Windows Media Center for scheduling recordings, but they work great with MythTV, VLC and others for recording. Using VLC, I've recorded some videos of a local band on a morning show that have ended up on YouTube...I can send links if you want to see how it looks, although that station only broadcasts in 480i. For what it's worth, I've successfully used three BT848/878/878+ cards---all of which were PixelView or STB cards---in the same machine running FreeBSD with the bktr driver and Motion to handle surveillance-camera duties. mplayer/mencoder could only use bktr0 cause they hard-code bktr0 in the source and seemed thoroughly uninterested in fixing this oversight, even though the change would be fairly minor. Hope that helps someone. Cheers, Josh -- Josh Tolbert h...@puresimplicity.net || http://www.puresimplicity.net/~hemi/ Security is mostly a superstition. It does not exist in nature, nor do the children of men as a whole experience it. Avoiding danger is no safer in the long run than outright exposure. Life is either a daring adventure, or nothing. -- Helen Keller ___ 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"
Apache module mod_fastcgi
according to: http://www.fastcgi.com/mod_fastcgi/docs/mod_fastcgi.html#FastCgiExternalServer --- Note: Using FastCgiServer within a VirtualHost does not necessarily limited access to that host. If filename is accessible via other virtual hosts, they too can leverage the same definition. --- how would I share this between multiple virtualhosts? I can get it to work in one default virtualhost but in none of my virtualhosts since it's already defined and being shared across all virtualhost? -- http://alexus.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"
Re: oops, now: bsd question: how to record a tv stream?
On Tue, Mar 13, 2012 at 12:39:38PM +1000, Da Rock wrote:
> Date: Tue, 13 Mar 2012 12:39:38 +1000
> From: Da Rock
> Subject: Re: oops, now: bsd question: how to record a tv stream?
> To: freebsd-questions@freebsd.org
[ ...]
>
> >>>Additionally, there may be an option to download some kind of media
> >>>streams. There are tools for that available.
> >>There is cx88 in the ports which will cover a lot of pci devices, and
> >> webcamd covers just about all the rest. Then use mplayer or another
> >>tool to record the stream.
> >>
> >>And if you're real tricky you can set it to record at a specific time
> >> and shut off at another specified time... :) I wrote a script for
> >>this; a bit hackish, but it gets the job done. I have to clean it up
> >>someday when I have the spare time.
> >
> >No one suggesting MythTV? I haven't used a tuner card but I thought
> >MythTV was the one to use.
> Pah! Too much bloat - especially for this use.
>
> A lot of setup and configuration is required, and for a one off why bother?
so that's it. i messed around with mythtv last fall on my
ubuntu distro. couldn't get anywhere and finally realized
that =you need some kind of HARDWARE=. well, bleep that. i
de-installed and got back to .
sinced early december i've been working on an accessibility
app for the speech impaired. it won't work on the berkeley
distros natively. it should given our linux stuff. i'll
tell you: i haven't have this much of a challenge since i
was studying data structures. Danm, gtk is hard. but
super fun. my application is as lean as i can make it,
Especially since it is aimed an people who have never used
computers before. i'm copying as much of gespeaker's
layout as i can because that is very lean and clean.
---this is a long-winded way of saying to da rock that i
hope you clean up your script[s] and publish the code in
/usr/ports.
{a final rant about copyright:: i woulnd never touch any
commercial station because they sneak in those bloody
commerc*als on you. before you know it, you've watched
a minute of babes trying to sell you your Zippy-Do sports
van. i dont have the energy to get mad. i just dont watch
anything but pbs or npr.}
> ___
> 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"
--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
Voice By Computer (for Universal Access): http:/www.thought.org/vbc
The 8.57a release of Jottings: http://jottings.thought.org
Twenty-five years of service to the Unix community.
___
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: oops, now: bsd question: how to record a tv stream?
On Sun, Mar 11, 2012 at 03:52:36PM -0500, Joshua Isom wrote: > Date: Sun, 11 Mar 2012 15:52:36 -0500 > From: Joshua Isom > Subject: Re: oops, now: bsd question: how to record a tv stream? > To: freebsd-questions@freebsd.org > > On 3/11/2012 3:28 PM, Gary Kline wrote: > >guys, > > > >i made the mistake that conrad did when replying. i could make e > >excuse liked only getting five hours sleep, etc, bujt i wont. > > > >here us a FBSD qauestion how can i capture any tv stream---or > >radio stream for later replay? or is that illegal, too? > > > >gray > > > > > > > > For capturing, I believe linux is your best bet. I had tried using > the bktr driver, but I couldn't get it to work properly with the > card I had. It could work somewhat from what I remember. The card > was my brother's and he used it under linux, but he upgraded to a > better one. > > Legality should be the same as a VCR/DVR, personal use only and > don't redistribute. if it means buying a card, then, nope. i assumed that the bits were streaming thu my cable to firefox and that thedre was some program that could collecte these data and stash them in, say , /tmp. i'm using linux as a desktop, and FBSD as my server. maybed i'll find where pbs has these films stashed ... or maybe they were only for "pledge week" gary ps:: fwiw, that capmbell stuff was about half of the original. i've got all 6 hours of audio, tho. > ___ > 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" -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Voice By Computer (for Universal Access): http:/www.thought.org/vbc The 8.57a release of Jottings: http://jottings.thought.org Twenty-five years of service to the Unix community. ___ 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: Making Music / Video folders on FreeBSD visible on HD TV
On Tue, 13 Mar 2012 13:59:45 -0500 Adam Vande More articulated: > Are you sure these devices aren't trying to connect to a DLNA > server? Such need can be met by net/mediatomb or other port. A couple of people have replied to this thread. The Samba shares are configured correctly and are visible on my Windows based PCs. I have no idea if the TVs are using DLNA. I never had to configure anything, other than sharing the folders, on my Microsoft PCs, so am I to assume that DLNA is always available on that OS? Anyway, I will try your suggestion. -- Carmel carmel...@hotmail.com ___ 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: Making Music / Video folders on FreeBSD visible on HD TV
> -Original Message- > From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- > questi...@freebsd.org] On Behalf Of Stas Verberkt > Sent: Tuesday, March 13, 2012 2:14 PM > To: freebsd-questions@freebsd.org > Subject: Re: Making Music / Video folders on FreeBSD visible on HD TV > > Carmel schreef op 13-03-2012 18:29: > > Presently, I have three HD TVs, two Samsung and one Sony. On these TVs > > there is a menu where I can access remote devices to access music or > > videos. By marking the folders "shared" in Windows, these folders are > > available on these TVs. I have found no way to accomplish the same > > thing with my FreeBSD-8.2 PC. Simply using Samba and creating a shared > > music or video directory does not work. I contacted Samsung and they > > told me that they do not support architecture other than Microsoft & > > MAC and that I should contact whoever wrote the OS I am working with > > for assistance. I didn't bother with Sony since I assume I would have > > only gotten the same response. > > > > If anyone understands what I am talking about and has a feasible > > solution I would love to hear. I had considered either mapping a drive > > in Windows that pointed to the FreeBSD share or creating a link to it. > > I would prefer not to have to go that route however, even if it did > > work. > > > > I probably should add that this entire system is wireless with the > > exception of the FreeBSD machine that is hard wired to the wireless > > router. > > My guess would still be Samba, as this is an implementation of the shared > folders of Windows. Maybe your configuration was not perfect? > ___ > 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" Make sure that the SAMBA shares are not hidden. Test from a windows PC to see that they are listed properly. ___ 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: Making Music / Video folders on FreeBSD visible on HD TV
On Tue, Mar 13, 2012 at 12:29 PM, Carmel wrote: > Presently, I have three HD TVs, two Samsung and one Sony. On these TVs > there is a menu where I can access remote devices to access music or > videos. By marking the folders "shared" in Windows, these folders are > available on these TVs. I have found no way to accomplish the same > thing with my FreeBSD-8.2 PC. > Are you sure these devices aren't trying to connect to a DLNA server? Such need can be met by net/mediatomb or other port. -- Adam Vande More ___ 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: Editor With NO Shell Access?
Tim Daneliuk wrote: > ... we're talking about almost 1000 systems > here. That's a whole bunch of configuration... Had you considered using something along the lines of sysutils/puppet? ___ 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: Making Music / Video folders on FreeBSD visible on HD TV
Carmel schreef op 13-03-2012 18:29: Presently, I have three HD TVs, two Samsung and one Sony. On these TVs there is a menu where I can access remote devices to access music or videos. By marking the folders "shared" in Windows, these folders are available on these TVs. I have found no way to accomplish the same thing with my FreeBSD-8.2 PC. Simply using Samba and creating a shared music or video directory does not work. I contacted Samsung and they told me that they do not support architecture other than Microsoft & MAC and that I should contact whoever wrote the OS I am working with for assistance. I didn't bother with Sony since I assume I would have only gotten the same response. If anyone understands what I am talking about and has a feasible solution I would love to hear. I had considered either mapping a drive in Windows that pointed to the FreeBSD share or creating a link to it. I would prefer not to have to go that route however, even if it did work. I probably should add that this entire system is wireless with the exception of the FreeBSD machine that is hard wired to the wireless router. My guess would still be Samba, as this is an implementation of the shared folders of Windows. Maybe your configuration was not perfect? ___ 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: Intel Pro/Wireless 2200BG (iwi) firmware error / device timeout
On Tue, Mar 13, 2012 at 4:27 PM, Joseph Mingrone wrote:
> I see there are still some open PRs for this problem, but they are a
> couple of years old. Does anyone know of any workarounds?
>
> I don't recall having problems in 7.x, but in 8.x I see the firmware
> errors every few hours. If I try to do a # /etc/rc.d netif restart the
> system reboots.
I don't know if it is related, but in 9.0-RELEASE, I can't load the
firmware at all (kern/165595)
Cheers
>
> # pciconf -lv
> ...
> iwi0@pci0:2:2:0: class=0x028000 card=0x27018086 chip=0x42208086
> rev=0x05 hdr=0x00
> vendor = 'Intel Corporation'
> device = 'driverIntel PRO/Wireless 2200BG (MPCI3B)'
> class = network
>
> # cat /boot/loader.conf
> ...
> legal.intel_iwi.license_ack=1
> if_iwi_load="YES"
>
> # cat /etc/rc.conf | grep wlan
> wlans_iwi0="wlan0"
> ifconfig_wlan0="WPA DHCP"
>
> # cat /etc/wap_supplicant.conf
> network={
> ssid="myssid"
> psk="mypsk"
> }
> ___
> 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"
Online Seller vs E-Commerce Seller
You're receiving this newsletter because you subscribed from our website. Can't see the message? View it in browser. happy customer Tips of the day: The 5 Habits of Highly Effective for E-Commerce Think Like A Consumer The online businesses that make their goods and services easy to find reap rewards in two ways: People purchase more and they experience greater overall satisfaction with the Website. If you sell paintings and frames, show the frames that best complement the paintings. Keep It Simple Successful ecommerce sites simplify the checkout process and display clear pricing and shipping information. They also post clear return policies and access to customer service. A Picture Is Worth A Thousand Words Use photos of your products and go easy on the text. Online usability studies suggest that people do not read; they scan. Its 25% hard to read on the web, so keep these guidelines in mind for optimum readability. Market Your Website Once It's Live You need to make an effort to market and promote your website to new customer. Tap on Lelong.my Marketplace with ready high traffic. Take advantage of this capability to reach a whole new set of customers. Make Payment Processing Easy Online shoppers need a way to give you money online. That's easy these days. You can accept credit card payments with either NetPay or PayPal. Forget about cash on delivery and meeting up buyer. This will make you exhausted. Read what our happy customers are saying: "Lelong class definitely is a Must attend class for anyone who want to do their business seriously in lelong, no matter you are newbie or season online marketer. Adrian, Nicole, all the lelong lecturers and staffs is very experience and helpful to hold you hand and guide you step by step. I had joined my 101 and 102 lelong class, and I am looking forward to joining more lelong class if there are any. Join the class now and I guarantee you won't regret it! Good works Lelong Team!" Terrence Koh - Part Time Seller "Saya pernah terfikir bagaimana cara untuk menjual online dimana saya hanya ada pengalaman menjual secara konvesional sahaja, namun setelah saya hadir kelas dari Lelong tenaga pengajar mereka amatlah berpengalaman dan membantu saya untuk mula menjual secara online. Mereka juga mendidik saya tentang cara-cara untuk menjual di Lelong.my dan juga tips efektif diberikan dan ianya penuh dengan maklumat yang berguna. Terima kasih Lelong!" Nor Rabiah binti Nasir - Part Time Seller More Testimonials We would love to hear from you! Don't hesitate to contact us for any enquiries! Powered by Lelong.my You are receiving this e-mail because you are in our mailing list. If you do not wish to receive further newsletters, you may unsubscribe by clicking Here ___ 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"
Making Music / Video folders on FreeBSD visible on HD TV
Presently, I have three HD TVs, two Samsung and one Sony. On these TVs there is a menu where I can access remote devices to access music or videos. By marking the folders "shared" in Windows, these folders are available on these TVs. I have found no way to accomplish the same thing with my FreeBSD-8.2 PC. Simply using Samba and creating a shared music or video directory does not work. I contacted Samsung and they told me that they do not support architecture other than Microsoft & MAC and that I should contact whoever wrote the OS I am working with for assistance. I didn't bother with Sony since I assume I would have only gotten the same response. If anyone understands what I am talking about and has a feasible solution I would love to hear. I had considered either mapping a drive in Windows that pointed to the FreeBSD share or creating a link to it. I would prefer not to have to go that route however, even if it did work. I probably should add that this entire system is wireless with the exception of the FreeBSD machine that is hard wired to the wireless router. -- Carmel carmel...@hotmail.com ___ 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: Editor With NO Shell Access?
On 3/13/2012 10:43 AM, Tim Daneliuk wrote: On 03/13/2012 01:39 AM, Joshua Isom wrote: On 3/12/2012 5:23 PM, Polytropon wrote: On Mon, 12 Mar 2012 15:19:51 -0700, Edward M. wrote: On 03/12/2012 03:10 PM, Polytropon wrote: /etc/shells to work, but a passwd entry like bob:*:1234:1234:Two-loop-Bob:/home/bob:/usr/local/bin/joe I think this would not let the user to login,etc I'm not sure... I assume logging in is handled by /usr/bin/login, and control is then (i. e. after successful login) transferred to the login shell, which is the program specified in the "shell" field (see "man 5 passwd") of /etc/passwd. How is login supposed to know if the program specified in this field is actually a dialog shell? From "man 1 login" I read that many shells have a built-in login command, but /usr/bin/login is the system's default binary for this purpose if the "shell" (quotes deserved if it is an editor as shown in my assumption) has no capability of performing a login. Are they logging in from the console or from ssh? If it's from a console, I'd send them directly into a jail with limited file system access, so that excecutables don't matter. If it's from ssh, I'd do the same thing. Assume they can break out of the editor or that something will happen. Make it minimalist about what they can do. Use the /rescue/vi in an empty jail with the files available. Don't think about changing editors, change the system. That's a really good idea, but we're talking about almost 1000 systems here. That's a whole bunch of configuration... Here's the simplified form. mkdir -p /edit_jail/usr/share/misc mkdir -p /edit_jail/var/tmp cp /usr/share/misc/termcap* /edit_jail/usr/share/misc/ cp /rescue/vi /edit_jail mount_nullfs /allowable_files /edit_jail/files jail -c path=/edit_jail command=/vi Only the last command would need to be done at login. If you want a different editor, you'll have to deal with libraries, etc. Most only need libc and libncurses so it's not that big a deal. ___ 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"
Interrupt storm and Intel DQ67SW
In case anyone else runs into this problem, here it is for the archives. FreeBSD 8.3, AMD64 (Actually, RELENG_8 as of March 2012) I upgraded my home server to an Intel DQ67SW motherboard (hardware version AAG12527-309). I used a bge PCI-E nic in the 1x slot which caused an interrupt storm issue with the usb. Trying an old PCI fxp card showed the same problem. Even with just 2Mb of pppoe traffic crossing the bge or fxp, I would see storm issues. Running top, showed 10% of the system was spending its time servicing interrupts. vmstat -i showed a rate of close to 10k on irq16. I upgraded the BIOS to SWQ6710H.86A.0061.2012.0210.1130 from the Nov 2011 version and all is fine now. Everything about the box 'feels' more responsive and throughput on my wan connection is normal again. # vmstat -i interrupt total rate irq16: bge0 ehci0+ 40439 3 irq20: fwohci0 2 0 irq23: ehci1 22177 2 cpu0: timer 22062162 2000 irq256: em014825 1 irq257: ahci04874088441 cpu3: timer 22054239 1999 cpu1: timer 22054150 1999 cpu2: timer 22054168 1999 Total 93176250 8446 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM) i5-2300 CPU @ 2.80GHz (2793.67-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Features=0xbfebfbff Features2=0x179ae3bf AMD Features=0x28100800 AMD Features2=0x1 TSC: P-state invariant real memory = 17179869184 (16384 MB) avail memory = 16434216960 (15672 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ichwd module loaded cryptosoft0: on motherboard aesni0: on motherboard acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xf000-0xf03f mem 0xfb40-0xfb7f,0xc000-0xcfff irq 16 at device 2.0 on pci0 pci0: at device 22.0 (no driver attached) atapci0: port 0xf130-0xf137,0xf120-0xf123,0xf110-0xf117,0xf100-0xf103,0xf0f0-0xf0ff irq 18 at device 22.2 on pci0 atapci0: [ITHREAD] ata2: at channel 0 on atapci0 ata2: [ITHREAD] ata3: at channel 1 on atapci0 ata3: [ITHREAD] uart2: port 0xf0e0-0xf0e7 mem 0xfbc29000-0xfbc29fff irq 17 at device 22.3 on pci0 uart2: [FILTER] em0: port 0xf080-0xf09f mem 0xfbc0-0xfbc1,0xfbc28000-0xfbc28fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: [FILTER] em0: Ethernet address: 00:22:4d:52:5c:34 ehci0: mem 0xfbc27000-0xfbc273ff irq 16 at device 26.0 on pci0 ehci0: [ITHREAD] usbus0: EHCI version 1.0 usbus0: on ehci0 pci0: at device 27.0 (no driver attached) pcib2: irq 17 at device 28.0 on pci0 pci2: on pcib2 bge0: mem 0xfbb1-0xfbb1 irq 16 at device 0.0 on pci2 bge0: CHIP ID 0x4001; ASIC REV 0x04; CHIP REV 0x40; PCI-E miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: Ethernet address: 00:10:18:14:15:43 bge0: [ITHREAD] pcib3: irq 17 at device 28.4 on pci0 pci3: on pcib3 3ware device driver for 9000 series storage controllers, version: 3.80.06.003 twa0: <3ware 9000 series Storage Controller> port 0xe000-0xe0ff mem 0xd000-0xd1ff,0xfba2-0xfba20fff irq 16 at device 0.0 on pci3 twa0: [ITHREAD] twa0: INFO: (0x15: 0x1300): Controller details:: Model 9650SE-2LP, 2 ports, Firmware FE9X 4.08.00.006, BIOS BE9X 4.08.00.001 pcib4: irq 18 at device 28.6 on pci0 pci4: on pcib4 xhci0: mem 0xfb90-0xfb901fff irq 18 at device 0.0 on pci4 xhci0: [ITHREAD] xhci0: 32 byte context size. usbus1 on xhci0 ehci1: mem 0xfbc26000-0xfbc263ff irq 23 at device 29.0 on pci0 ehci1: [ITHREAD] usbus2: EHCI version 1.0 usbus2: on ehci1 pcib5: at device 30.0 on pci0 pci5: on pcib5 fwohci0: mem 0xfb80-0xfb800fff irq 20 at device 3.0 on pci5 fwohci0: [ITHREAD] fwohci0: OHCI version 1.0 (ROM=0) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:22:4d:ff:ff:52:8f:44 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:22:4d:52:8f:44 fwe0: Ethernet address: 02:22:4d:52:8f:44 fwip0: on firewire0 fwip0: Firewire address: 00:22:4d:ff:ff:52:8f:44 @ 0xfffe, S400, maxrec 2048
Re: Editor With NO Shell Access?
On 03/13/2012 01:39 AM, Joshua Isom wrote: On 3/12/2012 5:23 PM, Polytropon wrote: On Mon, 12 Mar 2012 15:19:51 -0700, Edward M. wrote: On 03/12/2012 03:10 PM, Polytropon wrote: /etc/shells to work, but a passwd entry like bob:*:1234:1234:Two-loop-Bob:/home/bob:/usr/local/bin/joe I think this would not let the user to login,etc I'm not sure... I assume logging in is handled by /usr/bin/login, and control is then (i. e. after successful login) transferred to the login shell, which is the program specified in the "shell" field (see "man 5 passwd") of /etc/passwd. How is login supposed to know if the program specified in this field is actually a dialog shell? From "man 1 login" I read that many shells have a built-in login command, but /usr/bin/login is the system's default binary for this purpose if the "shell" (quotes deserved if it is an editor as shown in my assumption) has no capability of performing a login. Are they logging in from the console or from ssh? If it's from a console, I'd send them directly into a jail with limited file system access, so that excecutables don't matter. If it's from ssh, I'd do the same thing. Assume they can break out of the editor or that something will happen. Make it minimalist about what they can do. Use the /rescue/vi in an empty jail with the files available. Don't think about changing editors, change the system. That's a really good idea, but we're talking about almost 1000 systems here. That's a whole bunch of configuration... -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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"
Intel Pro/Wireless 2200BG (iwi) firmware error / device timeout
I see there are still some open PRs for this problem, but they are a
couple of years old. Does anyone know of any workarounds?
I don't recall having problems in 7.x, but in 8.x I see the firmware
errors every few hours. If I try to do a # /etc/rc.d netif restart the
system reboots.
# pciconf -lv
...
iwi0@pci0:2:2:0:class=0x028000 card=0x27018086 chip=0x42208086
rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = 'driverIntel PRO/Wireless 2200BG (MPCI3B)'
class = network
# cat /boot/loader.conf
...
legal.intel_iwi.license_ack=1
if_iwi_load="YES"
# cat /etc/rc.conf | grep wlan
wlans_iwi0="wlan0"
ifconfig_wlan0="WPA DHCP"
# cat /etc/wap_supplicant.conf
network={
ssid="myssid"
psk="mypsk"
}
___
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: Editor With NO Shell Access?
On Mon, Mar 12, 2012 at 8:19 PM, Tim Daneliuk wrote: > I have a situation where I need to provide people with the ability to edit > files. However, under no circumstances do I want them to be able to exit > to the shell. The client in question has strong (and unyielding) InfoSec > requirements in this regard. If the requirements are THAT hard, I think it would be best to do it the good ole fashioned way: modify the source code of their favorite editor, by patching out ALL calls to system(2), exec*(2), popen() et al. This way, you'll be sure that editor binary won't call out ANY external process whatsoever. A little bit less secure, but based on the same idea, would be to provide replacements for those process-creating functions in a custom library, say, libnofork.so where each of these functions immediately return or signal an error like EPERM instead of ultimately doing the syscall. Then link your client's editor with -lnofork to mask the original libc definitions. It is a little bit less secure than manually removing or commenting out calls to system(), exec*(), popen*() etc, because the editor could at least in theory call dlopen() on the original libc, where the functions are still there, or it could even issue the kernel syscalls directly, without going through libc... although that is very unlikely with the usual editors. It is also less secure, because from within this modified editor, the user could read the contents of libc.so into libnofork.so, and then restart the editor. But you get the basic idea. Alternatively, you may want to look into ways to disable forking() in general for a process. Some old Unices provided a way to selectively disable certain syscalls based on some root-definable administrative per-user or per-application policy, but I don't know whether this is possible with FreeBSD. Perhaps the new Capsicum [1] provides this, or will in the foreseeable future? I have not looked into it yet. [1]: http://www.cl.cam.ac.uk/research/security/capsicum/ > So ... are there editors without this feature? Can I compile something like > joe or vi to inhibit this feature? Yes, see above: provide a replacement library and link against that. Consider static linking for slightly increased security, and make sure the user can't modify the editor binary, can't modify any dynamic libraries it links against, and can't replace that binary with another binary. Security is like an onion. > Tim Daneliuk tun...@tundraware.com > PGP Key: http://www.tundraware.com/PGP/ Regards, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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"
Problem compiling emulators/virtualbox-ose-kmod 4.1.8_2
portmaster -a fails with: cc -O -pipe -march=athlon-mp -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_X86 -Werror -D_KERNEL -DKLD_MODULE -nostdinc -Iinclude -I. -Ir0drv -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c: In function 'rtR0MemObjFreeBSDAllocPhysPages': /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:405: error: invalid type argument of '->' *** Error code 1 Stop in /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv. I ran portsnap immediately before portmaster so my ports are up to date. Any suggestions? -- Mike Clarke ___ 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: oops, now: bsd question: how to record a tv stream?
Bernt Hansson schreef op 13-03-2012 12:12: On 2012-03-11 21:28, Gary Kline wrote: or is that illegal, too? Depends on jurisdiction. Indeed, Dutch and Belgium legislation, for example, permit making copies for personal use, which originates from recording the radio with a tape deck, which is basically what you are trying to do. I think US legislation is more strict and only allows personal copies where one has both the original and the copy, e.g. copying a CD to your (licensed) MP3 player. ___ 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: lost+found dir placement
On Tue, 13 Mar 2012 10:02:16 + (UTC), jb wrote: > Robert Bonomi mail.r-bonomi.com> writes: > > > ... > > The fsck_ffs manpage says that 'lost+found' is _created_ *when*needed*, > > in the root of a filesystem, if not already present. > > > > The presense of /mnt/lost+found is _not_ an error. just a surperfluous > > file that ended up there 'somehow'. > > ... > > This worried me. And still does ... How "clean" is your installation? If you have had mounted some UFS file system in /mnt that has undergone a fsck check where the creation of lost+found had been neccessary... no wait, it would be on that partition then. If this directory entry is present in /mnt which is supposed to be empty by default, e. g. if "mount" doesn't show something actually mounted on /mnt, then I think you should delete the directory entry. Just imagine the "fun" that could happen if you mount something to /mnt... However, do you remember _what_ created lost+found in /mnt? > > *IF* you're going to file a PR, it should be for the filesystem > > initialization process -- which "should" (a) create the lost+found > > directory, (b) create some 'reasonable' number of files in that directory, > > and (c) then delete all those files. This ensures that the directory > > exists and has disk-space allocated for a 'reasonable' number of > > 'recovered' file entries. > > > > That's perhaps why under Linux they have special mklost+found entry ? Nothing new. In fact, I remember that my WEGA (UNIX system III derivate) mentiones a command that would create the lost+found directory, mklf or createlf... as a binary. > > The existing fsck_ffs has a catastrophic failure mode if there is no > > space on the disk for the lost+found directory to grow to acomodate > > the recovered file entries. > > > > I was surprised to find empty lost+found dir in /mnt. > drwx-- 2 root wheel 512 May 5 2011 lost+found > That's why I jumped a bit. It's fully unsurprising to be surprised here. :-) > Few days ago, after clean reboot to single user mode, I tested fsck manually > on SUJ fs and found things that seemed to be questionable (I posted it on > current@ list, if you want to take a look). > > So, it must have happened during that time, because as I said I did not have > any forced fsck run at boot times, and I almost swear I did not have this > lost+found dir in /mnt before. Possible, but in a normal case, lost+found is tied to a partition (and per implication to a mountpoint). The mountpoint, if _not_ in use, should be empty. > I will take a look at source code of fsck* entries and perhaps find a clue. I posted the file name where you can find the handling of the creation of lost+found. Just search for this string and you'll find the corresponding section easily. -- 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"
Re: Jail and questions
Bernt Hansson wrote: Hello list I've setup a 32-bit jail on amd64 freebsd 8.2-stable. It works, sort of, but when i run portsnap extract in the jail it say Building new INDEX files... make_index: fopen(/dev/stdin): No such file or directory #ls /dev lrwxr-xr-x 1 root wheel12 6 Mar 02:56 log -> /var/run/log -rw-r--r-- 1 root wheel76 12 Mar 23:09 null -rw-r--r-- 1 root wheel 0 10 Mar 03:01 stderr -rw-r--r-- 1 root wheel 1360 7 Mar 04:44 stdout Where is stdin? or running #ps ps: /boot/kernel/kernel: No such file or directory Jails don't boot the host so they don't need /boot directory. I would say you have created the jail directory tree incorrectly. Give the qjail port a try for simply jail creation and admin. ___ 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: 9.0 spontaneously reboots
On 13/03/2012 10:28, Volodymyr Kostyrko wrote: > Matthew Seaman wrote: >> On 13/03/2012 08:59, Volodymyr Kostyrko wrote: >>> The only other weird thing about this server is: >>> >>> dev.cpu.0.temperature: 37,0C >>> dev.cpu.1.temperature: 37,0C >>> dev.cpu.2.temperature: 35,0C >>> dev.cpu.3.temperature: 35,0C >>> dev.cpu.4.temperature: 43,0C >>> dev.cpu.5.temperature: 43,0C >>> dev.cpu.6.temperature: 38,0C >>> dev.cpu.7.temperature: 38,0C >>> dev.cpu.8.temperature: 38,0C >>> dev.cpu.9.temperature: 38,0C >>> dev.cpu.10.temperature: 37,0C >>> dev.cpu.11.temperature: 37,0C >>> dev.cpu.12.temperature: 33,0C >>> dev.cpu.13.temperature: 33,0C >>> dev.cpu.14.temperature: 34,0C >>> dev.cpu.15.temperature: 34,0C >>> >>> And it's consistent - cores 4 and 5 always are hotter then any other. >>> This can be something with scheduler, however this started before any >>> actual load. Though numbers are normal I had never seen something >>> alike... >> >> Two cores per socket, and 8 sockets on the board? If so, that looks >> absolutely fine to me. The average temperature is 36.8C but 43.0C is >> still well within spec. That difference of just over 6 degrees is not >> really significant and probably entirely due to different airflow >> patterns over the different CPU sockets. If you swap the CPU package in >> that socket with one of the other ones, you'll find the hot spot stays >> put. You might be able to even things out by rerouteing cables, but >> really it's not worth the hassle and won't make any perceptible >> difference to performance. > > Nope: > > CPU: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz (2394.05-MHz > K8-class CPU) > FreeBSD/SMP: Multiprocessor System Detected: 16 CPUs > FreeBSD/SMP: 2 package(s) x 4 core(s) x 2 SMT threads > > So the difference is about one physical core with two SMT threads. > Which explains why the numbers go in pairs -- there's only 8 physical cores. Even so, I don't think there's any great problem there. Different cores in the same package can have different temperatures -- that's perfectly normal, and due to the physical properties of the CPU package and the local environment rather than any difference in processing load between cores. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: 9.0 spontaneously reboots
On 13/03/2012 09:08, Da Rock wrote: > On 03/13/12 19:11, Edward M. wrote: >> On 03/13/2012 01:59 AM, Volodymyr Kostyrko wrote: >>> I already moved from Kingston to Hynix with no luck. Next guess >>> points is motherboard problem (as memory is separated between >>> processors) or processor problem. I'll gonna pop one processor out >>> Leaving all memory on another one. >>I had a motherboard that was also rebooting constantly, it turned >> out, it was suffering from capacitor plague. >>I suggest to inspect each capacitor for any signs of leak and for >> broken traces. > I have to agree. I've seen this behaviour also on other systems and OS. Yes. A replacement motherboard would be my next step too. While bad capacitors are a fairly common cause, it can be due to other reasons: a crack in one of the traces or a dry-soldered joint that breaks electrical connection because of the effects of thermal expansion, or even the extra vibration when the fans go to full power or even when there is a lot of disk IO activity. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: 9.0 spontaneously reboots
Matthew Seaman wrote: On 13/03/2012 08:59, Volodymyr Kostyrko wrote: The only other weird thing about this server is: dev.cpu.0.temperature: 37,0C dev.cpu.1.temperature: 37,0C dev.cpu.2.temperature: 35,0C dev.cpu.3.temperature: 35,0C dev.cpu.4.temperature: 43,0C dev.cpu.5.temperature: 43,0C dev.cpu.6.temperature: 38,0C dev.cpu.7.temperature: 38,0C dev.cpu.8.temperature: 38,0C dev.cpu.9.temperature: 38,0C dev.cpu.10.temperature: 37,0C dev.cpu.11.temperature: 37,0C dev.cpu.12.temperature: 33,0C dev.cpu.13.temperature: 33,0C dev.cpu.14.temperature: 34,0C dev.cpu.15.temperature: 34,0C And it's consistent - cores 4 and 5 always are hotter then any other. This can be something with scheduler, however this started before any actual load. Though numbers are normal I had never seen something alike... Two cores per socket, and 8 sockets on the board? If so, that looks absolutely fine to me. The average temperature is 36.8C but 43.0C is still well within spec. That difference of just over 6 degrees is not really significant and probably entirely due to different airflow patterns over the different CPU sockets. If you swap the CPU package in that socket with one of the other ones, you'll find the hot spot stays put. You might be able to even things out by rerouteing cables, but really it's not worth the hassle and won't make any perceptible difference to performance. Nope: CPU: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz (2394.05-MHz K8-class CPU) FreeBSD/SMP: Multiprocessor System Detected: 16 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) x 2 SMT threads So the difference is about one physical core with two SMT threads. -- Sphinx of black quartz judge my vow. ___ 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: 9.0 spontaneously reboots
On 13/03/2012 08:59, Volodymyr Kostyrko wrote: > The only other weird thing about this server is: > > dev.cpu.0.temperature: 37,0C > dev.cpu.1.temperature: 37,0C > dev.cpu.2.temperature: 35,0C > dev.cpu.3.temperature: 35,0C > dev.cpu.4.temperature: 43,0C > dev.cpu.5.temperature: 43,0C > dev.cpu.6.temperature: 38,0C > dev.cpu.7.temperature: 38,0C > dev.cpu.8.temperature: 38,0C > dev.cpu.9.temperature: 38,0C > dev.cpu.10.temperature: 37,0C > dev.cpu.11.temperature: 37,0C > dev.cpu.12.temperature: 33,0C > dev.cpu.13.temperature: 33,0C > dev.cpu.14.temperature: 34,0C > dev.cpu.15.temperature: 34,0C > > And it's consistent - cores 4 and 5 always are hotter then any other. > This can be something with scheduler, however this started before any > actual load. Though numbers are normal I had never seen something alike... Two cores per socket, and 8 sockets on the board? If so, that looks absolutely fine to me. The average temperature is 36.8C but 43.0C is still well within spec. That difference of just over 6 degrees is not really significant and probably entirely due to different airflow patterns over the different CPU sockets. If you swap the CPU package in that socket with one of the other ones, you'll find the hot spot stays put. You might be able to even things out by rerouteing cables, but really it's not worth the hassle and won't make any perceptible difference to performance. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: lost+found dir placement
Robert Bonomi mail.r-bonomi.com> writes: > ... > The fsck_ffs manpage says that 'lost+found' is _created_ *when*needed*, > in the root of a filesystem, if not already present. > > The presense of /mnt/lost+found is _not_ an error. just a surperfluous > file that ended up there 'somehow'. > ... This worried me. And still does ... > *IF* you're going to file a PR, it should be for the filesystem > initialization process -- which "should" (a) create the lost+found > directory, (b) create some 'reasonable' number of files in that directory, > and (c) then delete all those files. This ensures that the directory > exists and has disk-space allocated for a 'reasonable' number of > 'recovered' file entries. > That's perhaps why under Linux they have special mklost+found entry ? > The existing fsck_ffs has a catastrophic failure mode if there is no > space on the disk for the lost+found directory to grow to acomodate > the recovered file entries. > I was surprised to find empty lost+found dir in /mnt. drwx-- 2 root wheel 512 May 5 2011 lost+found That's why I jumped a bit. Few days ago, after clean reboot to single user mode, I tested fsck manually on SUJ fs and found things that seemed to be questionable (I posted it on current@ list, if you want to take a look). So, it must have happened during that time, because as I said I did not have any forced fsck run at boot times, and I almost swear I did not have this lost+found dir in /mnt before. I will take a look at source code of fsck* entries and perhaps find a clue. jb ___ 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: oops, now: bsd question: how to record a tv stream?
doesn't VLC do that too? On 11 mrt 2012, at 21:28, Gary Kline wrote: > guys, > > i made the mistake that conrad did when replying. i could make e > excuse liked only getting five hours sleep, etc, bujt i wont. > > here us a FBSD qauestion how can i capture any tv stream---or > radio stream for later replay? or is that illegal, too? > > gray > > > > -- > Gary Kline kl...@thought.org http://www.thought.org Public Service Unix >Voice By Computer (for Universal Access): http:/www.thought.org/vbc > The 8.57a release of Jottings: http://jottings.thought.org >Twenty-five years of service to the Unix community. > > ___ > 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"
Re: 9.0 spontaneously reboots
On 03/13/12 19:11, Edward M. wrote: On 03/13/2012 01:59 AM, Volodymyr Kostyrko wrote: I already moved from Kingston to Hynix with no luck. Next guess points is motherboard problem (as memory is separated between processors) or processor problem. I'll gonna pop one processor out Leaving all memory on another one. I had a motherboard that was also rebooting constantly, it turned out, it was suffering from capacitor plague. I suggest to inspect each capacitor for any signs of leak and for broken traces. I have to agree. I've seen this behaviour also on other systems and OS. ___ 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: 9.0 spontaneously reboots
On 03/13/2012 01:59 AM, Volodymyr Kostyrko wrote: I already moved from Kingston to Hynix with no luck. Next guess points is motherboard problem (as memory is separated between processors) or processor problem. I'll gonna pop one processor out Leaving all memory on another one. I had a motherboard that was also rebooting constantly, it turned out, it was suffering from capacitor plague. I suggest to inspect each capacitor for any signs of leak and for broken traces. ___ 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: 9.0 spontaneously reboots
Matthew Seaman wrote: The only load I know to cause sure lockup in some hours is memcached. Right now project is migrated to redis and machines survives for two weeks. Most common problem for lockup is ECC error. I see. That puts a different complexion on things. Although it is application specific it doesn't rule out hardware problems. In fact, given the nature of the error -- ECC problems -- it pretty much nails it as something wrong with the RAM in that machine. Given that memtest86 doesn't show any problems, and you can run a similar workload with different software it suggests that you have a memory stick (or sticks) that are marginal. Something like extra heat due to higher rates of memory accesses from a particular application could be tipping it over the edge into failure. The 'marginal' behaviour need not be a fault in the memory stick per se. It could simply be the particular characteristics of the memory you have installed not being exactly compatible with your motherboard. In theory the memory conforming to a particular standard should avoid this sort of problem, but this is unfortunately not completely infallible. Swapping out memory sticks for an equivalent specification from a different manufacturer should give good results. I already moved from Kingston to Hynix with no luck. Next guess points is motherboard problem (as memory is separated between processors) or processor problem. I'll gonna pop one processor out Leaving all memory on another one. The only other weird thing about this server is: dev.cpu.0.temperature: 37,0C dev.cpu.1.temperature: 37,0C dev.cpu.2.temperature: 35,0C dev.cpu.3.temperature: 35,0C dev.cpu.4.temperature: 43,0C dev.cpu.5.temperature: 43,0C dev.cpu.6.temperature: 38,0C dev.cpu.7.temperature: 38,0C dev.cpu.8.temperature: 38,0C dev.cpu.9.temperature: 38,0C dev.cpu.10.temperature: 37,0C dev.cpu.11.temperature: 37,0C dev.cpu.12.temperature: 33,0C dev.cpu.13.temperature: 33,0C dev.cpu.14.temperature: 34,0C dev.cpu.15.temperature: 34,0C And it's consistent - cores 4 and 5 always are hotter then any other. This can be something with scheduler, however this started before any actual load. Though numbers are normal I had never seen something alike... -- Sphinx of black quartz judge my vow. ___ 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: 9.0 spontaneously reboots
On 13/03/2012 08:09, Volodymyr Kostyrko wrote: > The only load I know to cause sure lockup in some hours is memcached. > Right now project is migrated to redis and machines survives for two > weeks. Most common problem for lockup is ECC error. I see. That puts a different complexion on things. Although it is application specific it doesn't rule out hardware problems. In fact, given the nature of the error -- ECC problems -- it pretty much nails it as something wrong with the RAM in that machine. Given that memtest86 doesn't show any problems, and you can run a similar workload with different software it suggests that you have a memory stick (or sticks) that are marginal. Something like extra heat due to higher rates of memory accesses from a particular application could be tipping it over the edge into failure. The 'marginal' behaviour need not be a fault in the memory stick per se. It could simply be the particular characteristics of the memory you have installed not being exactly compatible with your motherboard. In theory the memory conforming to a particular standard should avoid this sort of problem, but this is unfortunately not completely infallible. Swapping out memory sticks for an equivalent specification from a different manufacturer should give good results. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: lost+found dir placement
jb wrote: > > Hi, > > Each fs should have its own lost+found directory. > It is used by fsck for placing recovered corrupted fs files in there. > This implies the dir must have already existed (it may not be mounted ad hoc > e.g. at boot time, during fs recovery). > > In FreeBSD 9, I found lost+found dir under /mnt. > This is incorrect - /mnt is defined under all standards (Filesystem Hierarchy > Standard, Unix directory structure) as "contains filesystem mount points". > > So, lost+found dir should exist under root dir as /lost+found. Do you have a filesystem mounted on /mnt? > > Any comments before I file a PR request ? The fsck_ffs manpage says that 'lost+found' is _created_ *when*needed*, in the root of a filesystem, if not already present. The presense of /mnt/lost+found is _not_ an error. just a surperfluous file that ended up there 'somehow'. *IF* you're going to file a PR, it should be for the filesystem initialization process -- which "should" (a) create the lost+found directory, (b) create some 'reasonable' number of files in that directory, and (c) then delete all those files. This ensures that the directory exists and has disk-space allocated for a 'reasonable' number of 'recovered' file entries. The existing fsck_ffs has a catastrophic failure mode if there is no space on the disk for the lost+found directory to grow to acomodate the recovered file entries. ___ 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: 9.0 spontaneously reboots
Da Rock wrote: I have one machine behaving unstable. This happened before 9.0. After upgrading to 9.0 machine was given a light load and now it reboots. Memory was already tested (without any errors) and changed after another reboot. So your RAM is good enough to pass a memory test. It doesn't mean it's not the culprit. Way too many false negatives from those things. Overnight soak test with memtest possible? I'm currently thinking of moving projects from this server to get to it more closely. I can't take server down for so long. But it survives an hour in memtest. -- Sphinx of black quartz judge my vow. ___ 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: lost+found dir placement
On Tue, 13 Mar 2012 07:58:09 + (UTC), jb wrote: > Hi, > > Each fs should have its own lost+found directory. > It is used by fsck for placing recovered corrupted fs files in there. Correct. > This implies the dir must have already existed (it may not be mounted ad hoc > e.g. at boot time, during fs recovery). No. This implication does not exist. If I read /usr/src/sbin/fsck_ffs/dir.c correctly, the lost+found/ directory will be created by fsck if it is required and _not_ present. It will do so on a inode based method (instead of utilizing a file system oriented call to make a directory). This is a requirement because (as you correctly mentioned) the partition checked will not be writable (or even be mounted), so mkdir() and related fs functions cannot be used. Also see an evidence for that idea in "man fsck_ffs". > In FreeBSD 9, I found lost+found dir under /mnt. > This is incorrect - /mnt is defined under all standards (Filesystem Hierarchy > Standard, Unix directory structure) as "contains filesystem mount points". According to "man hier" (mandatory for interpreting the file system hierarchy on FreeBSD) this your assumption sounds correct: /mnt is explained to be an "empty directory commonly used by system administrators as a temporary mount point", so having a lost+found/ directory in there doesn't seem to have any purpose and looks wrong. > So, lost+found dir should exist under root dir as /lost+found. Correct. It will be assigned to the results of possible recoveries of lost data of the / partition correctly. > Any comments before I file a PR request ? If this directory has been created by the installation process, I think you should. Maybe you verify the issue on the freebsd-fs@ list? -- 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"
Re: 9.0 spontaneously reboots
Adam Vande More wrote: I have one machine behaving unstable. This happened before 9.0. After upgrading to 9.0 machine was given a light load and now it reboots. Memory was already tested (without any errors) and changed after another reboot. So your RAM is good enough to pass a memory test. It doesn't mean it's not the culprit. Way too many false negatives from those things. True. First server was stacked with Kingston memory, and now I moved to Hynix. And is still gives me sometimes ECC errors. -- Sphinx of black quartz judge my vow. ___ 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: 9.0 spontaneously reboots
Matthew Seaman wrote: On 12/03/2012 14:07, Volodymyr Kostyrko wrote: What should I blame now? Is it some programming error or should I continue with testing/changing motherboard and cpu? Instability that appears spontaneously (and especially if it persists across system updates) is almost always caused by hardware problems. So, yes, carry on swapping out components until you can isolate where the problem is. Some common hardware problems which might result in the problems you've seen: * PSU going flakey. If you have the right measuring equipment, this is pretty easy to detect by looking at the output voltages -- if they've drifted out of spec, or if you've got mains frequency jitter leaking through then its no wonder your system crashes. Sensors report everything is good. * Similarly, if the crashing is associated with system load, (particularly at startup, when things are happening like disks spinning up) this can indicate a power supply fading under load. That can happen due to age, or because you've been adding extra hardware and haven't considered the power requirements. The only load I know to cause sure lockup in some hours is memcached. Right now project is migrated to redis and machines survives for two weeks. Most common problem for lockup is ECC error. * The other reason for crashing under load is overheating. Sometimes this can be cured easily by cleaning dust out of vents and heat-sinks. Check too for fans either seized or running slowly. Sensors reports normal temperature. * You may need to clean off any old heat-sink compound and re-apply a fresh layer, especially if you've taken CPU coolers off at some point. * There's also the old capacitor problem: electrolytic capacitors have a failure mode that generates some positive pressure inside them. This is detectable by the end of the capacitor being bowed out, rather than slightly concave. (Generally this means a new motherboard, although I've heard of people being able to solder in replacements successfully.) It's fully serviced SuperMicro server without any additional problems. Other than that, try disconnecting and reconnecting peripherals like disks or DVDs and so forth in various combinations to test if that improves system stability. One faulty component can knock the whole machine over. -- Sphinx of black quartz judge my vow. ___ 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: lost+found dir placement
On Tue, Mar 13, 2012 at 2:58 AM, jb wrote: > Hi, > > Each fs should have its own lost+found directory. > It is used by fsck for placing recovered corrupted fs files in there. > This implies the dir must have already existed (it may not be mounted ad > hoc > e.g. at boot time, during fs recovery). > > In FreeBSD 9, I found lost+found dir under /mnt. > This is incorrect - /mnt is defined under all standards (Filesystem > Hierarchy > Standard, Unix directory structure) as "contains filesystem mount points". > > So, lost+found dir should exist under root dir as /lost+found. > > Any comments before I file a PR request ? > jb > The directory is created in the top of the filesystem, so you should check what is mounted on /mnt. Filesystem Hierarchy Standard -- This is a Linux standard. For info on FreeBSD hierarchy see man hier(7) -- Adam Vande More ___ 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"
lost+found dir placement
Hi, Each fs should have its own lost+found directory. It is used by fsck for placing recovered corrupted fs files in there. This implies the dir must have already existed (it may not be mounted ad hoc e.g. at boot time, during fs recovery). In FreeBSD 9, I found lost+found dir under /mnt. This is incorrect - /mnt is defined under all standards (Filesystem Hierarchy Standard, Unix directory structure) as "contains filesystem mount points". So, lost+found dir should exist under root dir as /lost+found. Any comments before I file a PR request ? jb ___ 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: /usr/lib32 question
On Tue, Mar 13, 2012 at 12:06 AM, Polytropon wrote: > On Mon, 12 Mar 2012 23:49:50 -0700, Waitman Gobble wrote: > > Hi, > > > > > > I have four files in /usr/lib32 - libc.so.7, libcrypt.so.5, librt.so.1, > > libthr.so.3 that are 444 root. Seems like i am unable to change > permissions > > or remove... any idea why? or really, how to delete those files. it's an > > amd64 machine. > > I'm on i386 here, so I can't check, but: > > See if the files have additional flags set, especially > the "system immutable" flag (schg): > ># ls -lo /usr/lib32 > > If neccessary, use: > ># chflags noschg /usr/lib32/* > > and continue trying to change permissions or remove the > files in that directory. > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > cool, thank you. Waitman Gobble San Jose California USa ___ 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: /usr/lib32 question
On Mon, 12 Mar 2012 23:49:50 -0700, Waitman Gobble wrote: > Hi, > > > I have four files in /usr/lib32 - libc.so.7, libcrypt.so.5, librt.so.1, > libthr.so.3 that are 444 root. Seems like i am unable to change permissions > or remove... any idea why? or really, how to delete those files. it's an > amd64 machine. I'm on i386 here, so I can't check, but: See if the files have additional flags set, especially the "system immutable" flag (schg): # ls -lo /usr/lib32 If neccessary, use: # chflags noschg /usr/lib32/* and continue trying to change permissions or remove the files in that directory. -- 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"
Re: /usr/lib32 question
On Mon, Mar 12, 2012 at 11:49 PM, Waitman Gobble wrote: > Hi, > > > I have four files in /usr/lib32 - libc.so.7, libcrypt.so.5, librt.so.1, > libthr.so.3 that are 444 root. Seems like i am unable to change permissions > or remove... any idea why? or really, how to delete those files. it's an > amd64 machine. > > Thanks, > Waitman Gobble > San Jose California USA > > oops, duh sorry it's late. figured it out. :) chflags noschg Thanks Waitman Gobble San Jose California USA ___ 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"
