Date: Sat, 29 Sep 2007 00:52:03 +0200 From: Roland Smith <rsmith@xs4all.nl> To: neal <kneel.pardoe@virgin.net> Cc: freebsd-questions@freebsd.org Subject: Re: newby needing help Message-ID: <20070928225203.GA49278@slackbox.xs4all.nl> In-Reply-To: <46FD74A6.7060808@virgin.net> References: <46FC1C65.6060801@virgin.net> <20070927212854.GA18018@slackbox.xs4all.nl> <46FD74A6.7060808@virgin.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--AhhlLboLdkugWU4S Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 28, 2007 at 09:39:50PM +0000, neal wrote: > Roland Smith wrote: >> On Thu, Sep 27, 2007 at 09:11:01PM +0000, neal wrote: >>> I've checked out all the main functions I want from FreeBSD and had the= m=20 >>> all working (hehe, but since broke some) so I'm happy it will do the=20 >>> things I want so far. >>>=20 >>> First question, what is recommended regarding doing updates. Is it best= =20 >>> to just do all of them? >> It depends. If the update of the base system concerns something that you >> use, I would definitely install it. >=20 > That's the problem though, same with linux, there are obvious things that= I=20 > would update but there are likely items that I would never have a clue if= I=20 > needed them or not. As I'm going to do a completely fresh install on a=20 > clean system I might just try doing all upgrades right from the start and= =20 > see how it goes from there. There are different branches that you can follow. You could go for 6.2-RELEASE with (security patches). You won't have to update this often. Or if you need drivers or features that are not in RELEASE yet, you can follow 6-STABLE. 7-CURRENT is for those feeling adventurous. I'd recommend starting with 6.2-RELEASE with patches. =20 >> The best way to keep the base system up-to-date is using csup (which is >> still referenced in the Handbook in =A720.3 as cvsup). >> For updating the ports tree I can recommend portsnap. For updating the >> ports themselves I use portmaster. >>> I have always had problems doing this e.g. with Mandrake and other Linu= xs=20 >>> and so am reluctant, but if it is usual I'll give it a try. >> The upgrade tools on FreeBSD work quite well. But if you're rebuilding >> your own ports it can take quite some time depending on your machine. >=20 > I've been using the Package Manager so far but will look into using a=20 > command prompt at some later time. I've never used "Package Manager". I didn't even know FreeBSD had one. :-) >>> I have a drive hda, it has a swap an unused space and four partitions o= ne=20 >>> of which is my home partition hda7. How do I refer to this home partiti= on=20 >>> using ad0??? >>> notation=20 >> If you do 'ls ad0*' you'll see what is available. Remember that what DOS >> and Linux calls partitions are called slices in FreeBSD. Partitions in >> FreeBSD are subdivisions of a slice. E.g. ad0s1a is partition a of slice >> 1 of ad0. Customarily, slice b is used for swap, and slice c is >> unused. You can see this with the 'bsdlabel' command. >=20 > OK, I've done that. >=20 > this is the result for the drive currently being used by linux. > ------------------------- > [pineal@localhost /usr/home/pineal]$ ls /dev/ad0* > /dev/ad0 /dev/ad0s2 /dev/ad0s6 /dev/ad0s8 > /dev/ad0s1 /dev/ad0s5 /dev/ad0s7 /dev/ad0s9 > ------------------------- >=20 > The number of apparent slices (those with a ad0s[n] designation) seen by= =20 > BSD is one more than the number of linux partitions I actually have. No I= =20 > haven't miss-counted. >=20 > I have 1 swapfile partition and five partitions hda5-9 used by linux. Try mounting slices 5-9 with mount_ext2fs (as root). =20 > btw I tried to run the bsdlabel command but it returns "no valid label=20 > found" for both ad0 and ad1. My bad. That only works with BSD partitions. =20 > Maybe I didn't make myself clear here. I have an existing in-use Linux=20 > system. I want to be able to access the /home partition as it contains al= l=20 > my personal data that I will need to move over to FreeBSD when I do the n= ew=20 > install. I would still recommend moving the data to a UFS2 filesystem. >> You might find =A716.3 of the Handbook enlightening. >=20 > did you mean from Ch 16 "3. Why will chmod not change the permissions on= =20 > symlinks?" I mean chapter 16, section 3; "Adding Disks" (on my 6-STABLE system). The HTML version lives at=20 file:///usr/share/doc/en_US.ISO8859-1/books/handbook/disks-adding.html =20 Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --AhhlLboLdkugWU4S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFG/YWSEnfvsMMhpyURAvLzAJoC1Cy9nvM2P85op/2YuJ+Z04F5ZwCfep2m T7tCmRS/LRqbRjPrO7jTi+A= =BAXC -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070928225203.GA49278>