On Sat, 10 Aug 2024 09:02:13 -0700 (PDT)
"Rodney W. Grimes" wrote:
> > Shawn Webb writes:
> >
> > > While probably less efficient than just running the tools outright, I
> > > usually just set up a tmpfs that I chroot into and install those kinds
> > > of packages.
> >
> > Yeah, I do something
> Shawn Webb writes:
>
> > While probably less efficient than just running the tools outright, I
> > usually just set up a tmpfs that I chroot into and install those kinds
> > of packages.
>
> Yeah, I do something similar, with the footnote that I more often than
> not have no internet connection
Shawn Webb writes:
> While probably less efficient than just running the tools outright, I
> usually just set up a tmpfs that I chroot into and install those kinds
> of packages.
Yeah, I do something similar, with the footnote that I more often than
not have no internet connection, so I
On Tue, Jul 30, 2024 at 07:07:51PM +, Poul-Henning Kamp wrote:
> I do not want want this to turn into a everything-and-Emacs bloat-party,
> but I would find it really helpful if our install-ISO images had two
> HW-spelunking ports installed:
>
> sysutils/smartmo
On 2024-07-30 19:07 +, Poul-Henning Kamp wrote:
> sysutils/smartmontools
>
> and
>
> sysutils/dmidecode
>
> Is that even possible ?
>
> Am I the only one who thinks so ?
I have missed having these tools numerous times over the years. Whether it's
installing on a new machine
I do not want want this to turn into a everything-and-Emacs bloat-party,
but I would find it really helpful if our install-ISO images had two
HW-spelunking ports installed:
sysutils/smartmontools
and
sysutils/dmidecode
Is that even possible ?
Am I the only one who thinks so
error out of the installer upon
verification of checksums, they do not align with the checksum files in
the directory:
https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/15.0/
<https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/150/>
Steps to replicate:
1. Cr
checksums, they do not align with the checksum files in the directory:
https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/15.0/
Steps to replicate:
1. Create a virtualbox profile with freebsd
2. Attach one of the below iso images
3. Run the installation
4. Select keymap
5
On 2015-12-29 11:01, Glen Barber wrote:
> On Tue, Dec 29, 2015 at 07:57:42AM -0800, Yuri wrote:
>> disk1.iso has kernel panic during boot.
>>
>> And bootonly.iso boots but after downloading kernel and base it says that
>> there is the incorrect checksum, and it needs to downlodagain.
>>
>> Just tri
On Tue, Dec 29, 2015 at 05:16:40PM +0100, Matthias Apitz wrote:
> On Tuesday, 29 December 2015 17:01:28 CET, Glen Barber wrote:
> >On Tue, Dec 29, 2015 at 07:57:42AM -0800, Yuri wrote:
> >>disk1.iso has kernel panic during boot.
> >>
> >>And bootonly.iso boots but after downloading kernel and base
On Tuesday, 29 December 2015 17:01:28 CET, Glen Barber wrote:
On Tue, Dec 29, 2015 at 07:57:42AM -0800, Yuri wrote:
disk1.iso has kernel panic during boot.
And bootonly.iso boots but after downloading kernel and base it says that
there is the incorrect checksum, and it needs to downlodagain.
J
On Tue, Dec 29, 2015 at 07:57:42AM -0800, Yuri wrote:
> disk1.iso has kernel panic during boot.
>
> And bootonly.iso boots but after downloading kernel and base it says that
> there is the incorrect checksum, and it needs to downlodagain.
>
> Just tried FreeBSD-11.0-CURRENT-amd64-20151217-r292413
disk1.iso has kernel panic during boot.
And bootonly.iso boots but after downloading kernel and base it says
that there is the incorrect checksum, and it needs to downlodagain.
Just tried FreeBSD-11.0-CURRENT-amd64-20151217-r292413-disc1.iso
Yuri
__
O. Hartmann wrote:
On 02/15/12 13:58, Dimitry Andric wrote:
On 2012-02-15 13:37, O. Hartmann wrote:
;-) Problem: I can not even login anymore, since I have "insecured" the
console for security reasons and the shell is rejecting due to a symbol
missing. I tried booting into single user mode, b
On 02/15/12 13:58, Dimitry Andric wrote:
> On 2012-02-15 13:37, O. Hartmann wrote:
>> ;-) Problem: I can not even login anymore, since I have "insecured" the
>> console for security reasons and the shell is rejecting due to a symbol
>> missing. I tried booting into single user mode, but that doesn'
On 02/15/12 13:58, Dimitry Andric wrote:
> On 2012-02-15 13:37, O. Hartmann wrote:
>> ;-) Problem: I can not even login anymore, since I have "insecured" the
>> console for security reasons and the shell is rejecting due to a symbol
>> missing. I tried booting into single user mode, but that doesn'
On 2012-02-15 13:37, O. Hartmann wrote:
> ;-) Problem: I can not even login anymore, since I have "insecured" the
> console for security reasons and the shell is rejecting due to a symbol
> missing. I tried booting into single user mode, but that doesn't help
> much.
When booting in single user mo
art over with a snapshot emergency/live DVD/CD, but for
>>> CURRENT, I can not find any ISO images. Apart from the CTM way, is there
>>> another opportunity toget a) ISO images of a more recent CURRENT b) a
>>> working libc.so.7 that will make me rebuilding the system?
; that mistake).
>
> I thought I could start over with a snapshot emergency/live DVD/CD, but
> for CURRENT, I can not find any ISO images. Apart from the CTM way, is
> there another opportunity toget
> a) ISO images of a more recent CURRENT
> b) a working libc.so.7 that will make
gt; > refuses to do anything since login doesn't work. /bin/sh is missing a
> > symbol, I forgot the name, it was late last night (and therefore I made
> > that mistake).
> >
> > I thought I could start over with a snapshot emergency/live DVD/CD, but for
> >
> symbol, I forgot the name, it was late last night (and therefore I made
> that mistake).
>
> I thought I could start over with a snapshot emergency/live DVD/CD, but for
> CURRENT, I can not find any ISO images. Apart from the CTM way, is there
> another opportunity toget a
bol, I forgot the name, it was late last night (and therefore I made
> that mistake).
>
> I thought I could start over with a snapshot emergency/live DVD/CD, but
> for CURRENT, I can not find any ISO images. Apart from the CTM way, is
> there another opportunity toget
> a) IS
ore I made
that mistake).
I thought I could start over with a snapshot emergency/live DVD/CD, but
for CURRENT, I can not find any ISO images. Apart from the CTM way, is
there another opportunity toget
a) ISO images of a more recent CURRENT
b) a working libc.so.7 that will make me rebuilding the system?
On Aug 7, 2011, at 9:23 AM, Bruce Cran wrote:
> On 06/08/2011 18:02, Martin Matuska wrote:
>> The error is in FreeBSD ISO images.
>> They are created using makefs and that doesn't create ISO files that
>> strictly comple to the ECMA-119 (ISO9660 standard).
>>
On 06/08/2011 18:02, Martin Matuska wrote:
The error is in FreeBSD ISO images.
They are created using makefs and that doesn't create ISO files that
strictly comple to the ECMA-119 (ISO9660 standard).
I have already filed a PR at NetBSD (bin/45217):
http://gnats.netbsd.org/cgi-bin/que
On Sat, 06 Aug 2011 20:37:38 +, Baptiste Daroussin wrote:
On Sat, 06 Aug 2011 19:02:49 +0200, Martin Matuska wrote:
The error is in FreeBSD ISO images.
They are created using makefs and that doesn't create ISO files that
strictly comple to the ECMA-119 (ISO9660 standard).
I have al
On Sat, 06 Aug 2011 19:02:49 +0200, Martin Matuska wrote:
The error is in FreeBSD ISO images.
They are created using makefs and that doesn't create ISO files that
strictly comple to the ECMA-119 (ISO9660 standard).
I have already filed a PR at NetBSD (bin/45217):
http://gnats.netbsd.org/cg
The error is in FreeBSD ISO images.
They are created using makefs and that doesn't create ISO files that
strictly comple to the ECMA-119 (ISO9660 standard).
I have already filed a PR at NetBSD (bin/45217):
http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=45217
The volume_set_id do
It's often convenient to extract pieces of iso9660 images for recovery
purposes or a jail. As libarchive no longer recognizes them one has to
resort to mdconfig + mount_cd9660. On a zfs-only system this populates
bufspace unused by arc cache and never gives memory back... nevermind.
$ tar tf Fre
On 2003.11.26 22:53:26 +0100, Claus Guttesen wrote:
> Hi.
>
> > Will ISO images be released for 5.2-BETA i386?
> > Or is that strictly an -RC thing?
>
> Ftp'ed to ftp.freebsd.org using a freebsd-ftp-client
> but couldn't find the ISO-image for 5.2 beta. Using
Hi.
> Will ISO images be released for 5.2-BETA i386?
> Or is that strictly an -RC thing?
Ftp'ed to ftp.freebsd.org using a freebsd-ftp-client
but couldn't find the ISO-image for 5.2 beta. Using OS
X's finder found the folder and files. Peculiar.
Permissions?
regards
Clau
The availability of ISO images was announced to this mailing list this
morning. Please check your local mirror; i386, alpha, and amd64 should be
available on most mirrors now.
Scott
On Wed, 26 Nov 2003, Jesse Guardiani wrote:
> Will ISO images be released for 5.2-BETA i386?
> Or i
Will ISO images be released for 5.2-BETA i386?
Or is that strictly an -RC thing?
Thanks.
--
Jesse Guardiani, Systems Administrator
WingNET Internet Services,
P.O. Box 2605 // Cleveland, TN 37320-2605
423-559-LINK (v) 423-559-5145 (f)
http://www.wingnet.net
> Thanks, and go buy some 5.0 CD's =-)
>
Of course ! MediaHouse in russia had a litle bit of delay - about a 2-3
monts !!!
Realy im think that needed only one disk . Tere is no need to very fast
updates in home , where realy ussing 4 disks.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
All,
There seems to be some confusion created by choices that we made
for the 5.0 release regarding ISO image availability. To refresh, from
FreeBSD 4.4 to 4.7, we made available 5 iso images for i386 and
alpha. This consisted of a mini-disc1 that contained only the bits
needed for installing
On Wed 2000-08-02 (11:05), Marc Teichtahl wrote:
> i need to build a large number of machine with a customer distribution
> based on 4.1-RELEASE
>
> are there any pointers or help you can give me on how to create an ISO
> image of my distribution ?
cd /usr/src/release && make release
You might
dear All,
i need to build a large number of machine with a customer distribution
based on 4.1-RELEASE
are there any pointers or help you can give me on how to create an ISO
image of my distribution ?
--
Marc Teichtahl
Manager, Data Network DesignVersatel Telecom
"W
Matt Heckaman <[EMAIL PROTECTED]> wrote in list.freebsd-current:
> Speaking of ISOs, where is the 4.0-RELEASE ISO,
It doesn't exist yet. If I understood Jordan correctly, he
wants to wait a bit after the release and let the dust settle
a bit before creating the CD-ROM set for Walnut Creek.
How
On Fri, Mar 17, 2000 at 11:42:43AM -0800, Kris Kennaway wrote:
> No it doesn't.
>
> Download the binary installation files onto another machine, and burn a CD
> with them (you must have a mechanism to burn a CD if you were intending to
> burn an ISO image of one). Then use this CD as the media t
On Fri, 17 Mar 2000, Will Andrews wrote:
> Exactly. Only thing is, an FTP install requires a usable internet
> connection on intended box, which is not always available. ;-)
No it doesn't.
Download the binary installation files onto another machine, and burn a CD
with them (you must have a mech
At 10:12 AM 3/17/00 -0500, Will Andrews wrote:
>On Fri, Mar 17, 2000 at 10:00:44AM -0500, Kelly Yancey wrote:
> > This is all beginning to smell a lot like a FTP install.
>
>Exactly. Only thing is, an FTP install requires a usable internet
>connection on intended box, which is not always availab
At 09:46 AM 3/17/00 -0500, Will Andrews wrote:
>On Wed, Mar 15, 2000 at 11:59:29AM -0600, Jeffrey J. Mountin wrote:
> > However, if you consider the size of the file and the possibility of
> > corruption, then it should be archived with gzip and forget the
> compression
> > (gzip -1). Now it can
At 9:46 AM -0500 2000/3/17, Will Andrews wrote:
> I tend to agree with this. 650MB is way too much - perhaps the images could
> be broken up according to the portion of the system (i.e., bin, sbin,
> usr.bin, usr.sbin, etc, et cetera).
I think the entire point of the ISO ima
> Had
> the file been split and a checksum computed for each piece, I could have
> grabbed only the affected portion of the ISO.
This is screaming for an FTP server mod similar to the wuftpd code that will
automatically run tar|gzip. That is, given a file "foo", serve "foo.aa" to be
the first (s
On Fri, Mar 17, 2000 at 10:00:44AM -0500, Kelly Yancey wrote:
> This is all beginning to smell a lot like a FTP install.
Exactly. Only thing is, an FTP install requires a usable internet
connection on intended box, which is not always available. ;-)
--
Will Andrews <[EMAIL PROTECTED]>
GCS/E/S
>
> I tend to agree with this. 650MB is way too much - perhaps the images could
> be broken up according to the portion of the system (i.e., bin, sbin,
> usr.bin, usr.sbin, etc, et cetera).
>
This is all beginning to smell a lot like a FTP install.
Kelly
--
Kelly Yancey - [EMAIL PROTECT
On Wed, Mar 15, 2000 at 11:59:29AM -0600, Jeffrey J. Mountin wrote:
> However, if you consider the size of the file and the possibility of
> corruption, then it should be archived with gzip and forget the compression
> (gzip -1). Now it can be checked for errors.
MD5 checksums are more compact
Out of the ether, James FitzGibbon spewed forth the following bits:
> It might be nice if there were a utility that could pull the ISO in small
> slices just like any distribution and then put it back together. For that
> matter, couldn't the ISO image be made into a distribution that sysinstall
* Jeffrey J. Mountin ([EMAIL PROTECTED]) [000315 17:35]:
> However, if you consider the size of the file and the possibility of
> corruption, then it should be archived with gzip and forget the compression
> (gzip -1). Now it can be checked for errors.
Isn't there a CHECKSUMS.MD5 file in the
[...]
> > Another issue is the size. Many factors determine how quickly one can
> > obtain the ISO. It would be nice if it were broken into smaller
> > volumes. About 10-20 MB each would be good. That way should something
> > fail, there less time and bandwidth wasted should one need to sta
Mar 2000, Matthew Hunt wrote:
: Date: Thu, 16 Mar 2000 14:24:42 -0500
: From: Matthew Hunt <[EMAIL PROTECTED]>
: To: Jeffrey J. Mountin <[EMAIL PROTECTED]>
: Cc: [EMAIL PROTECTED]
: Subject: Re: Why not gzip iso images?
:
: On Thu, Mar 16, 2000 at 01:12:39PM -0600, Jeffrey J. M
On Thu, Mar 16, 2000 at 01:12:39PM -0600, Jeffrey J. Mountin wrote:
> >Also take into account that many people are downloading and
> >recoding the images on Windows boxes, which don't have gzip
> >by default.
>
> And then they can xfer it over to their FBSD system, etc..
You're suggesting that
At 11:09 PM 3/15/00 +0100, Oliver Fromme wrote:
>That's true. Most of the files in the ISO images are already
>compressed, so trying to gzip it saves only a few percent.
>
>Also take into account that many people are downloading and
>recoding the images on Windows boxes, w
On Wed, Mar 15, 2000 at 12:11:48PM -0800, Darryl Okahata wrote:
> While you are right about the download/gunzip times, compression
> doesn't help that much. As has been mentioned in -hackers, the ISO
> images only compress by 3% or so, or around ~20MB. So, instead of a
>
> But for the ISO images... IS it a problem to gzip
> them
> They take less space on the master site and the mirror
> sites and they take less bandwidth!
Since almost the entire content of the ISO image is already gzipped, the
size savings works out to be a percent or two, or
On Mar 15, 9:03am, Kris Kennaway wrote:
} Subject: Re: Why not gzip iso images?
} On Wed, 15 Mar 2000, Alfred Perlstein wrote:
}
} > I feel pretty confident assuming that most people that burn ISOs probably
} > keep enough disk space free to hold one and not much more, going from
| > Alas, that is just not true for many of us who are in bandwidth-poor
| > countries. Over here, it can take 3 to BIGNUM hours to download an ISO
| > image (there aren't any up-to-date local mirrors), depending on time of
| > day and the phase of the moon. I think compression would definitely h
On Wed, 15 Mar 2000, Anatoly Vorobey wrote:
> Alas, that is just not true for many of us who are in bandwidth-poor
> countries. Over here, it can take 3 to BIGNUM hours to download an ISO
> image (there aren't any up-to-date local mirrors), depending on time of
> day and the phase of the moon. I
Jeffrey J. Mountin <[EMAIL PROTECTED]> wrote in list.freebsd-current:
> AFAICR, the one time that a gzip and bzip version were available the size
> was not all that significant and there were promptly removed.
That's true. Most of the files in the ISO images are already
comp
can take 3 to BIGNUM hours to download an ISO
> image (there aren't any up-to-date local mirrors), depending on time of
> day and the phase of the moon. I think compression would definitely help.
While you are right about the download/gunzip times, compression
doesn't he
At 05:53 AM 3/15/00 -0800, Alfred Perlstein wrote:
>* Kai Voigt <[EMAIL PROTECTED]> [000315 05:47] wrote:
> > Matt Heckaman wrote:
> > > It's been my experience that gzipping an ISO (or other compression tools)
> > > do not make enough different to justify the time it takes to both
> compress
> >
On Wed, Mar 15, 2000 at 08:14:37AM -0500, Matt Heckaman wrote:
> It's been my experience that gzipping an ISO (or other compression tools)
> do not make enough different to justify the time it takes to both compress
> and uncompress these things. For example, the time needed to un-gzip the
> ISO c
On Wed, 15 Mar 2000, Alfred Perlstein wrote:
> I feel pretty confident assuming that most people that burn ISOs probably
> keep enough disk space free to hold one and not much more, going from
> a requirement of ~650MB to ~1.2GB wouldn't be a smart move imo.
fetch -o - ftp://path/to/iso.gz | gun
* Kai Voigt <[EMAIL PROTECTED]> [000315 05:47] wrote:
> Matt Heckaman wrote:
> > It's been my experience that gzipping an ISO (or other compression tools)
> > do not make enough different to justify the time it takes to both compress
> > and uncompress these things. For example, the time needed to
Matt Heckaman wrote:
> It's been my experience that gzipping an ISO (or other compression tools)
> do not make enough different to justify the time it takes to both compress
> and uncompress these things. For example, the time needed to un-gzip the
> ISO could be longer than the time it would take
ROTECTED]>
: To: [EMAIL PROTECTED]
: Subject: Why not gzip iso images?
:
: After reading the announcement...
: Congratulations to the FreeBSD community
: another milestone!
: A great OS...
:
: But for the ISO images... IS it a problem to gzip
: them
: They take less space on the master site and
After reading the announcement...
Congratulations to the FreeBSD community
another milestone!
A great OS...
But for the ISO images... IS it a problem to gzip
them
They take less space on the master site and the mirror
sites and they take less bandwidth!
Shouldn't be a problem I
67 matches
Mail list logo
