Re: FreeBSD on Acer C7 Chromebook?
Yes. I plan to try to get FreeBSD booting on a Chromebox (not the same but close enough- both use the 2nd generation core boot firmware described here http://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/custom-firmware). Don't hold your breath. It's not clear this can be done without some programming. The boot codes for Chrome OS devices aren't so much "non standard BIOS" as completely their own thing. Nothing wrong with that, but it makes booting anything other than your own linux kernel very difficult. If anyone beats me to it, PLEASE, post to the Chrome OS mailing list with how you do it! Or somehow make it known Trever On Tuesday, February 5, 2013 6:45:13 AM UTC-8, Arthur Chance wrote: > > [I'm not sure whether this would be better on -hackers@ or -hardware@ > but -questions@ seems like a good place to start.] > > Is anyone considering getting FBSD to run on the Acer C7 Chromebook? The > pros are that it's a cheap, small and relatively lightweight 64 bit > Intel portable using integrated Intel graphics. The cons are that it's a > Chromebook, so has a completely non-standard BIOS and boot sequence. > However, Ubuntu has been hacked to boot on it (Google for "ChrUbuntu") > so it's not totally locked down. > > This would make a very useful little system, but the programming needed > is beyond my skill set I'm afraid. > ___ > freebsd-...@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: sysctl security.jail.* descriptions
Jamie Gritton wrote: On 02/06/13 09:59, Fbsd8 wrote: > Fbsd8 wrote: >> Waitman Gobble wrote: >>> On Feb 6, 2013 7:17 AM, "Fbsd8" wrote: Waitman Gobble wrote: > On Feb 6, 2013 7:02 AM, "Fbsd8" wrote: >> Where do I find the descriptions of what these jail MIBs do? ... >> security.jail.param.securelevel: 0 >> security.jail.param.path: 1024 >> security.jail.param.name: 256 >> security.jail.param.parent: 0 >> security.jail.param.jid: 0 ... >> >> What about the other security.jail.param.* MIBs >> where are they documented at? In the jail(8) main page, there's the following tidbit: | Jails have a set a core parameters, and kernel modules can add their | own jail parameters. The current set of available parameters can be | retrieved via ``sysctl -d security.jail.param''. Any parameters not | set will be given default values, often based on the current | environment. The sysctls do not themselves have values. Their useful parts are the associated types and descriptions (as well as their very existence). The descriptions are good for the above-mentioned "sysctl -d", and the types are used by jail(8) to know how to set a particular parameter. Rereading the "man jail" for 9.1 talks about securelevel as a jail parammeter. So correct me if I an wrong. All the security.jail.param.* MIBs are set in rc.conf or /etc/jail.conf file on a per jail bases by changing the word "parm" to the jailname? There's not always a direct connection between the jail parameters and the current rc.conf values. The jail parameters are what you'd use in a jail.conf(5) file, or in the "jail_jailname_parameters" rc variable. - Jamie Yes I read man jail and issued the "sysctl -d" to get the list of MIBs I posted. So I am still left with no explanation of HOW to code these new jail MIBs in 9.X to enable them on a per jail bases. Any thoughts on how to do that? ___ 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: sysctl security.jail.* descriptions
On 02/07/13 05:55, Fbsd8 wrote: Jamie Gritton wrote: On 02/06/13 09:59, Fbsd8 wrote: > Fbsd8 wrote: >> Waitman Gobble wrote: >>> On Feb 6, 2013 7:17 AM, "Fbsd8" wrote: Waitman Gobble wrote: > On Feb 6, 2013 7:02 AM, "Fbsd8" wrote: >> Where do I find the descriptions of what these jail MIBs do? ... >> security.jail.param.securelevel: 0 >> security.jail.param.path: 1024 >> security.jail.param.name: 256 >> security.jail.param.parent: 0 >> security.jail.param.jid: 0 ... >> >> What about the other security.jail.param.* MIBs >> where are they documented at? In the jail(8) main page, there's the following tidbit: | Jails have a set a core parameters, and kernel modules can add their | own jail parameters. The current set of available parameters can be | retrieved via ``sysctl -d security.jail.param''. Any parameters not | set will be given default values, often based on the current | environment. The sysctls do not themselves have values. Their useful parts are the associated types and descriptions (as well as their very existence). The descriptions are good for the above-mentioned "sysctl -d", and the types are used by jail(8) to know how to set a particular parameter. Rereading the "man jail" for 9.1 talks about securelevel as a jail parammeter. So correct me if I an wrong. All the security.jail.param.* MIBs are set in rc.conf or /etc/jail.conf file on a per jail bases by changing the word "parm" to the jailname? There's not always a direct connection between the jail parameters and the current rc.conf values. The jail parameters are what you'd use in a jail.conf(5) file, or in the "jail_jailname_parameters" rc variable. - Jamie Yes I read man jail and issued the "sysctl -d" to get the list of MIBs I posted. So I am still left with no explanation of HOW to code these new jail MIBs in 9.X to enable them on a per jail bases. Any thoughts on how to do that? Well the jail(8) man page is all about setting these parameters. You might also want to take a look at jail.conf(5) which I mentioned. But don't think of them as MIBs anymore - the "-d" is the only thing you'll have to do directly with the sysctls. - Jamie ___ 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"
GPIO in 9.1-RELEASE
I'm moving this thread from hardware@, I think this ain't the rigth list, is it? Hi list, I have a net4801 Soekris board. It has 12-pin GPIO interface. An almost GENERIC kernel doesn't show any /dev/gpio* device. I tried including device gpio and I see the module with # kldstat -v | grep gpio but still no /dev/gpio* device. Could anyone point me to the steps to follow in order to enable such interface? And taking the opportunity for a second shot, any recommendation for a Perl module to work with? Thanks in advance Regards. Alberto Mijares ___ 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: How to add unused space to an existing install
--On February 6, 2013 5:21:39 PM -0600 dte...@freebsd.org wrote: -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Paul Schmehl Sent: Wednesday, February 06, 2013 9:59 AM To: FreeBSD Questions List Subject: How to add unused space to an existing install I have a FreeBSD 8.3 RELEASE box that we recently discovered only has part of the "disk" being used. This box has four 1TB drives in RAID 5, and df only shows 500MB of disk available. fdisk shows this: # fdisk -p # /dev/mfid0 g c364602 h255 s63 p 1 0xa5 63 1562363771 a 1 When I run the fdisk editor in sysinstall I see this: Disk name: mfid0 FDISK Partition Editor DISK Geometry: 364602 cyls/255 heads/63 sectors = 5857331130 sectors (2860024MB) Offset Size(ST)End Name PType Desc Subtype Flags 0 63 62- 12 unused0 63 1562363771 1562363833 mfid0s1 8freebsd 165 1562363834 4294981702 5857345535- 12 unused0 I want to capture all that unused space and add it to the server. fstab has this: # cat /etc/fstab # DeviceMountpoint FStype Options Dump Pass# /dev/mfid0s1b noneswapsw 0 0 /dev/mfid0s1a / ufs rw 1 1 /dev/mfid0s1e /home ufs rw 2 2 /dev/mfid0s1d /tmpufs rw 2 2 /dev/mfid0s1f /usrufs rw 2 2 /dev/mfid0s1g /varufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 When I try to create a new slice using fdisk, it doesn't seem to work. Did you try something like: echo "p 2 165 * *" | sudo fdisk -f- /dev/mfid0 ?? Thank you for your detailed and informative answer. I did not. I'm a neophyte in the disk world. I've always used sysinstall to setup partitions and mount points. Afterward "fdisk -p" should show something like... # /dev/mfid0 g c364602 h255 s63 p 1 0xa5 63 1562363771 p 2 0xa5 a 1 And then you'll have /dev/mfid0s2 which you can do-with what you like (directly newfs the slice or create BSD partitions underneath that to further sub-divide into as many as 8 smaller units, /dev/mfid0s2[a-h]). I've been doing some more research on this problem, and I've discovered that bsdlabel has a 2 to the 32nd limit on disk size. It appears I have to use gpart instead. Is that not correct? If I move to the label editor, I get this: FreeBSD Disklabel Editor Disk: mfid0 Partition name: mfid0s1 Free: 0 blocks (0MB) Part Mount Size Newfs Part Mount Size Newfs - - - - mfid0s1a 2000MB * mfid0s1d65536MB * mfid0s1e 4096MB * mfid0s1b swap65536MB SWAP mfid0s1f10240MB * mfid0s1g 601GB * As you can see mfid0s1g is 601GB, and according to fstab that's /var. Yet df -h shows: # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/mfid0s1a1.9G726M1.0G41%/ devfs1.0k1.0k 0B 100%/dev /dev/mfid0s1e3.9G 38M3.5G 1%/home /dev/mfid0s1d 62G6.6M 57G 0%/tmp /dev/mfid0s1f9.7G7.5G1.4G84%/usr /dev/mfid0s1g582G 39G496G 7%/var So apparently I'm not creating this new slice? It should be /dev/mfid0s1h, correct? Let's not confuse slices (DOS partitions) with disklabels (BSD partitions). OK. I've clearly done that. As I say, I'm a neophyte in the disk geometry and configuration field. DOS partitions are (maximum 4 per disk): mfid0s1 mfid0s2 mfid0s3 mfid0s4 (according to your "fdisk -p" output, you're mfid0 disk is currently only using mfid0s1) BSD partitions are (maximum 8 per "slice" aka DOS partition): mfid0s1a mfid0s1b mfid0s1c mfid0s1d mfid0s1e mfid0s1f mfid0s1g mfid0s1h (according to your sysinstall output, you're mfid0s1 slice has 5 BSD partitions -- a, e, d, f, and g) I see. How to I "recapture" the remaining 2+TB of space that's not being used? The easiest way to use your extra space is to not adjust one of those 5 BSD partitions, but instead create a new DOS partition (mfid0s2 as previously discussed above). However, if you *really* want to "grow" an existing BSD partition, this can be done (very carefully). I'm all for taking the easy way out. :-) First, you'll want to save the output of "disklabel -r mfid0s1" to a text file. Next, you'll have to re-fdisk mfid0 so that the first slice covers the entire disk. Of course, re-mastering the slices does not affect the data, but it _will_ wipe out the BSD partition map (the disklabels; in other words, after using fdisk
RE: How to add unused space to an existing install
On 7 Feb 2013, Paul Schmehl wrote: > > --On February 6, 2013 5:21:39 PM -0600 dte...@freebsd.org wrote: > > > > > > >> -Original Message- > >> From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- > >> questi...@freebsd.org] On Behalf Of Paul Schmehl > >> Sent: Wednesday, February 06, 2013 9:59 AM > >> To: FreeBSD Questions List > >> Subject: How to add unused space to an existing install > >> > >> I have a FreeBSD 8.3 RELEASE box that we recently discovered only has > >> part of the "disk" being used. This box has four 1TB drives in RAID 5, > >> and df only shows 500MB of disk available. > >> > >> fdisk shows this: > >> # fdisk -p > >> # /dev/mfid0 > >> g c364602 h255 s63 > >> p 1 0xa5 63 1562363771 > >> a 1 > >> > >> When I run the fdisk editor in sysinstall I see this: > >> > >> Disk name: mfid0 FDISK Partition > >> Editor > >> DISK Geometry: 364602 cyls/255 heads/63 sectors = 5857331130 sectors > >> (2860024MB) > >> > >> Offset Size(ST)End Name PType Desc Subtype > >> Flags > >> > >> 0 63 62- 12 unused0 > >> 63 1562363771 1562363833 mfid0s1 8freebsd 165 > >> 1562363834 4294981702 5857345535- 12 unused0 > >> > >> I want to capture all that unused space and add it to the server. > >> > >> fstab has this: > >> # cat /etc/fstab > >> # Device Mountpoint FStype Options Dump > >> Pass# > >> /dev/mfid0s1bnoneswapsw 0 > >> 0 > >> /dev/mfid0s1a/ ufs rw 1 > >> 1 > >> /dev/mfid0s1e/home ufs rw 2 > >> 2 > >> /dev/mfid0s1d/tmpufs rw 2 > >> 2 > >> /dev/mfid0s1f/usrufs rw 2 > >> 2 > >> /dev/mfid0s1g/varufs rw 2 > >> 2 > >> /dev/acd0/cdrom cd9660 ro,noauto 0 0 > >> > >> When I try to create a new slice using fdisk, it doesn't seem to work. > > > > Did you try something like: > > > > echo "p 2 165 * *" | sudo fdisk -f- /dev/mfid0 > > > > ?? > > Thank you for your detailed and informative answer. > > I did not. I'm a neophyte in the disk world. I've always used sysinstall > to setup partitions and mount points. > > > > > Afterward "fdisk -p" should show something like... > > > ># /dev/mfid0 > > g c364602 h255 s63 > > p 1 0xa5 63 1562363771 > > p 2 0xa5 > > a 1 > > > > And then you'll have /dev/mfid0s2 which you can do-with what you like > > (directly newfs the slice or create BSD partitions underneath that to > > further sub-divide into as many as 8 smaller units, /dev/mfid0s2[a-h]). > > > > I've been doing some more research on this problem, and I've discovered > that bsdlabel has a 2 to the 32nd limit on disk size. It appears I have to > use gpart instead. Is that not correct? > Only if your disk is larger than 2TB (or 2048GB). If you try to partition a >2TB disk with fdisk the most you can hope to access is 2TB (the rest will be forever unused). I was noticing that that the total size for all your partitions is about 744.95GB -- far short of the maximum addressable of 2TB. So you *could* gain access to more space with the tricks discussed here, but yes... You will be required to use gpart to address more than 2TB of storage on a single discrete disk. gpart creates a GPT layout versus fdisk which creates an MBR layout. GPT uses length identifiers double that of MBR so you should be able to address up to 16 million terabytes on any single discrete disk with gpart. That ought to be enough for a while (the largest storage array known to exist today is in the Petabytes ... thousands of terabytes -- nobody has yet produced a single storage device of contiguous addressable space matching-or-exceeding 1024 petabytes or 1M terabytes; so we have a ways to go before anybody reaches the limit of 2^64). > > > >> If I move to the label editor, I get this: > >> > >> FreeBSD Disklabel Editor > >> > >> Disk: mfid0 Partition name: mfid0s1 Free: 0 blocks (0MB) > >> > >> Part Mount Size Newfs Part Mount Size Newfs > >> - - - - > >> mfid0s1a 2000MB * > >> mfid0s1d65536MB * > >> mfid0s1e 4096MB * > >> mfid0s1b swap65536MB SWAP > >> mfid0s1f10240MB * > >> mfid0s1g 601GB * > >> > >> As you can see mfid0s1g is 601GB, and according to fstab that's /var. > >> > >> Yet df -h shows: > >> > >> # df -h > >> Filesystem SizeUsed Avail Capacity Mounted on > >> /dev/mfid0s1a1.9G726M1.0G41%/ > >> devfs1.0k1.0k 0B 100%/dev > >> /dev/mfid0s1e3.9G 38M3.5G
Re: geli overhead?
On Mon, 4 Feb 2013 22:25:33 +0100 mhca12 wrote: > Does skipping authentication also remove the requirement of > zeroing the whole eli disk for the checksums? It's not needed from that perspective, but it makes it a bit more secure if you do that or fill the device from /dev/random before the init. If you don't do either an attacker may be able infer information about the layout of files. ___ 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"
off-topic....
guys, ihad better make this fast; this desktop [dell duo] has been crashing at random for the past couple month. no clue. but ive ordered a refurb with a three-year warranty. I hope, I hope. my question is: how to set up an account for code on google-code. I'v found a 'cheat sheet' site and others that should help me with svn. I have used cvs [late 90's]; I use rcs daily and figure I'll learn subversion in time. but what else do I have to do to get my "vbc" code over on google? their explaination is written in hieroglyphics. enough. gary ps: I t is worth noting that my vbc wworks on freebsd so long as youve got espeak and the gtk stuff. -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Twenty-six 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: NcFTPd on 9.1 64-bit
Jim Pazarena wrote, On 2013-01-27 7:58 PM: I have found that on the two machines which I installed 9.1 on, NcFTPd fails system logins for non-root attempts with "Password wrong for user from 192.168.1.51" These are logins which previously on 9.0 worked as expected, and now fail on 9.1. Has anyone else experienced this? Any suggestions? Thanks! No one has answered on this question, and supp...@ncftp.com is also silent. I *do* see an error go by during boot, which states "unable to open /etc/auth.conf" FreeBSD 9.1 does not HAVE auth.conf (9.0 DOES) failing getting NcFTPd working, what is the next ftpd recommended ? ___ 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: NcFTPd on 9.1 64-bit
Jim Pazarena wrote: Jim Pazarena wrote, On 2013-01-27 7:58 PM: I have found that on the two machines which I installed 9.1 on, NcFTPd fails system logins for non-root attempts with "Password wrong for user from 192.168.1.51" These are logins which previously on 9.0 worked as expected, and now fail on 9.1. Has anyone else experienced this? Any suggestions? Thanks! No one has answered on this question, and supp...@ncftp.com is also silent. I *do* see an error go by during boot, which states "unable to open /etc/auth.conf" FreeBSD 9.1 does not HAVE auth.conf (9.0 DOES) failing getting NcFTPd working, what is the next ftpd recommended ? Did you try moving the 9.0 /etc/auth.conf to your 9.1 system? ___ 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: How to add unused space to an existing install
On Thu, 7 Feb 2013, Teske, Devin wrote: On 7 Feb 2013, Paul Schmehl wrote: I've been doing some more research on this problem, and I've discovered that bsdlabel has a 2 to the 32nd limit on disk size. It appears I have to use gpart instead. Is that not correct? Only if your disk is larger than 2TB (or 2048GB). If you try to partition a >2TB disk with fdisk the most you can hope to access is 2TB (the rest will be forever unused). I was noticing that that the total size for all your partitions is about 744.95GB -- far short of the maximum addressable of 2TB. So you *could* gain access to more space with the tricks discussed here, but yes... You will be required to use gpart to address more than 2TB of storage on a single discrete disk. gpart creates a GPT layout versus fdisk which creates an MBR layout. GPT uses length identifiers double that of MBR so you should be able to address up to 16 million terabytes on any single discrete disk with gpart. That ought to be enough for a while (the largest storage array known to exist today is in the Petabytes ... thousands of terabytes -- nobody has yet produced a single storage device of contiguous addressable space matching-or-exceeding 1024 petabytes or 1M terabytes; so we have a ways to go before anybody reaches the limit of 2^64). To be exact: fdisk can only deal with MBR partitioning. bsdlabel only deals with FreeBSD partitions. Both align partitions to CHS values, which don't apply to disks made in the last couple of decades. This means that partitions created by these two tools will almost certainly be misaligned when created on an Advanced Format (4K) hard drive or an SSD. gpart(8) can do GPT *and* MBR *and* bsdlabel and other partition schemes. It does all the things that fdisk and bsdlabel do, and more. For examples of creating both GPT and MBR/bsdlabel partitioning with gpart: http://www.wonkity.com/~wblock/docs/html/disksetup.html ___ 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"
Fwd:
http://www.pixfoto.it/6qydll.php?s=ot ___ 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: NcFTPd on 9.1 64-bit
On 2013-02-07 5:55 PM, Jim Pazarena wrote: Jim Pazarena wrote, On 2013-01-27 7:58 PM: I have found that on the two machines which I installed 9.1 on, NcFTPd fails system logins for non-root attempts with "Password wrong for user from 192.168.1.51" These are logins which previously on 9.0 worked as expected, and now fail on 9.1. Has anyone else experienced this? Any suggestions? Thanks! No one has answered on this question, and supp...@ncftp.com is also silent. I *do* see an error go by during boot, which states "unable to open /etc/auth.conf" FreeBSD 9.1 does not HAVE auth.conf (9.0 DOES) The creator of NcFTPd (Mike Gleason) provided me a 9.1 version, and it works as expected. Kudos to Mike. -- Jim Pazarena fqu...@paz.bz ___ 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"
Fwd:
http://www.cinzianumviaggi.com/6c9cxj.php?s=ot ___ 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"
