Accidentally deleted all contents of /usr/port/sysutil using rm -rf

aurora72 · #1 May 27th, 2009, 01:19

Late at night while trying to port an application, I have accidentally deleted all contents of /usr/port/sysutil using
rm -rf.

Now, how do I return them back in any way (i.e. reinstalling them thru the FreeBSD 6.3 Installation CD's, or simply recovering them from harddisk)

mount -l gives:
/dev/ad0sle on / (ufs, local)
devfs on /dev (devfs, local)
...

DrJ · #2 May 27th, 2009, 01:22

Just update your ports tree using your favorite utility (such as csup or cvsup). The directory will be restored, albeit in updated form.

mdg583 · #3 May 27th, 2009, 02:37

I am not at my freebsd desktop now, but I used a line like this in my supfile:
*default date=2009.04.28.23.59.59
Maybe you can google it, and set it to about the time of the release, if you really don't want an updated ports tree.

pbd · #4 May 27th, 2009, 10:00

If you want the original ports tree from FreeBSD 6.3, unpack it from CD, or fetch it:

Code:

fetch -o - ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/6.3-RELEASE/ports/ports.tgz | tar -z -x -v --include ports/sysutils -f - -C /usr/

You can also update your ports tree, which will "restore" your ports/sysutils - create a supfile as described in

Quote:

/usr/share/examples/cvsup/ports-supfile

and use cvsup as described in

Quote:

http://www.freebsd.org/doc/en/books/handbook/cvsup.html

vivek · #5 May 27th, 2009, 10:52

Or run portsnap:

Code:

portsnap fetch extract

**DutchDaemon** · #6 May 27th, 2009, 10:56

Was portsnap already in the 6.3 base system? Don't remember.

vivek · #7 May 27th, 2009, 11:17

On FreeBSD v6.0 or above, portsnap is contained in the FreeBSD base / core system. You only need to to install portsanp if you are using older version i.e. 5.x

pbd · #8 May 27th, 2009, 11:19

Quote:

Originally Posted by DutchDaemon

Was portsnap already in the 6.3 base system? Don't remember.

Yes, it is.

Code:

# uname -a
FreeBSD ... 6.3-RELEASE-p10 FreeBSD 6.3-RELEASE-p10 #0: Thu Apr 23 02:58:25 CEST 2009     root@...:/usr/obj/usr/src/sys/KERNEL  i386
# which portsnap 
/usr/sbin/portsnap

richardpl · #9 May 27th, 2009, 12:21

Quote:

Originally Posted by vivek

Or run portsnap:

Code:

portsnap fetch extract

Overbloat, in OP case

Quote:

portsnap extract sysutils

Please next time do RTFM, portsnap(8)

**DutchDaemon** · #10 May 27th, 2009, 12:26

Doesn't incorporating a ports 'subtree' into an existing (and seemingly untouched) 6.3 ports tree cause problems with INDEX, versions, dependencies, et al.?

richardpl · #11 May 27th, 2009, 12:35

Well if OP use old ports tree that is another pile of problems .... in this case portsnap just extract one subtree(aka path) instead extracting all tree.
If it doesn't require fetch command I don't see any problems.

**DutchDaemon** · #12 May 27th, 2009, 12:47

Ok, aurora72:

- are you using an unaltered 6.3 ports tree as it came off the CD?
-> use the suggestion in post #3 (fetch the 'frozen' 6.3 ports snapshot and extract the sysutils stuff)

- are you using an up-to-date ports tree?
-> use the 'partial portsnap' solution and restore sysutils

- are you unsure at what stage your ports tree is right now?
-> get with the program and use 'portsnap fetch extract' once and 'portsnap fetch update' in the future

vivek · #13 May 27th, 2009, 13:01

Quote:

Originally Posted by richardpl

Overbloat, in OP case

Please next time do RTFM, portsnap(8)

It is not a bad idea to make entire tree upto date. OP can update all outdated package. I will take security any day over little spend to perform ports tree (and ports itself) to upgrade

Also, modern hardware and network is pretty powerful to handle any overbloat that cab be caused by 48MB file. If OP is on home computer with crappy internet than only I guess it is overbloat...

aurora72 · #14 May 27th, 2009, 13:31

Quote:

Originally Posted by DutchDaemon

Ok, aurora72:

- are you using an unaltered 6.3 ports tree as it came off the CD?
-> use the suggestion in post #3 (fetch the 'frozen' 6.3 ports snapshot and extract the sysutils stuff)

- are you using an up-to-date ports tree?
-> use the 'partial portsnap' solution and restore sysutils

- are you unsure at what stage your ports tree is right now?
-> get with the program and use 'portsnap fetch extract' once and 'portsnap fetch update' in the future

Well, first of all I must say that my FreeBSD computer's got no Internet connection as I'm still trying to make its wireless PCI card work with NDISWrapper.

Also, I have written the FreeBSD version wrong, it must have been 6.4 and not 6.3. (I was sleepy as I wrote it last night) To be exact, the version is 6.4-RELEASE and machine : i386

So now I have 3 Installation CD's of FreeBSD 6.4 which are labeled as CD#1, CD#2 and CD#3, though I haven't used the CD#3 during the installation.

Among the suggestions, the one made by pbd in particular, suggests that I use

Code:

fetch -o - ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/6.3-RELEASE/ports/ports.tgz | tar -z -x -v --include ports/sysutils -f - -C /usr/

which I cannot, as it's not connected to Internet.

So which way should I use to reinstall the sysutils from CD?

Thanks.

**DutchDaemon** · #15 May 27th, 2009, 13:36

Ok:

Code:

Type:  sysinstall
Choose: Configure
Choose: Distributions
Check: [X] Ports
Select: 1 Install from CD/DVD
Select: your CD/DVD Drive

Take it from there. I don't have CDs here, so I can't look beyond that point.

Once you have an Internet connection, update the ports tree and keep it up-to-date using portsnap(8). Use ports-mgmt/portmaster or ports-mgmt/portupgrade for updating ports (applications).

aurora72 · #16 May 27th, 2009, 15:28

Quote:

Originally Posted by DutchDaemon

Code:

Type:  sysinstall
Choose: Configure
Choose: Distributions
Check: [X] Ports
Select: 1 Install from CD/DVD
Select: your CD/DVD Drive

I was browsing the sysinstall documents and that procedure has cut it. It downloaded >40MB of files from the CD#1 and everything's now back in place. Might seem like a rough way of recovering only the "sysutils" but I had no other choice as I'm still a newbie and that's why the suggestions of other friends looked intimitading to me, though they were technically more precise...

I can go on installing the NDISWrapper and the WiFi PCI card now

richardpl · #17 May 27th, 2009, 15:45

This is second time you mentioned NDISWrapper. But NDISWrapper is available only for linux. *BSD use NDISulator aka Project Evil TM

Mel_Flynn · #18 May 27th, 2009, 21:43

Quote:

Originally Posted by richardpl

This is second time you mentioned NDISWrapper. But NDISWrapper is available only for linux. *BSD use NDISulator aka Project Evil TM

That's not so bad. I call ubuntu MS Linux.
(iow: can't we all get along? It really is a wrapper around the NDIS protocol, but the name was taken, hmm?)

richardpl · #19 May 27th, 2009, 23:31

Are you serious?
That is same as calling linux freebsd or freebsd linux.

They are doing same thing but in completly different way so it is incorrect to deny existence of any of them.

I'm going for another happy pill now ... please wait

**SirDice** · #20 May 28th, 2009, 07:43

Quote:

Originally Posted by richardpl

This is second time you mentioned NDISWrapper. But NDISWrapper is available only for linux. *BSD use NDISulator aka Project Evil TM

ndis(4)

I'd call it ndiswrapper too

richardpl · #21 May 28th, 2009, 09:00

You can call it NWO if you want.
Oh those kids today ...

fronclynne · #22 May 28th, 2009, 22:01

. . . just don't call me late for dinner.

aurora72 · #23 May 29th, 2009, 23:53

I wouldn't guess that the thread would go on, but anyways that's fine. Well, having come over the problems I had at the start, I gave a little pause and did not attempt to use the WiFi PCI card on my FreeBSD machine for a while but soon I will start working on it.

As for the confusion about the naming of NDIS simulator/wrapper richardpl's correct in emphazising the difference between, because the name "NDISulator" is present on "Setting up network interface cards" section of the FreeBSD manual and no mention of NDISWrapper has been made there.

However, I 'll have to use the NDISWrapper because that's the only one I have up for the task.
(I had downloaded it from http://garr.dl.sourceforge.net/sourc...er-1.54.tar.gz)

But I suspect it will be installed under FreeBSD. Or should I try installing NDISulator instead? But where do I download its source files if there are any? I googled by the terms "NDISulator download" and no download links are returned.

Is NDISulator listed under ports collection? I couldn't find it in a search at FreeBSD Ports Search by the search term "NDISulator"

So, what should I do to install my USR5417 WiFi PCI card (whose .sys & .inf files I have)?

Thanks.

**DutchDaemon** · #24 May 30th, 2009, 00:09

apropos ndis

richardpl · #25 May 30th, 2009, 00:11

Quote:

Originally Posted by aurora72

I wouldn't guess that the thread would go on, but anyways that's fine. Well, having come over the problems I had at the start, I gave a little pause and did not attempt to use the WiFi PCI card on my FreeBSD machine for a while but soon I will start working on it.

As for the confusion about the naming of NDIS simulator/wrapper richardpl's correct in emphazising the difference between, because the name "NDISulator" is present on "Setting up network interface cards" section of the FreeBSD manual and no mention of NDISWrapper has been made there.

However, I 'll have to use the NDISWrapper because that's the only one I have up for the task.
(I had downloaded it from http://garr.dl.sourceforge.net/sourc...er-1.54.tar.gz)

But I suspect it will be installed under FreeBSD. Or should I try installing NDISulator instead? But where do I download its source files if there are any? I googled by the terms "NDISulator download" and no download links are returned.

Is NDISulator listed under ports collection? I couldn't find it in a search at FreeBSD Ports Search by the search term "NDISulator"

So, what should I do to install my USR5417 WiFi PCI card (whose .sys & .inf files I have)?

Thanks.

RTFM, Everything is explained in Handbook and in ndisgen(8) and ndis(4) you dont need ports if you already have inf and sys files.

NDISwrapper works only and only on Linux ...

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Solved] /usr full	janroc	General	11	July 8th, 2010 08:13
Accidentally changed disk geometry	mamalos	System Hardware	0	March 18th, 2009 13:47
[Solved] Accidentally 'chown -R' to /usr/local in jail as root	tekkon	General	6	March 9th, 2009 23:41
Am I really lost if I've just deleted /var/db/pkg/* by mistake?	toomadd	Installation and Maintenance of FreeBSD Ports or Packages	3	March 9th, 2009 23:01
[Solved] accidentally run ldconfig without '-m'	SaveTheRbtz	General	2	January 13th, 2009 09:01

The Following User Says Thank You to DutchDaemon For This Useful Post:
aurora72 (May 27th, 2009)

The Following User Says Thank You to richardpl For This Useful Post:
aurora72 (May 29th, 2009)